CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/maintainer-orchestrator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, largely actionable orchestration policy with genuine validation gates around its risky batch operations. Its main costs are the repetition of the same scope-authority guardrail across at least five sections and some repo-specific or template content inlined that could live in reference files.

Suggestions

Consolidate the repeated scope-authority rules ('no heartbeat/ledger/refill/release merely from invocation') into a single 'Scope Authority' section and reference it from the Monitoring, Reporting, Landing, and Releases sections instead of restating them.

Move the OpenClaw-specific queue policy (and optionally the owner-decision brief template) into a file under references/ and keep a one-line pointer in SKILL.md, shortening the body and improving progressive disclosure.

Add an explicit failure-recovery loop to the Landing Standard (e.g., what to do when exact-head CI is red or autoreview reports actionable findings), and briefly define where the 'autoreview' gate comes from so the step is executable.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no explanation of git, CI, or PR basics), but the scope-authority guardrail is repeated across many sections — 'never created merely because this skill was invoked', 'Do not automatically continue into dependency maintenance... Refill only when the user explicitly requested an ongoing queue', 'A queue invocation does not imply release authority', 'Do not create or maintain that log for one-shot batches' — where a single consolidated authority section could be tightened considerably.

3 / 5

Actionability

Concrete, executable guidance dominates: 'Record git status -sb, branch, upstream, HEAD, staged/unstaged/untracked state, and ahead/behind counts', 'Fetch current refs. On a clean default branch, fast-forward pull and verify it remains clean', named commands like scripts/pr, the decision-brief field list, and explicit triage categories. As an instruction-only orchestration skill this is actionable with only minor gaps (e.g., the 'autoreview' step is referenced but not defined here).

4 / 5

Workflow Clarity

The lifecycle is clearly sequenced (activation gate → scope contract → workers → repository preservation → triage → execution/public gate → monitoring → landing → reporting) with real validation checkpoints for its batch/destructive operations: the numbered repository-preservation procedure with stop conditions, the Landing Standard's explicit gates (reproduced symptom, regression coverage, exact-head CI green, 'fresh autoreview with no accepted/actionable findings'), and 'Refresh item and worker state immediately before asking.' Minor gaps remain, e.g. no explicit recovery loop if landing gates fail.

4 / 5

Progressive Disclosure

Good structure with clear section headers and a real, clearly signaled one-level-deep reference ('exclude archived repositories and the repositories listed in references/non-majority-repositories.md', which exists in the bundle). Minor organization gaps: the OpenClaw-specific queue policy and the owner-decision brief template are candidate content for separate reference files in a ~190-line SKILL.md.

4 / 5

Total

15

/

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 strong, specific description with good natural maintainer vocabulary and excellent distinctiveness from single-item skills. Its main weakness is that the trigger guidance is only stated as an exclusion rather than an explicit positive 'Use when...' clause, and it omits several queue/sweep/batch trigger words that its own body recognizes.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'Coordinate multiple maintainer issues, PRs, or repositories', 'bounded workers', 'serialized public actions', and 'clear owner decisions' — which are specific and actionable, though terms like 'bounded workers' are somewhat abstract and coverage of the actual workflow (triage, landing, monitoring) is not comprehensive.

4 / 5

Completeness

The 'what' is clear (coordinate multiple maintainer issues/PRs/repos with workers, serialized public actions, owner decisions) and a 'when' exists, but it is expressed only negatively ('Do not use for one issue or PR') rather than as an explicit positive 'Use when...' trigger clause; the positive condition must be inferred.

4 / 5

Trigger Term Quality

Natural maintainer vocabulary is present ('maintainer issues', 'PRs', 'repositories', 'multiple'), which users would plausibly say. A few natural trigger phrases the body itself identifies — 'queue', 'sweep', 'batch', 'portfolio', 'parallel workstreams' — are missing from the description.

4 / 5

Distinctiveness Conflict Risk

The multi-item coordination niche is distinct and the explicit negative boundary ('Do not use for one issue or PR') sharply separates it from ordinary single-item maintainer/review/release skills, giving minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

steipete/agent-scripts

Path

skills/maintainer-orchestrator/SKILL.md

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.