agentsclimarketplace
Sign in

Maintain doc tone

Skill matt-riley/skill-evaluator/.agents/skills/maintain-doc-tone

Use whenever you are asked to create, edit, modify, or review any documentation files, or whenever the user mentions writing documentation.From its SKILL.md

Install
npx -y skills add matt-riley/skill-evaluator --skill maintain-doc-tone

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 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 file declares

Copied from the file, not written here

The file declares its own license as GNU GPL v3. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.1 KB, 396 tokens by cl100k_base, as published. Nobody here has run it

Maintain Documentation Tone

Use this skill to ensure that all documentation in this repository maintains a consistent, friendly, and enthusiastic voice.

Use this skill when

  • The user asks to write, edit, or update a .md file in the documentation.
  • You are adding a new page to the Astro site.
  • The user asks you to review documentation for tone or style.

Do not use this skill when

  • Editing strict technical contracts (like OpenAPI specs or internal JSON schemas) where a conversational tone would cause parsing errors or confusion.
  • The user explicitly asks for a formal, dry, or academic tone for a specific file (like an official legal disclaimer).

First move

  1. Read the exact tone requirements and examples located in references/tone-guidelines.md.
  2. Scan the document you are about to edit to ensure your changes will blend seamlessly with the surrounding text.

Workflow

  1. Apply the tone guidelines (enthusiastic, accessible, emoji-friendly) to your draft.
  2. Replace robotic or overly corporate phrasing ("This application executes the initialization sequence") with friendly, human phrasing ("Getting started is a breeze! Just run this command:").
  3. Ensure formatting uses modern markdown features (bolding for emphasis, bullet points for readability).

Validation

  • Check the emojis: Does the section have at least one tasteful, relevant emoji?
  • Check the voice: Read the text out loud (in your head). Does it sound like a friendly developer pairing with you, or does it sound like a corporate manual? If the latter, rewrite it.

Examples

  • "Update the Quick Start guide to include the new config flag." -> Triggers this skill to ensure the new step is written enthusiastically.
  • "Write an ADR for switching to Astro." -> Triggers this skill to ensure the ADR is clear but still approachable.

What ships with it: 1 file

1.2 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.