contributors-update

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

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/contributors-update/SKILL.md

Quality

Content

100%Weight 40%Scale 1-3

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 tight, fully executable six-step workflow with concrete commands and thorough validation and approval checkpoints. It assumes Claude's competence and avoids both padding and unnecessary file splitting.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven, with no padding explaining what git, PRs, or a README are; operational prose (e.g. the untrusted-data warning) earns its place rather than re-teaching known concepts.	3 / 3
Actionability	It provides fully executable bash and `gh pr list` commands with the only placeholder (YYYY-MM-DD) clearly flagged, making the workflow copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	The six-step sequence has explicit validation checkpoints — a dirty-check stop, a user approval gate, a staged-change assertion (`test ... = "README.md"`), ff-only re-pull, and a conflict re-approval loop — satisfying the destructive/batch feedback-loop requirement.	3 / 3
Progressive Disclosure	No bundle files are provided; the single self-contained SKILL.md is organized into clearly headed sections with no wall of text or nested references, which is appropriate for this focused single-workflow skill.	3 / 3
	Total	12 / 12 Passed

Description

60%Weight 40%Scale 1-3

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 action-oriented about its niche, but lacks an explicit "Use when..." trigger and broader natural keyword coverage. Adding a usage clause and common user phrasings would lift the weaker dimensions.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when updating the README contributors list from recently merged PRs, or when the user asks to add new contributors.'

Include common natural variations like 'add contributors', 'new contributors', or 'update contributors list' so users' phrasing matches the description.

Rephrase in third-person action form and lead with the trigger context to sharpen distinctiveness from generic README-editing skills.

Dimension	Reasoning	Score
Specificity	The description names multiple concrete actions in a specific domain — "Find merged PR authors missing from README" and "update the contributors list" — matching the anchor for listing several specific concrete actions rather than vague language.	3 / 3
Completeness	It clearly answers what the skill does, but provides no "Use when..." trigger clause; "after approval" is a procedural precondition, not a usage trigger, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	It includes relevant terms ("merged PR authors", "README", "contributors list") but omits common natural variations a user would actually say, such as "add contributors" or "new contributors".	2 / 3
Distinctiveness Conflict Risk	The contributors-from-merged-PRs niche is fairly specific, but the absence of explicit distinct triggers means it could still overlap with generic README-editing skills.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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
Path: .claude/skills/contributors-update/SKILL.md
Commit: 01964cc

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.