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

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

Quality

Content

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

A mature, well-structured orchestration skill with strong workflow sequencing, explicit validation checkpoints, and concrete actionable guidance. Its weaknesses are mild verbosity from repeated single-item exclusions and a long dense body that could split some specialized policy into references.

Dimension	Reasoning	Score
Conciseness	Dense, directive prose that assumes Claude's competence (no explanations of git/PRs/CI) with every line operational, though some single-item exclusions and 'Do not...' rules recur across sections and could be tightened.	4 / 5
Actionability	Highly concrete for an instruction-only skill: specific commands ('git status -sb', 'scripts/pr review/artifact/prepare/sync/merge'), explicit triage categories with criteria, and a structured decision-brief and landing checklist, with minor gaps where guidance is necessarily conditional/policy-based.	4 / 5
Workflow Clarity	A clearly sequenced control-plane workflow (classify -> scope -> preserve -> triage -> execute/public gate -> monitor -> land -> report) with explicit validation checkpoints (verify clean state, verify worker permissions, exact-head CI green, fresh autoreview), feedback loops, and checklists for a batch/destructive process.	5 / 5
Progressive Disclosure	Well-organized sections with one clearly signaled one-level-deep reference (references/non-majority-repositories.md) that correctly offloads the large repo-data table, but the ~190-line body is dense and specialized sections like OpenClaw Queue Mode could arguably be split out for a cleaner overview.	4 / 5
	Total	17 / 20 Passed

Description

78%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, well-scoped description with a clear niche and strong disambiguation against single-item work. Its main weakness is expressing the trigger only as a negative exclusion rather than a positive 'Use when...' clause, and omitting common synonyms (queue, sweep, batch, triage) that appear in the body.

Suggestions

Add a positive 'Use when...' clause listing the natural trigger phrases (e.g., 'Use when coordinating multiple issues, PRs, repositories, a queue, sweep, batch, or portfolio triage').

Broaden trigger terms to include synonyms users actually say: queue, sweep, batch, portfolio, maintainer night, triage.

Keep the 'Do not use for one issue or PR' exclusion but pair it with the positive trigger so the activation condition is stated affirmatively.

Dimension	Reasoning	Score
Specificity	Names the domain ('maintainer issues, PRs, or repositories') and several concrete orchestration actions ('bounded workers, serialized public actions, and clear owner decisions'), with only minor coverage gaps.	4 / 5
Completeness	Clearly states what the skill does and conveys when via the multiple-vs-single contrast plus the explicit exclusion 'Do not use for one issue or PR', but the 'when' is a negative statement rather than a positive 'Use when...' clause.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('maintainer issues', 'PRs', 'repositories') with good coverage, though common synonyms like queue, sweep, batch, triage, or portfolio are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (multi-item orchestration) with a distinct 'multiple' trigger and an explicit 'Do not use for one issue or PR' disambiguation that minimizes overlap with ordinary maintainer/review 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: 15bcfe3

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