CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rules-distill

Scan skills to extract cross-cutting principles and distill them into rules — append, revise, or create new rule files

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is rules-distill in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A well-engineered orchestration skill with exact commands, a complete subagent prompt, explicit user-approval checkpoints, and clean script/body separation. Its only weaknesses are minor: slight redundancy between the verdict definitions and the example output, and an inline end-to-end example that could be externalized.

DimensionReasoningScore

Conciseness

The body is dense and operational and assumes competence ("Group skills into thematic clusters based on their descriptions" with no over-explanation), but verdict meanings appear in both the subagent prompt and the Verdict Reference table, and the end-to-end example repeats the Phase 3 report format — minor trimmable redundancy that keeps it below the every-token-earns-its-place anchor.

4 / 5

Actionability

Fully concrete for an instruction-only skill: exact bash commands, a copy-paste-ready subagent prompt with a complete JSON output schema, an exact timestamp format ("date -u +%Y-%m-%dT%H:%M:%SZ"), and good/bad verdict examples — matching the anchor for specific guidance covering common cases.

5 / 5

Workflow Clarity

Three phases are explicitly sequenced with real validation gates: "Never modify rules automatically. Always require user approval.", a cross-batch merge that re-checks the 2+ skills requirement with combined evidence, and a four-point all-must-be-true extraction checklist, matching the explicit-validation-and-checklists anchor.

5 / 5

Progressive Disclosure

Deterministic collection logic is appropriately split into two real scripts referenced by exact one-level-deep paths (both verified to exist in the bundle), but the ~50-line illustrative end-to-end example is inline operational-style content that could live in a separate file — a minor organization gap versus the ideally-split anchor.

4 / 5

Total

18

/

20

Passed

Description

71%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.

A specific, action-oriented description that clearly communicates what the skill does and occupies a distinct niche. Its main weakness is the complete absence of "when to use" trigger guidance, which both caps completeness and limits natural trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions updating, maintaining, or consolidating rules, or after a skills audit reveals repeated patterns".

Include natural user phrasings like "extract principles", "promote skill patterns to rules", or "rules maintenance" to broaden trigger-term coverage.

Mention the periodic-maintenance trigger from the body ("monthly or after installing new skills") in the description so timing-based invocations match.

DimensionReasoningScore

Specificity

Lists multiple concrete actions covering the full workflow — "Scan skills", "extract cross-cutting principles", "distill them into rules", "append, revise, or create new rule files" — matching the comprehensive-coverage anchor rather than the minor-gaps anchor below it.

5 / 5

Completeness

The "what" is clear and specific, but there is no "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; it is not 4 because the "when" is not even weakly implied.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("skills", "principles", "rules", "append", "revise") but common variations users might say ("update rules", "maintain", "consolidate", "patterns") are missing, fitting the good-coverage-with-a-few-missing anchor rather than the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The skills-to-rules promotion niche is clearly carved ("extract cross-cutting principles and distill them into rules"), but the body references a closely related "skill-stocktake" skill and rules-maintenance territory overlaps with adjacent skills, giving minor overlap risk rather than minimal.

4 / 5

Total

16

/

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.

Validation — 15 / 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

valeriibeck-star/claude-skills

Path

skills/rules-distill/SKILL.md

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.