CtrlK
BlogDocsLog inGet started
Tessl Logo

contributors-update

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

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary instruction-only skill body: concrete executable commands, a tightly sequenced workflow with validation and rollback checkpoints at every risky step, and disciplined token efficiency. The untrusted-PR-metadata note is a justified, behavior-changing addition rather than padding.

DimensionReasoningScore

Conciseness

The body is lean and command-first: every line carries non-obvious workflow detail (marker-commit cutoff with 1-week overlap margin, ff-only pulls, staged-only guard) and nothing explains concepts Claude already knows. No padding is detectable to trim.

5 / 5

Actionability

Guidance is fully executable and copy-paste ready, from the worktree-locating pipeline and the gh pr list command with pushed-down search filter and --jq projection, to the exact commit message with the [contributors-updated] marker and the test-based staged-change verification.

5 / 5

Workflow Clarity

Six clearly sequenced steps with explicit validation checkpoints and feedback loops throughout: stop on dirty tree, user approval gate before any edit, re-pull with --ff-only immediately before commit, staged-file equality check, git diff --cached --check, and a stop/recompute/re-approve path if master moved. The batch/direct-push validation cap is satisfied, not violated.

5 / 5

Progressive Disclosure

The skill is a single linear workflow (~100 lines) with well-organized numbered sections and no content that belongs in separate files; there are no bundle references to verify, and nothing is inlined that should be split out.

5 / 5

Total

20

/

20

Passed

Description

65%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 specific, distinctive, appropriately concise description whose only significant weakness is the absence of any 'when to use' trigger guidance. Adding a Use-when clause and a couple of natural synonyms would lift the two weakest dimensions.

Suggestions

Append a trigger clause such as: 'Use when the user asks to update contributors, credits, or the authors list after merged PRs, or mentions the [contributors-updated] marker.'

Broaden trigger coverage with natural synonyms users might say, e.g. 'credits', 'acknowledgments', or 'who contributed since the last update'.

Optionally surface one more concrete action (e.g. writing one-line contribution descriptions or creating the marker commit) to round out capability coverage.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions ("Find merged PR authors missing from README", "update the contributors list"), but does not list several actions or comprehensive coverage, matching the 1-2-concrete-actions anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present ("merged PR authors", "README", "contributors list"), giving good keyword coverage, though a few natural synonyms like "credits" or "acknowledgments" are missing, keeping it below the comprehensive-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (post-merge contributors-list maintenance) with distinct trigger terms like "merged PR authors" and "contributors list", so the risk of triggering the wrong skill is minimal.

5 / 5

Total

15

/

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