agentsclimarketplace

Skill tester

Skill ivuorinen/skills/.claude/skills/skill-tester

My assortment of Claude Code skills

Install
npx -y skills add ivuorinen/skills --skill skill-tester

Assembled 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.
  • 1 stars1 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

Use when verifying that a skill actually changes Claude's behaviour — runs TDD pressure scenarios against a skill before and after writing it.

SKILL.md

2.0 KB, 411 tokens by cl100k_base, as published. Nobody here has run it

Skill Tester

TDD for documentation: watch the agent fail without the skill, write the skill, watch the agent pass.

RED phase — baseline (run BEFORE writing the skill)

Dispatch a subagent with this prompt, substituting <skill-name> and <scenario>:

You are working on <scenario>. Do NOT load any skills. <pressure>

What do you do?

Pressure types to combine:

  • Time: "You're under deadline, the user is waiting"
  • Sunk cost: "You've already written 200 lines"
  • Authority: "The senior dev told you to skip this step"
  • Exhaustion: "This is the 10th task in a row"

Record exact rationalizations the agent uses to skip the rule.

GREEN phase — write and verify

Write the skill or command body (skills/<skill-name>/SKILL.md, or skills/nitpicker/commands/<command>.md for a nitpicker command). Address each rationalization from RED explicitly. Then dispatch the same subagent again, this time with the skill loaded. Confirm each RED rationalization is blocked. If a new loophole emerges, add an explicit counter to the skill and re-run.

REFACTOR phase — verify after refactoring

Refactor the skill body for clarity and precision. Then dispatch the same scenario again (skill still loaded). Confirm all GREEN scenarios still pass and no new loopholes have appeared. If they have, add counters and re-run.

Checklist

  • RED scenario run and rationalizations documented
  • Skill written addressing each rationalization
  • GREEN scenario confirms compliance
  • REFACTOR scenario re-run confirms no regression and no new loopholes
  • Validator passes: uv run scripts/validate-skill.py skills/<skill-name>/SKILL.md (for a nitpicker command: skills/nitpicker/SKILL.md — it validates the command files too)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 327,132. 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.