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.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryDeveloper toolsStars0
About this skill
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.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
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.
About this listing
Category
Developer tools
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI