agentsclimarketplace
Sign in

Write skill

Skill pwguler/skills/skills/write-skill

Create or edit a document an agent reads and prove it changes behavior. Use when writing or editing a skill, AGENTS.md, CLAUDE.md, a system prompt, or other agent-facing prose, or verifying one before it ships.From its SKILL.md

Install
npx -y skills add pwguler/skills --skill write-skill

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

  • 2 stars2 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.

SKILL.md

1.7 KB, as published. Nobody here has run it

Writing for agents is test-first development applied to prose. The same loop ships every document an agent reads: skills, AGENTS.md, CLAUDE.md, system prompts.

  1. Baseline first: run the scenario the document targets on an agent WITHOUT it, and record exactly how it fails or rationalizes. No observed failure means the document has nothing to teach.
  2. Write the minimum prose that fixes those specific failures. Not a manual: the shortest process that changes the behavior.
  3. Re-run the scenario with the document loaded. It passes or the document is wrong.
  4. Close loopholes: new rationalizations found on re-runs get plugged, then verified again.

A test harness changes mechanics, not the loop: when one exists, automate the baseline re-run.

Conventions for skills in this repo:

  • Frontmatter carries name (letters, digits, hyphens) and description. The description states when to fire, with trigger phrasing ("Use when..."), not a summary of the process.
  • disable-model-invocation: true only for skills that must never fire on their own; the description then reads as a human-facing one-liner.
  • Keep SKILL.md lean. Separate files only for heavy reference or reusable assets; link them relatively.
  • No em dashes. Decisive present tense. Zero upstream or status mentions.

Skip it when the work is a one-off, when standard practice is already well documented, or when a linter or hook could enforce the rule mechanically.

Keep looking

Skills are one crate of 626,474. 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.