How do I install the Human Writing skill?

Run npx skillmds@latest add dvcrn/human-writing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Human Writing safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Human Writing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Human Writing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Human Writing?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Human Writing by dvcrn — Agent Skill

Name: Human Writing
Rating: 4.5 (4 reviews)
Author: dvcrn

Human Writing

Guidelines and standards for professional, human-like writing and documentation. Use this skill when generating READMEs, technical documentation, code comments, or any formal written output to avoid common AI 'tells', buzzwords, and stylistic tropes. Ensure content follows the 'Professional Human in the Field' standard: high precision, zero fluff, and no emojis in technical contexts.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

Human-Writing Skill

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.

Core Directives

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.

Workflow

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.

Reference Materials

ai-tells.md - Field guide to AI writing "tells" to avoid.
standards.md - Human-like professional writing standards.

---name: human-writingdescription: Guidelines and standards for professional, human-like writing and documentation. Use this skill when generating READMEs, technical documentation, code comments, or any formal written output to avoid common AI 'tells', buzzwords, and stylistic tropes. Ensure content follows the 'Professional Human in the Field' standard: high precision, zero fluff, and no emojis in technical contexts.---# Human-Writing SkillThis 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.## Core Directives1. **Eliminate AI "Tells":** Before finalizing any documentation or formal text, refer to [ai-tells.md](references/ai-tells.md) to identify and remove overused LLM vocabulary, structural tropes, and puffy language.2. **Apply Professional Standards:** Follow the guidelines in [standards.md](references/standards.md) for technical precision, information density, and tone.3. **No Buzzwords:** Zero tolerance for "synergy," "cutting-edge," "revolutionize," "seamless," or "leverage." If a technical term exists, use it.4. **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.5. **Precision Over Prose:** Humans in the field value numbers, versions, and RFCs over flowery descriptions. ## WorkflowWhen asked to "write documentation," "create a README," or "explain this technically":1. **Scan references/ai-tells.md** for words to ban from the current draft.2. **Apply references/standards.md** to structure the output with high density and low fluff.3. **Draft the content.**4. **Self-Audit:** Verify the output does not contain "Rule of Three" adjectives or "Not only... but also" parallelisms.5. **Finalize:** Remove all emojis and corporate filler.## Reference Materials- [ai-tells.md](references/ai-tells.md) - Field guide to AI writing "tells" to avoid.- [standards.md](references/standards.md) - Human-like professional writing standards.

Frequently asked questions