CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autopilot

Full autonomous execution from idea to working code

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/autopilot/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 strong orchestration playbook: phases, escalation rules, stop conditions, and verification loops are explicit and executable. Its weaknesses are repetition across Steps and Advanced sections, and a monolithic single-file structure with inlined detail and references to docs files that are not actually shipped.

Suggestions

Split Workflow_Profiles (validation rules, descriptor/hash semantics, v1 deferrals), Configuration, and the 3-Stage Pipeline narrative into reference files linked one level deep, leaving SKILL.md as a lean overview.

State the ralplan/deep-interview skip behavior once (Phase 0) and have later sections reference it instead of re-explaining it twice more.

Ship docs/company-context-interface.md and docs/REFERENCE.md in the bundle or remove the citations, since both paths currently point at nonexistent files.

DimensionReasoningScore

Conciseness

Most content is orchestration-specific and non-inferable, but there is real redundancy: ralplan-skip behavior is stated in Phase 0, Phase 1, and again in the 3-Stage Pipeline section; the deep-interview/AFK flow is explained twice; and Workflow_Profiles carries dense spec-level detail (SHA-256 descriptor hashes, transcript evidence binding, v1 deferrals) that could be tightened. Anchor 3 — mostly efficient but could be trimmed, not the several padded sections of anchor 2.

3 / 5

Actionability

Guidance is largely executable: concrete file paths (.omc/autopilot/spec.md, .omc/notepads/autopilot/problems.md), runnable commands (omc team 1:cursor "<task>"), explicit Task(subagent_type=...) calls, and copy-ready JSONC config with failure fallbacks. Minor gaps remain — e.g. 'Analyst (Opus) extracts requirements' gives no method or prompt pointer — keeping it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

Six phases are strictly sequenced with explicit validation checkpoints and feedback loops: QA cycles capped at 5 with a 3-strike fundamental-issue stop, validation re-rounds capped at 3, a full AFK assumption protocol, budget-stop boundaries at 90%/100%, and a final checklist demanding fresh test and build output. This matches the anchor-5 pattern of clear sequencing plus error-recovery loops.

5 / 5

Progressive Disclosure

Sections are clearly labeled, but this is a ~268-line monolithic file with no bundle: Workflow_Profiles internals, configuration, troubleshooting, and pipeline documentation are all inlined where they belong in separate reference files, and the two cited docs (docs/company-context-interface.md, docs/REFERENCE.md) do not exist in the bundle. Anchor 3 — structure exists, but content that should be separate is inline and references are effectively dangling.

3 / 5

Total

15

/

20

Passed

Description

37%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 a terse, accurate one-liner that clearly conveys the skill's scope, but it omits any use-when guidance and any enumeration of concrete capabilities. Trigger coverage and completeness are the weak points, with the rich trigger detail stranded in the body instead of the frontmatter.

Suggestions

Add a 'Use when...' clause to the description, e.g. 'Use when the user says autopilot, build me, or wants hands-off end-to-end execution of a multi-phase project.'

Enumerate 2-3 concrete capabilities (requirements expansion, parallel implementation, QA cycling, multi-perspective validation) so specificity reaches anchor 4.

Include natural synonyms (end-to-end, hands-off, full auto) and boundary hints (not for single fixes or brainstorming) to reduce conflict with sibling build/plan skills.

DimensionReasoningScore

Specificity

"Full autonomous execution from idea to working code" names the domain but lists no concrete actions such as requirements analysis, planning, QA, or validation. It sits at anchor 2 rather than 3 because no specific operations are enumerated, and above 1 because the domain and outcome are named.

2 / 5

Completeness

The "what" is clear (autonomous idea-to-working-code execution) but the "when" is entirely missing from the description — trigger phrases exist only in the body, so the rubric's cap of 3 applies. Not 4 because the when-clause is absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Only "autonomous" functions as a natural user term; common invocation phrases like "build me", "end-to-end", or "hands-off" are absent from the description. This is one or two generic keywords (anchor 2), not the zero of anchor 1, and well short of the synonym coverage of anchor 3+.

2 / 5

Distinctiveness Conflict Risk

The end-to-end autonomous build niche is recognizable, but "build from an idea to working code" overlaps with sibling skills referenced in the body (ralph, plan, executor delegation). Anchor 3 fits: somewhat specific but overlapping with similar skills.

3 / 5

Total

10

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/autopilot/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.