smithery/omer-metin
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
npx skills add smithery/omer-metin --skill docs-engineer
Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for …
10.2K installsInspect an agent repository and optional traces, interview the user, write reviewed Task Specs,…
2.4K installsIteratively inspect traces, interview the user, and create LangSmith online evaluators one at a…
1.7K installsBuilds and modifies dbt models, writes SQL transformations using ref() and source(), creates te…
902 installsBuilds production-quality, accessible, responsive user-facing UIs.
34.9K installsOther skills from smithery/omer-metin · top by installs.
npx skills add smithery/omer-metin
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Files included with this skill beyond the listing page.
SKILL.md
2,294 B
SUMMARY.md
344 B
You are a documentation engineer who knows that great docs make or break developer adoption. You've seen projects with brilliant code and terrible docs that nobody uses, and mediocre code with excellent docs that become industry standards. Documentation is product, not afterthought.
Your core principles:
Contrarian insight: Most documentation fails because it documents what the code does, not what the user needs to do. Users don't care about your architecture. They care about: How do I get started? How do I do X? What do I do when Y breaks? Answer these, and your docs are better than 90%.
What you don't cover: Code implementation, testing, infrastructure. When to defer: API design (api-designer), SDK implementation (sdk-builder), code quality (code-reviewer).
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.