CtrlK
BlogDocsLog inGet started
Tessl Logo

format-source-add-rule

Add a new rule to the format-source skill, derived from a Git commit.

62

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/format-source-add-rule/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean, single-purpose workflow: concrete templates, explicit validation with a feedback loop, and clear sequencing. The only meaningful gap is the absence of one worked example of a finished rule and the implicit reliance on the format-source skill's own interface for the self-test step.

DimensionReasoningScore

Conciseness

The ~50-line body is lean and instructional throughout: exact file paths, an exact template, and targeted anti-bias guidance ("Do not bias toward Java", abstract-identifier requirements) with no explanations of concepts Claude already knows. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Guidance is mostly executable: exact paths (`.claude/skills/format-source/SKILL.md`), a copy-paste markdown template, a commit message format, and a concrete self-test procedure. It falls short of anchor 5 because no filled-in example rule is shown and the self-test relies on the reader knowing how to scope `/format-source` to specific files and manual rules only.

4 / 5

Workflow Clarity

Five clearly sequenced steps (inspect, dedupe, write, self-test, commit) with explicit stop-and-ask checkpoints for ambiguity and a full validate-fix-retry feedback loop ("revise the rule and repeat until it does") before committing. This matches anchor 5's explicit validation with error-recovery loops.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (none exist in the bundle), and is cleanly organized into Inputs and a five-step Workflow with headings. Per the simple-skill guideline, well-organized sections alone warrant a 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 states a clear, concrete capability but is minimal: it answers "what" well while entirely omitting "when". Adding an explicit trigger clause and a few natural synonyms would materially improve trigger quality and completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to encode a formatting convention spotted in a commit, or asks to add a rule to format-source."

Include natural trigger variations such as "formatting convention", "style rule", or "derive a rule from this commit" so users' phrasing matches without knowing the skill name.

Optionally mention the input requirement (a commit SHA) and the outcome (a self-tested, committed rule) to round out the capability coverage.

DimensionReasoningScore

Specificity

"Add a new rule to the format-source skill, derived from a Git commit" names the domain and one concrete action with its input source, but does not list several specific actions. It matches anchor 3 (1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

The "what" is clear (add a rule to the format-source skill derived from a commit), but there is no "Use when..." clause or any equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. It is not 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

The description contains relevant keywords ("rule", "format-source", "Git commit") but misses common natural variations a user would say, such as "formatting convention", "style rule", or "derive a rule from a commit". This fits anchor 3 (some relevant keywords, missing variations) rather than 4's good coverage with only a few gaps.

3 / 5

Distinctiveness Conflict Risk

The niche is specific (rule derivation for the named format-source skill from Git commits), so overlap risk is minor and limited to closely related skill-editing skills. It is not 5 because the description lacks explicit distinct trigger phrases that would fully minimize wrong-skill triggering.

4 / 5

Total

13

/

20

Passed

Validation

100%

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
liferay/liferay-portal
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.