Edit technical writing for clarity, conciseness, and active voice.
npx skills add https://github.com/Objective-Arts/lens-dist --skill editing-objective-arts
Please help me install this Agent Skill. Skill: editing Source: https://github.com/Objective-Arts/lens-dist/tree/main/canon/editing Command: npx skills add https://github.com/Objective-Arts/lens-dist --skill editing-objective-arts
This Skill helps users improve their writing by applying Stephen King's practical advice to technical documentation and code, focusing on clarity, conciseness, and honesty.
Apply the editing skill to refine the provided text for clarity and conciseness.
High-intent search queries and answers about installing and using this skill.
To improve technical writing clarity, eliminate jargon, passive voice, and unnecessary adverbs. Apply active voice, simple vocabulary, and direct phrasing to enhance readability in documentation and commit messages.
The best way to refine lengthy technical explanations is by killing self-indulgent phrasing, cutting unnecessary words, and replacing complex vocabulary with plain language to produce actionable summaries.
Eliminate passive voice and jargon from documentation by using strong verbs and active voice. Replace overly complex vocabulary with plain language to ensure direct and impactful technical writing.
Yes, this editing approach works for code comments and commit messages. It focuses on removing jargon and weak adverbs to improve readability, ensuring concise and clear technical communication.
Use concise editing principles for technical content when you need to transform verbose explanations into actionable summaries. This ensures documentation, commit messages, and README files remain direct and readable.
BrunoAMSilvaEnforce concise, active voice writing for API docs, code comments, and ADRs.
FacturaScriptsGuide Git commit message creation using Conventional Commits best practices.
jon23dEnforce best practices for writing human-readable documentation.
pablitonogValidate YAML frontmatter and Markdown structure for best-practice documentation.
