maintainer-orchestrator

Coordinate multiple maintainer issues, PRs, or repositories with bounded workers, serialized public actions, and clear owner decisions. Do not use for one issue or PR.

Quality

69%

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 ./skills/maintainer-orchestrator/SKILL.md

Quality

Content

75%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 skill body is a well-structured, actionable control-plane document with clear workflows and validation checkpoints for destructive and batch operations. It is slightly verbose from cross-section restatement and would benefit from tighter consolidation.

Suggestions

Consolidate the repeated one-shot-vs-persistent-portfolio distinction into a single canonical statement to trim restated content.

Promote the activation gate into a short scannable checklist so the single-item vs orchestration decision is faster to apply.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence without explaining known concepts, though the one-shot-vs-persistent distinction is restated across several sections and could be consolidated.	4 / 5
Actionability	Concrete commands like 'git status -sb', specific gating rules, and an exact landing checklist give mostly executable guidance; as an instruction-only skill the absence of code is not penalized and the directives are specific.	4 / 5
Workflow Clarity	Multi-step processes like Repository Preservation (numbered 1-5 with an explicit stop-for-owner checkpoint) and the Landing Standard checklist are clearly sequenced with validation, satisfying the destructive/batch feedback requirement and staying above the cap of 3.	4 / 5
Progressive Disclosure	Content is well-organized into focused sections with a single real one-level-deep reference (references/non-majority-repositories.md) that is clearly signaled, with only minor organization gaps in a long control-plane document.	4 / 5
	Total	16 / 20 Passed

Description

63%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 specific and clearly distinct with strong concrete actions and a helpful negative boundary, but it omits an explicit positive 'Use when...' trigger clause, leaving the activation condition only implied.

Suggestions

Add an explicit positive trigger clause such as 'Use when coordinating multiple independent issues, PRs, or repositories' to make the 'when' explicit rather than implied.

Include a few natural phrasings a user would actually say (e.g. 'maintainer queue', 'portfolio sweep', 'batch triage') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the domain — 'bounded workers', 'serialized public actions', and 'clear owner decisions' — giving comprehensive coverage rather than a single generic verb.	5 / 5
Completeness	The 'what' is clear, but the 'when' is only weakly implied via the negative trigger 'Do not use for one issue or PR'; there is no explicit 'Use when...' clause, so completeness is capped at 3 per the rubric.	3 / 5
Trigger Term Quality	Natural user terms like 'maintainer issues', 'PRs', and 'repositories' appear, but it lacks synonyms or file-extension-style variations and relies on the domain nouns rather than the phrasings a user would naturally say.	4 / 5
Distinctiveness Conflict Risk	The multi-item orchestration niche is clearly bounded and the explicit 'Do not use for one issue or PR' boundary sharply reduces overlap with single-item maintainer skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: steipete/agent-scripts
Path: skills/maintainer-orchestrator/SKILL.md
Commit: 2b082d9

Reviewed: 2 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.