Enforce active voice, imperative mood, and citations in engineering documentation.
npx skills add https://github.com/Elmanuel1/skills --skill tech-writing-style
Please help me install this Agent Skill. Skill: tech-writing-style Source: https://github.com/Elmanuel1/skills/tree/main/tech-writing-style Command: npx skills add https://github.com/Elmanuel1/skills --skill tech-writing-style
This Skill eliminates inconsistent, hard-to-follow technical writing that wastes engineering time, creates confusion during implementation, and leads to outdated or unreliable documentation across engineering-facing content.
Use the tech-writing-style skill to edit the draft API reference document to enforce active voice, add concrete request/response examples, and remove all marketing fluff and unsubstantiated claims before publishing.
High-intent search queries and answers about installing and using this skill.
You enforce consistent technical writing standards by applying a universal style guide that mandates active voice, imperative mood for instructions, and consistent terminology across all engineering-facing prose. This eliminates confusion and reduces reader skimming by removing filler words and marketing fluff.
The best way to edit a draft API reference is to enforce active voice, add concrete request and response code examples, cite source code locations, and remove unsubstantiated hedge words. This ensures other team members can implement integrations quickly without follow-up questions.
Yes, you can use a technical style guide for both writing and editing tasks. It applies to all engineering-facing prose including READMEs, architecture overviews, API references, runbooks, ADRs, design docs, PRDs, code comments, and onboarding guides.
You verify technical content quality by requiring source citations for all concrete claims and running a final pre-delivery checklist. This process catches errors, style violations, and inconsistencies in architecture overviews before they reach the engineering audience.
You should remove marketing fluff and hedge words from engineering documentation to prevent vague language like "typically works" from creating implementation confusion. Replacing abstract claims with concrete real-world examples ensures content remains clear, reliable, and actionable for engineering audiences.
curiositechGenerate READMEs, API references, ADRs, and runbooks with validation scripts.
b566776Execute structured web-verified technical research workflows for architecture and technology topics.
MatthieuszValidate TypeScript code against predefined coding standards using static analysis tools.
GauravSingla-1Draft internal memos, newsletters, and FAQs aligned with corporate tone guidelines.
