detail-create-rules

Interactively create a new Detail rule for a repository — gather context, submit the creation request, wait for completion, review the results, and pull them locally. Use when asked to "create a rule", "add a rule", "propose rules", "create/propose a Detail rule", or similar.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%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 tight, highly actionable skill body that sequences a five-step CLI workflow with executable commands and a polling/failure checkpoint. The main gap is the absence of a rigorous validate→retry loop around the batch rule-pull write step.

Suggestions

Add an explicit validation/feedback loop to Step 5: after pulling each rule, verify the file exists at the expected path and retry or report if a pull fails, rather than only confirming at the end.

In Step 3, specify a maximum poll count or timeout so the loop cannot run indefinitely on a stuck 'pending' status.

Surface the request-id format and default output directory earlier (e.g., in a short 'Key outputs' note) so downstream steps reference them without re-deriving.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no concept over-explanation — every line is an executable instruction, prerequisite, or command, matching the lean-and-efficient anchor; not 4 because there are no padded sections to trim.	5 / 5
Actionability	Fully executable copy-paste-ready CLI commands with concrete flags and placeholders ('detail rules create [--description ...] [--bug-ids ...]', 'detail rules requests show <request_id>') covering the common cases; not 4 because guidance is complete rather than having minor gaps.	5 / 5
Workflow Clarity	Clear Steps 1–5 sequence with a status-polling checkpoint and explicit failure handling ('If it fails, report the error... and stop') in Step 3; not 5 because Step 5's batch file-write only lightly verifies output ('confirm the files written') without a validate→retry feedback loop, and not 3 because most checkpoints are present.	4 / 5
Progressive Disclosure	Well-organized single-file sections with clear headers and no nested references; no bundle files exist so structure is appropriate; not 5 because the body (~70 lines) slightly exceeds the under-50-line simple-skill threshold that would permit a 5 on organization alone.	4 / 5
	Total	18 / 20 Passed

Description

88%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 strong, well-structured description that clearly states both the capability (a five-step rule-creation workflow) and explicit trigger conditions with natural phrasing. Its only weakness is mild overlap risk from generic trigger terms like 'create a rule'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions spanning the full lifecycle — 'gather context, submit the creation request, wait for completion, review the results, and pull them locally' — matching the comprehensive-coverage anchor; not 4 because coverage is broad rather than having minor gaps.	5 / 5
Completeness	Explicitly answers both what (create a Detail rule via five concrete steps) and when ('Use when asked to...') with concrete trigger phrases, matching the anchor; not 4 because the 'when' is fully explicit rather than only weakly specified.	5 / 5
Trigger Term Quality	Provides natural trigger phrases with synonyms ('create a rule', 'add a rule', 'propose rules', 'create/propose a Detail rule') but a few common variants are absent; not 5 because coverage is good rather than exhaustive and not 3 because several natural terms are present.	4 / 5
Distinctiveness Conflict Risk	The 'Detail rule' niche is mostly distinct, but generic triggers like 'create a rule'/'add a rule' carry minor overlap risk with other rule-creation skills; not 5 because of that residual overlap and not 3 because the Detail-specific trigger anchors it clearly.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: usedetail/cli
Path: .claude/skills/detail-create-rules/SKILL.md
Commit: 5e8ba56

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.