Enforce plain language, active voice, and British English in technical documentation.
npx skills add https://github.com/baphled/dotopencode --skill writing-style-baphled
Please help me install this Agent Skill. Skill: writing-style Source: https://github.com/baphled/dotopencode/tree/main/skills/writing-style Command: npx skills add https://github.com/baphled/dotopencode --skill writing-style-baphled
This Skill helps establish and maintain a consistent, professional, and engaging writing voice, ensuring technical communication is clear, precise, and free of unnecessary jargon.
Apply the writing-style skill to ensure the attached document uses plain language and active voice.
High-intent search queries and answers about installing and using this skill.
To make technical documentation clearer, apply plain language principles, use active voice, and remove unnecessary jargon to ensure your writing voice is consistent and engaging for diverse audiences.
Plain language in technical writing focuses on clarity and precision, using active voice to convey information directly without verbosity, ensuring standardized style guidelines are met for diverse reader groups.
Enforcing British English conventions in project documentation involves establishing standardized style guidelines that calibrate technical communication, ensuring consistent tone, precise vocabulary, and uniform style across all content.
Yes, you can review API documentation drafts by checking for adherence to plain language principles, active voice usage, and British English conventions to calibrate the technical communication for your target audience.
The best way to maintain style consistency across technical content is to establish a standardized writing voice that enforces plain language, active voice, and audience calibration across all project documentation.
Calibrating technical communication for diverse audiences focuses on adapting tone and clarity without verbosity, but relies heavily on strictly enforcing the established plain language and active voice guidelines to succeed.
cccnam5158Draft professional emails with structured subject, greeting, body, and closing.
2lab-aiApply GOV.UK style guide and GDS content design principles to written content.
narumikrProofread Japanese text for spelling, grammar, punctuation, and style errors.
abudhahirEnforce active voice, American English, and sentence case in technical documentation.
