Index of every page on this site: llms.txt
All skills
Run it yourself

Writes and refines agent skills (a SKILL.md plus optional reference files and scripts) in one standard shape - a trigger-first description, a body under 100 lines, detail split one level deep, and a quick with/without test. Use when the user wants to create a skill, turn a workflow, habit or repeated correction into a skill, edit or tighten an existing SKILL.md, or fix a skill that does not trigger. Not for running formal benchmarks or description-optimization loops - use skill-creator.

  • 3 files
  • 8.7 KB
  • Updated 3 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/avik-creator/agent-skills/writing-skills

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

EVALS.md

≈504 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Testing a skill with and without

Read at SKILL.md step 7. The question is whether the skill changes what an agent does, not whether its text sounds right.

Write the cases first

  • 2-5 prompts a real user would type, each with:
    • Must: things the answer has to do or contain, each checkable (a command run, a file touched, a phrase, a refusal).
    • Must not: the mistakes the skill exists to prevent.
  • Write them before reading any run. Why: criteria written after the answers bend to fit them.
  • Add 2-3 near misses: prompts that share keywords but should not load the skill.
  • Take criteria from mistakes you have seen an agent make, not from the skill's own wording.

Run three arms

Same prompt, same model, a fresh agent each time:

  1. Bare: no skill, no project instructions.
  2. Rules only: the project's instructions without the skill.
  3. Skill: the skill added.

If the bare arm already passes a case, the case has no teeth. Replace it.

Grade

  • A pass meets every must and no must-not. An error, an empty answer, or nothing checkable is "incomplete", never a pass.
  • Every "yes" quotes the span in the answer that shows it. A yes with no quote is unverified.
  • Grade without knowing which arm wrote the answer where you can: strip names and paths that give it away.
  • Doing beats saying: an answer that explains the rule but doesn't apply it fails.
  • For a skill that claims to catch bugs, plant a known fault in a copy and keep a healthy control. The control must pass, and the fault must fail one named check. The agent under test must not see the fault or the answer.
  • One run is an example, not a rate. Repeat a case before calling a difference real, and keep the counts per case rather than one blended score.

Report

Per case: the three verdicts with their quotes, and what the transcript shows the agent did. Then the changes to the skill, each tied to a failed case. Fix a failure by sharpening the reason in the skill, then rerun that case in all three arms.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at a0324a3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 3 weeks ago

README badge

README badge for avik-creator/agent-skills/writing-skills