CtrlK
BlogDocsLog inGet started
Tessl Logo

format-source-add-rule

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

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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

100%

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

The content is lean, concrete, and well-sequenced with an explicit validate-fix-retry loop and copy-paste-ready templates, all without padding or explaining concepts Claude already knows. It is a strong, self-contained instruction skill.

DimensionReasoningScore

Conciseness

The body is lean and task-focused with concrete templates; it assumes Claude's competence and never explains basic concepts like git diffs or formatting, matching the 'lean and efficient' anchor.

3 / 3

Actionability

Provides copy-paste-ready guidance — an exact markdown rule template, concrete file paths, and a literal commit-message format — fully executable rather than pseudocode.

3 / 3

Workflow Clarity

A clearly sequenced Inspect→Check→Write→Self-Test→Commit flow with an explicit validation feedback loop ('If the rule does not produce an equivalent change, revise and repeat') and stop-and-ask checkpoints.

3 / 3

Progressive Disclosure

A self-contained single-purpose skill (~61 lines) with well-organized Inputs/Workflow sections and no nested references; per the simple-skills note this can score 3 with clean organization alone.

3 / 3

Total

12

/

12

Passed

Description

57%

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 is specific and distinctive but describes only one action and, critically, omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause and a broader action list would raise the completeness and specificity scores.

Suggestions

Append an explicit trigger clause, e.g. 'Use when you want to encode a formatting convention spotted in someone's commit into the format-source skill.'

Expand the action list beyond a single verb — e.g. 'Inspect a commit, extract a formatting pattern, and append a numbered rule with diff examples.'

Add natural user phrasings like 'formatting convention' or 'formatting rule from a commit' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the concrete action ('Add a new rule') and source ('derived from a Git commit') but only a single action — not the multiple concrete actions the top anchor calls for.

2 / 3

Completeness

It clearly states what the skill does but lacks any explicit 'Use when...' trigger guidance, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

'Git commit' and 'rule' are relevant keywords, but common user-facing phrasings ('format my code', 'add a formatting convention') are absent, matching the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

Tied to a specific skill ('format-source') and a Git-commit-derived workflow, giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

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.

Validation16 / 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.