CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-rule

Use when found gap or repetative issue, that produced by you or implemenataion agent. Esentially use it each time when you say "You absolutly right, I should have done it differently." -> need create rule for this issue so it not appears again.

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/customaize-agent/skills/create-rule/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 content is a thorough, actionable guide with strong templates, executable examples, and a well-sequenced workflow including validation and refinement loops. Its main weaknesses are moderate verbosity from a duplicated official-documents section and the absence of any bundle files to offload detail.

Suggestions

Remove or condense the trailing 'Claude Code Official Rules Guidlines' section, which duplicates the path-scoping and setup guidance already covered earlier in the skill.

Move the large complete examples and the official-guidelines material into a references/ file (e.g. RULES-GUIDE.md) and link to it from SKILL.md to improve progressive disclosure.

Trim explanatory prose around concepts Claude already knows (e.g. what rules vs skills are) to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient and well-organized, but the trailing 'Claude Code Official Rules Guidlines' section largely restates earlier material (setup, path-scoping, user-level rules), adding padding that could be trimmed.

3 / 5

Actionability

It provides copy-paste-ready templates (frontmatter, Incorrect/Correct structure), multiple complete executable code examples, and a concrete checklist, covering the common rule-creation cases.

5 / 5

Workflow Clarity

The 7-step process is clearly sequenced with an explicit validation step (Step 6) and a Decompose-Filter-Reweight refinement feedback loop (Step 7) that supports error recovery and iteration.

5 / 5

Progressive Disclosure

Section structure is clear, but the skill is a single ~520-line file with no references/ directory and no signaled links to separate detail files, so content that could be split out (e.g. the official-guidelines section, full examples) is inlined.

3 / 5

Total

16

/

20

Passed

Description

48%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 communicates a clear trigger scenario but is hampered by vague action language, spelling/grammar errors, and an only-implied statement of what the skill actually does. Tightening the wording and explicitly stating the concrete actions would substantially raise the score.

Suggestions

Add a concrete 'what' clause listing the actions the skill performs, e.g. 'Creates .claude/rules files using contrastive Incorrect/Correct examples to prevent recurring agent mistakes.'

Fix spelling and phrasing ('repetative', 'implemenataion', 'absolutly') so trigger terms read naturally and reliably match user language.

Lead with an explicit 'Use when...' clause followed by the concrete capabilities, mirroring the structure of the rubric's strong examples.

DimensionReasoningScore

Specificity

The description names the domain (creating rules) but the only concrete action stated is 'need create rule', which is generic and lacks the specific actions involved in rule creation.

2 / 5

Completeness

It gives a clear 'when' (after noticing a recurring gap or self-correction) but the 'what' is only weakly implied ('need create rule') rather than explicitly stating what the skill does.

3 / 5

Trigger Term Quality

It includes a recognizable natural trigger ('You absolutly right, I should have done it differently') alongside 'gap or repetative issue', but common synonyms and variations are missing and phrasing is informal.

3 / 5

Distinctiveness Conflict Risk

It targets a distinct niche (.claude/rules creation) with a fairly specific trigger, leaving only minor overlap risk with adjacent skills.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (612 lines); consider splitting into references/ and linking

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

plugins/customaize-agent/skills/create-rule/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.