CtrlK
BlogDocsLog inGet started
Tessl Logo

contributors-update

Find merged PR authors missing from README and update the contributors list after approval

60

Quality

71%

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/contributors-update/SKILL.md
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.

The content is a tightly written, fully executable workflow with strong validation gates and error-recovery loops appropriate to a destructive direct-push operation. Its only soft spot is progressive disclosure, where the modest length and absence of references keep it at a 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of git/PR basics), with only minor operational prose such as the AGENTS.md documentation-only-exception note that could be trimmed slightly.

4 / 5

Actionability

Fully executable, copy-paste-ready bash commands appear throughout (git worktree list, gh pr list, git log, staged-change test), with the single placeholder YYYY-MM-DD explicitly flagged for substitution.

5 / 5

Workflow Clarity

Six clearly sequenced steps include explicit validation checkpoints (dirty-checkout stop, ff-only pull, `test git diff --cached = README.md`), an approval gate, and an error-recovery feedback loop for master drift on this destructive direct-push operation.

5 / 5

Progressive Disclosure

No bundle files exist; the ~100-line body is well-organized into numbered sections as a single cohesive workflow that genuinely needs no external splitting, landing just below the reference-based 5 anchor.

4 / 5

Total

18

/

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 clearly communicates the skill's purpose and concrete actions but omits any 'when to use' trigger guidance, capping its completeness. It is specific and distinct yet relies on somewhat technical phrasing rather than natural user terminology.

Suggestions

Append an explicit trigger clause, e.g. 'Use when refreshing the contributors list in a README after a batch of PRs has merged'.

Add natural synonyms users would say ('add new contributors', 'update contributors') alongside 'merged PR authors'.

Consider adding one more concrete action (e.g. 'preview additions for approval') to lift specificity from 1-2 to several actions.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Find merged PR authors missing from README' and 'update the contributors list after approval'), matching the 1-2 concrete actions anchor; not 'several' so it stays at 3.

3 / 5

Completeness

Clearly states the 'what' but provides no 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant keywords ('merged PR authors', 'README', 'contributors list', 'approval') but they skew technical and lack common natural variations like 'add new contributors', fitting the some-relevant-keywords-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

Targets a narrow niche (contributors-list sync from merged PRs) with minimal conflict risk, though it lacks explicit distinguishing trigger phrases that would push it to a 5.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
homeassistant-ai/ha-mcp
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.