End-to-end GitHub repository maintenance for open-source projects. Use when asked to triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository. Triggers include "triage", "maintain", "review PRs", "analyze issues", "repo maintenance", "what needs attention", "open source maintenance", or any request to understand and act on GitHub issues/PRs. Supports human-in-the-loop workflows with persistent memory across sessions.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific concrete actions, comprehensive trigger terms that users would naturally say, explicit 'Use when' and 'Triggers include' clauses, and a clearly defined niche in GitHub/open-source maintenance. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('triage issues, review PRs, analyze contributor activity, generate maintenance reports') and when ('Use when asked to...' with explicit 'Triggers include' clause listing specific keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'triage', 'maintain', 'review PRs', 'analyze issues', 'repo maintenance', 'what needs attention', 'open source maintenance'. Includes both technical and conversational phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on GitHub repository maintenance for open-source projects. The specific triggers like 'triage', 'repo maintenance', and 'open source maintenance' create a distinct domain unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-crafted skill that demonstrates mastery of all evaluation dimensions. It provides a complete operational framework for repository maintenance with clear workflows, explicit validation gates, and appropriate progressive disclosure through referenced files. The content is dense yet navigable, with every section serving a clear purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and bullet points to convey information densely. It assumes Claude's competence and avoids explaining basic concepts like what GitHub is or how PRs work. | 3 / 3 |
Actionability | Provides concrete, executable commands (npx tsx scripts), specific file paths, clear citation formats, and explicit workflow stages. The script usage section is copy-paste ready with multiple flag examples. | 3 / 3 |
Workflow Clarity | The 6-stage workflow is clearly sequenced with explicit gates and checkpoints. The 'Gates (Read-Before-Acting)' section provides validation stops, and human approval requirements create clear feedback loops for risky operations. | 3 / 3 |
Progressive Disclosure | Excellent structure with a Reference Router table that explicitly tells when to load each reference file. Content is appropriately split between the main skill and referenced files (workflow.md, decision-framework.md, etc.) with clear one-level-deep navigation. | 3 / 3 |
Total | 12 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
8de01ac
Table of Contents
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.