Name: ac-master-controller
Rating: 55.2 (1 reviews)
Author: fernandezbaptiste

ac-master-controller

Master controller for complete autonomous operation. Use when starting full autonomous projects, managing end-to-end workflow, controlling autonomous lifecycle, or running complete implementations.

Quality

61%

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-master-controller/SKILL.md

The canonical home for this skill is ac-master-controller 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 a lean overview with concrete quick-start code and a well-signaled reference to a real bundled script, but its autonomous-loop workflow lacks validation checkpoints and a feedback loop, capping workflow clarity.

Suggestions

Add explicit validation checkpoints and a feedback loop to the workflow (e.g. after LOOP: validate output, on failure fix and re-run, only then proceed to REPORT), with the concrete command or method call for each step.

Make the Quick Start fully copy-paste ready by defining project_dir (e.g. 'project_dir = Path(".")') and showing the run_project return handling.

Expand the API Reference beyond a single pointer — list the key MasterController methods/run_project parameters inline so the skill is usable without opening the script.

Dimension	Reasoning	Score
Conciseness	The body is lean — compact Quick Start code, a terse workflow diagram, and a one-line API pointer — with only minor redundancy in the 'Purpose' section restating the header/description, matching the 'efficient; minor instances that could be trimmed' anchor.	4 / 5
Actionability	The Quick Start gives concrete, mostly executable Python (import path, constructor, run_project with spec/objective kwargs), but project_dir is undefined and only one example is shown, so it stops just short of fully copy-paste-ready coverage.	4 / 5
Workflow Clarity	The SETUP→SPEC→LOOP→VERIFY→REPORT sequence is clearly ordered, but this is an autonomous LOOP/batch operation with no validate→fix→retry feedback loop or checkpoint commands; per the batch-operation cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	A well-signaled one-level-deep reference ('See scripts/master_controller.py for full implementation') points to a real bundled script, with organized Quick Start / Workflow / API sections; the thin API Reference (a single pointer) and absence of other reference files keep it just below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

53%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 has an explicit 'Use when' trigger clause and answers both what and when, but its capabilities are stated as generic verbs rather than concrete actions, and its scope is broad enough to risk overlap with related autonomous-coding skills.

Suggestions

Replace generic verbs ('managing', 'controlling', 'running') with concrete capabilities the controller performs (e.g. 'generates feature lists from a spec', 'runs an autonomous implementation loop', 'validates output', 'produces a completion report').

Add natural user-facing synonyms or concrete nouns to the trigger clause (e.g. 'build a full project unattended', 'run a spec-to-completion pipeline').

Sharpen the niche so it is distinguishable from other autonomous/agent skills, e.g. by scoping to multi-session, end-to-end project completion.

Dimension	Reasoning	Score
Specificity	Names the domain ('complete autonomous operation', 'end-to-end workflow') but the actions are generic verbs — 'starting', 'managing', 'controlling', 'running' — with no concrete capabilities (e.g. generating feature lists, running loops, validating, reporting), matching the 'names domain but actions are minimal/generic' anchor.	2 / 5
Completeness	Explicitly answers both what ('Master controller for complete autonomous operation') and when ('Use when starting full autonomous projects, managing end-to-end workflow...'), with the 'when' carrying multiple concrete trigger phrases; the 'what' stays somewhat abstract, keeping it just below the top anchor.	4 / 5
Trigger Term Quality	Includes some natural phrases a user might say ('autonomous projects', 'end-to-end workflow') but mixes in technical phrasing ('autonomous lifecycle', 'complete implementations') and lacks synonyms or concrete file/extension triggers, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'master controller / full autonomous project' framing is somewhat specific, but 'autonomous projects', 'end-to-end workflow', and 'complete implementations' are broad enough to overlap with other autonomous-coding and agent-orchestration skills.	3 / 5
	Total	12 / 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-master-controller/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.