CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autonomous-workflow

The phase machinery (0–7) behind the `aw` dispatcher: task intake through a tested draft PR in an isolated worktree, gated by the plan.md brief and the run-checks.mjs sentinel, with companions that never block. Not the entry point — natural-language requests for autonomous work go to the `aw` skill; invoke /autonomous-workflow only to run the phases directly.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually well-structured orchestrator index: phases are gated, tiering is decision-procedural, and feedback loops are explicit, with lean and actionable inline guidance. Its main weakness is bundle integrity — the body points to a large file tree that is mostly absent, and most shipped reference files are orphaned from the index.

Suggestions

Ship the referenced `rules/*.md`, `templates/*`, and `aw/SKILL.md` files with the skill (or prune the references to files that exist), so the index's per-phase links actually resolve for an agent loading the bundle.

Add a short 'Further reading' map that links the other eight files in `references/` (e.g. `error-recovery-scenarios.md`, `planning-quality-research.md`) from the relevant sections, so shipped reference material is discoverable rather than orphaned.

Trim the tier-detection elaboration (the 'Two readings this exists to rule out' block and the `aw-executor` table row) into their referenced rule files to tighten token cost without losing the decision procedure.

DimensionReasoningScore

Conciseness

The body is dense and high-signal — terse tables, exact sentinel strings, and no explanations of concepts Claude already knows (nothing explains what a worktree or CI is). A few passages could be trimmed (the "Two readings this exists to rule out" elaboration and the long `aw-executor` unit-table row), which keeps it at anchor 4 rather than the every-token-earns-its-place bar of anchor 5.

4 / 5

Actionability

Provides concrete executable guidance throughout — exact commands (`gw add <branch>`, `Skill("aw-verify", "run local --no-push --no-comment --foreign-stack abort")`), a canonical MODE SELECTION output format, a complete copy-paste Lite brief, and install commands. It falls short of anchor 5's fully-executable bar because the actual phase procedures are delegated to `rules/*.md` files that are not present in the bundle, leaving the reader one broken hop from execution.

4 / 5

Workflow Clarity

Eight phases are each paired with an explicit gate in a table, tier detection is a first-yes decision walk, mandatory phases are flagged ("Phase 0 and Phase 2 are MANDATORY"), and error-recovery feedback loops are explicit (stuck-loop caps triggering `Skill("confidence", "analysis")`, failed `ui:` criteria re-entering Phase 3 under the same turn cap). This matches anchor 5: clear sequence, explicit validation steps, and feedback loops for error recovery.

5 / 5

Progressive Disclosure

The body is explicitly an index ("This file is an index; procedures live in `rules/*.md` and load on demand") with well-signaled, one-level-deep references per phase — textbook design. Scored against the actual bundle, however, roughly 23 of the 25 referenced paths do not exist (all of `rules/`, `templates/`, `aw/`, `CLAUDE.md`, `README.md`), and 8 of the 9 files in `references/` are never referenced from the body, so navigation does not resolve and the organization gaps exceed anchor 4's "minor".

3 / 5

Total

16

/

20

Passed

Description

87%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, distinctive description that states concrete capabilities, gives explicit positive and negative invocation guidance, and cleanly separates this skill from the `aw` dispatcher. Trigger term coverage is good though not exhaustive of natural synonyms.

DimensionReasoningScore

Specificity

Names several concrete actions and artifacts — "task intake through a tested draft PR in an isolated worktree", "gated by the plan.md brief and the run-checks.mjs sentinel", "run the phases directly" — with only minor coverage gaps. It describes the pipeline arc rather than comprehensively enumerating capabilities, so it sits at anchor 4 rather than 5, and its action specificity is well above the 1–2-action bar of anchor 3.

4 / 5

Completeness

Explicitly answers both questions: what ("The phase machinery (0–7) behind the `aw` dispatcher: task intake through a tested draft PR in an isolated worktree, gated by the plan.md brief and the run-checks.mjs sentinel") and when ("invoke /autonomous-workflow only to run the phases directly"), including an explicit negative boundary ("Not the entry point"). The when-guidance is fully explicit with concrete trigger phrasing, exceeding anchor 4's "could be more explicit".

5 / 5

Trigger Term Quality

Includes the primary natural phrase users would say ("natural-language requests for autonomous work") plus concrete domain terms ("tested draft PR", "phases", "worktree") with explicit routing guidance. Coverage is good but missing common synonyms (e.g. "unattended", "feature development"), fitting anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description actively disambiguates from its sibling skill ("Not the entry point — natural-language requests for autonomous work go to the `aw` skill") and carves a clear niche as the phase machinery. This is a clear niche with distinct triggers and minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 33 missing, 1 deeper-than-1-level, 3 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

mthines/agent-skills

Path

skills/workflow/autonomous-workflow/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.