Assay

Invoke this skill (or /rulesense:assay) any time a user wants feedback on rule files they already have. This covers CLAUDE.md and .claude/rules/ — grading, scoring, auditing, reviewing, or critiquing the structural clarity of existing instructions. Trigger broadly: if someone asks "are my rules any good", "look at my rules", "check my CLAUDE.md", "grade my instruction files", "which rules are weak/vague/passive/garbage", "triage this inherited rule set", or "which rules should be hooks instead" — this is the skill. Also trigger when someone references /rulesense:assay with any flags (--json, --fix, --verbose). The core signal is: the user has existing Claude Code rules and wants an opinion on their quality. This skill reads and evaluates — it never creates new rules (that's forge), never reviews code or PRs, and ignores non-Claude-Code config like eslint or prettier.

mkdir -p ~/.claude/skills/assay
curl -L https://claudskills.com/skills/assay/SKILL.md \
  -o ~/.claude/skills/assay/SKILL.md

@misc{assay-2026,
  author    = {IamK77},
  title     = {Assay [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/assay/}
}