CtrlK
BlogDocsLog inGet started
Tessl Logo

open-source-maintainer

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.

75

Quality

94%

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

86%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 body is a tight, well-organized operating manual that uses a reference router and gates to keep the overview lean while routing detail to real bundle files. It is highly actionable for the scripted steps and well-sequenced, with only minor gaps in execution-stage detail and triage-output validation.

Suggestions

Add an explicit verify/validate step after the Stage 1 triage run (e.g., confirm the report folder and expected files exist before analyzing) to strengthen the feedback loop and push workflow_clarity to 5.

Inline one or two concrete examples of analysis output (e.g., a sample intent-extraction note) so the Stage 2–3 steps are executable without loading a reference, narrowing the actionability gap.

Consider collapsing the Gates section into the Reference Router table or cross-linking them to remove the mild duplication of the same reference paths.

DimensionReasoningScore

Conciseness

Lean and well-structured body that assumes Claude's competence; it establishes a skill-specific operating contract rather than explaining known concepts, and every section earns its tokens. The only mild redundancy (Reference Router table vs. Gates) is justified by distinct framing.

5 / 5

Actionability

Provides copy-paste-ready script commands with concrete flags (--delta, --keep, --datetime, --config), a precise citation format, and a state-file table, but the analysis/execution stages delegate specifics to references, leaving minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced Stage 0–6 workflow with explicit STOP gates and a human-approval checkpoint before execution; not a 5 because the batch triage step lacks an explicit verify-output feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with one-level-deep, well-signaled references via the Reference Router table and Gates section; all 8 referenced files exist in references/ and content is appropriately split for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

100%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 is a strong, concise statement that names the domain, enumerates concrete capabilities, provides explicit 'Use when' triggers with natural synonyms, and stakes out a distinct niche. Voice is third-person imperative throughout, satisfying the rubric's voice requirement.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'triage issues, review PRs, analyze contributor activity, generate maintenance reports, or maintain a repository' — giving comprehensive coverage of the maintenance domain rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' ('End-to-end GitHub repository maintenance for open-source projects') and 'when' ('Use when asked to...') with concrete trigger phrases; voice is third-person imperative, so no penalty applies.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and likely user phrasings: 'triage', 'maintain', 'review PRs', 'analyze issues', 'repo maintenance', 'what needs attention', 'open source maintenance'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (open-source GitHub maintenance) with distinct, specific triggers unlikely to fire for unrelated skills; minimal overlap risk.

5 / 5

Total

20

/

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
numman-ali/n-skills
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.