CtrlK
BlogDocsLog inGet started
Tessl Logo

rulecheck

Autonomous rule adherence checker. Scans the codebase for rule violations, fixes the highest-impact ones in an isolated worktree, runs full validation, creates a PR. Uses memory to track progress across runs.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/rulecheck/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured orchestrator prompt that tells Claude exactly what to do and, importantly, what not to do, with a clear launch-wait-report sequence and strong failure guardrails. It is concise and actionable, with only minor room to add an explicit example launch and a verification step before reporting.

DimensionReasoningScore

Conciseness

The body is compact and assumes Claude's competence, using terse imperative directives with no padding about what agents or worktrees are; the only minor excess is the repeated 'Do NOT' list, which could be tightened slightly.

4 / 5

Actionability

It gives concrete, executable guidance — 'Launch the rulecheck-agent with the focus area: $ARGUMENTS', 'Wait for it to complete', 'Report ONLY what the agent told you' — with specific instructions; the small gap is the lack of an exact launch command/example.

4 / 5

Workflow Clarity

A clear numbered sequence (launch → wait → report) with explicit guardrails for failure/context-limit cases; it stops short of a 5 because there is no explicit validation checkpoint the orchestrator performs on the agent's output before reporting.

4 / 5

Progressive Disclosure

This is a short, single-purpose orchestrator skill with no bundle files and a well-organized two-section structure (Your Job / Rules for You); per the simple-skkill note, that is appropriately structured and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

50%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description concretely describes a multi-step scan/fix/PR workflow but omits any explicit 'Use when' trigger guidance and leans on technical jargon over natural user phrasing. It is distinct and specific, yet lacks the trigger phrases that would let a user reliably invoke it.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. 'Use when the user asks to check or fix AGENTS.md rule violations, or wants rule-adherence cleanup before a PR.'

Surface natural synonyms users actually say (e.g. 'rule check', 'lint AGENTS.md', 'rule adherence') rather than only technical terms like 'isolated worktree'.

Lead with the user-facing verb (e.g. 'Checks and fixes AGENTS.md rule violations') to strengthen the 'what' framing.

DimensionReasoningScore

Specificity

Names the domain (AGENTS.md rule violations) and several concrete actions — 'Scans the codebase', 'fixes the highest-impact ones', 'runs full validation', 'creates a PR' — which constitute a clear multi-step capability set with only minor coverage gaps.

4 / 5

Completeness

It clearly states what the skill does (scan and fix rule violations, create a PR) but provides no 'Use when...' trigger clause, so the 'when' is only weakly implied — per the rubric this caps completeness at 3.

3 / 5

Trigger Term Quality

The description uses technical framing ('rule violations', 'isolated worktree') rather than natural user phrases; a user would more likely say 'check AGENTS.md rules' or 'fix lint violations', and common synonyms are missing.

2 / 5

Distinctiveness Conflict Risk

The 'AGENTS.md rule violations' niche is fairly specific and distinct from most general-purpose skills, leaving only minor overlap risk with general linting or review skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
coleam00/Archon
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.