Style guide
Skill khshanovskyi/custom-agent-skills/agent_demo/_skills/style-guide
Project to demonstrate custom implementation of agent skills
npx -y skills add khshanovskyi/custom-agent-skills --skill style-guideAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Enforces brand voice, tone, and writing style rules. Use when the user asks to write, rewrite, edit, proofread, or review any text — blog posts, emails, social media copy, product descriptions, or support replies. Also use when the user asks about tone, style, or brand writing guidelines.
SKILL.md
1.7 KB, as published. Nobody here has run it
Style Guide Skill
File Map
REFERENCE.md— complete rules per content type (email, blog, social, support)EXAMPLES.md— before/after rewrites for the most common mistakes
Workflow
- Identify the content type (email, blog post, social post, support reply, etc.)
- Apply the core brand voice principles below
- For type-specific rules, read
/skills/style-guide/REFERENCE.md - For before/after examples of common mistakes, read
/skills/style-guide/EXAMPLES.md - Return polished text and briefly explain the key changes made
Core Principles
- Voice: Conversational but authoritative. Write like a knowledgeable friend, not a corporate manual.
- Tone: Positive, inclusive, and energetic — never condescending or pushy.
- Length: Shorter is better. Cut every word that doesn't earn its place.
- Person: Second person ("you/your") for user-facing content; first-person plural ("we/our") for company statements.
Instant Rules
- No jargon without explanation on first use
- No passive voice unless intentional for tone softening
- Contractions are encouraged ("you're", "it's", "we've")
- Numbers: spell out one–nine; use digits for 10 and above
- Oxford comma always ("red, white, and blue")
- Em dashes for emphasis — use sparingly
- Avoid exclamation marks; let the content be exciting, not the punctuation