Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Guidelines and standards for professional, human-like writing and documentation. Use this skill when generating READMEs, technical documentation, code commen...
Guidelines and standards for professional, human-like writing and documentation. Use this skill when generating READMEs, technical documentation, code commen...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill provides the operational standards for generating professional, high-density, and human-sounding documentation and prose. It is designed to purge common LLM stylistic "tells" and replace them with the precision of a senior engineer or domain expert.
Eliminate AI "Tells": Before finalizing any documentation or formal text, refer to ai-tells.md to identify and remove overused LLM vocabulary, structural tropes, and puffy language. Apply Professional Standards: Follow the guidelines in standards.md for technical precision, information density, and tone. No Buzzwords: Zero tolerance for "synergy," "cutting-edge," "revolutionize," "seamless," or "leverage." If a technical term exists, use it. No Emojis in Docs: Reserve emojis for chat interactions (as per SOUL.md). Professional documentation (READMEs, PR descriptions, code comments) must remain text-only for maximum clarity. Precision Over Prose: Humans in the field value numbers, versions, and RFCs over flowery descriptions.
When asked to "write documentation," "create a README," or "explain this technically": Scan references/ai-tells.md for words to ban from the current draft. Apply references/standards.md to structure the output with high density and low fluff. Draft the content. Self-Audit: Verify the output does not contain "Rule of Three" adjectives or "Not only... but also" parallelisms. Finalize: Remove all emojis and corporate filler.
ai-tells.md - Field guide to AI writing "tells" to avoid. standards.md - Human-like professional writing standards.
Writing, remixing, publishing, visual generation, and marketing content production.
Largest current source with strong distribution and engagement signals.