Name: ac-autonomous-orchestrator
Rating: 57.599999999999994 (1 reviews)
Author: fernandezbaptiste

ac-autonomous-orchestrator

Main orchestrator for autonomous coding operations. Use when running autonomous sessions, coordinating components, managing the full lifecycle, or orchestrating implementations.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ac-autonomous-orchestrator/SKILL.md

The canonical home for this skill is ac-autonomous-orchestrator in fernandezbaptiste/Skrillz

Quality

Content

68%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 concise and action-oriented with executable Quick Start code and a real referenced script, but its multi-step workflow is presented as an abstract diagram lacking explicit validation feedback loops. Structure and progressive disclosure are good with minor organization gaps.

Suggestions

Expand the Orchestration Flow into concrete commands with an explicit validation feedback loop (e.g., 'if VALIDATE fails: fix and re-run VALIDATE; only then COMMIT') to lift workflow_clarity past the destructive-ops cap.

Replace the one-line 'Integration' section with concrete detail on which AC skills are coordinated and how they are invoked, or remove it if nothing actionable can be stated.

Drop the redundant restatement of purpose in the body since it duplicates the frontmatter description, saving tokens.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with an executable Quick Start, but it re-states the purpose already in the frontmatter ('Main orchestrator for autonomous coding operations' and the Purpose paragraph), a minor redundancy that could be trimmed.	4 / 5
Actionability	Quick Start provides executable, copy-paste-ready Python referencing the real bundled script, but the Orchestration Flow is a high-level ASCII diagram rather than runnable commands, leaving minor gaps versus full coverage of common cases.	4 / 5
Workflow Clarity	The flow lists a clear 6-step sequence including a named VALIDATE step, but for destructive/batch autonomous operations (git commit, code execution) it shows no explicit error-recovery feedback loop, so the validation cap of 3 applies.	3 / 5
Progressive Disclosure	Content is organized into clear sections (Purpose, Quick Start, Orchestration Flow, Integration, API Reference) with a one-level-deep pointer to the verified scripts/autonomous_orchestrator.py, but the 'Integration' section is a single vague line and no advanced-usage reference exists.	4 / 5
	Total	15 / 20 Passed

Description

62%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 third-person, has an explicit 'Use when' clause, and names a clear niche, but its action verbs and trigger phrases are abstract rather than concrete. It is solid but stops short of the comprehensive, natural-language triggers of the top anchors.

Suggestions

Replace abstract verbs with concrete operations (e.g., 'plans features, runs TDD loops, validates QA, and commits changes') to lift specificity.

Add natural trigger phrases and synonyms users would actually say, such as 'autonomous coding session', 'unattended feature build', or 'self-driving dev loop'.

Tighten the 'when' clause with file/state triggers (e.g., 'Use when starting an unattended build session or resuming a paused autonomous run') to reduce overlap with sibling AC skills.

Dimension	Reasoning	Score
Specificity	Names the domain (autonomous coding) and several actions — 'coordinating components, managing the full lifecycle, or orchestrating implementations' — but these are abstract verbs rather than concrete operations, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states a clear 'what' ('Main orchestrator for autonomous coding operations') and an explicit 'Use when...' clause with multiple trigger phrases, but the triggers are somewhat abstract rather than fully concrete, placing it just below the top anchor.	4 / 5
Trigger Term Quality	Relevant keywords like 'autonomous sessions', 'coordinating components', and 'full lifecycle' appear, but it misses common variations, synonyms, or concrete artifacts users might say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Main orchestrator' carves a distinct niche, but the broad 'autonomous coding operations' scope creates minor overlap risk with closely related AC skills, matching the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: fernandezbaptiste/Skrillz
Path: .claude/skills/ac-autonomous-orchestrator/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.