Skip to content
SkillCheatSheet Sign in

writing-for-agents

An AI agent skill from mattpocock/skills, scored 57 out of 100 by code.

57/ 100C

Code score by group

  • Spec20/20
  • Description8/20
  • Procedure12/15
  • Done criteria0/15
  • Resources6/10
  • Scripts5/8
  • Safety3/7
  • Upkeep3/5

It loses the most points in Done criteria (15), the group that checks whether there is a checklist and a step that verifies the work.

What the author says it does

Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
mattpocock/skills
Folder
skills/productivity/writing-for-agents
License
MIT
GitHub stars
322,426
SKILL.md lines
82
Other files
2

Add writing-for-agents to your agent

npx skills add mattpocock/skills --skill writing-for-agents

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from mattpocock/skills

  1. setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-…

    79B
  2. diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

    78B
  3. migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    74B
  4. domain-modeling

    Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

    73B
  5. wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an…

    67C
  6. code-review

    Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (doe…

    66C
  7. wayfinder

    Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the des…

    63C
  8. to-tickets

    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one f…

    62C

All skills in mattpocock/skills

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.