CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

auto

Use when the work spans several files or replaces a framework, language, auth, storage, or API layer (rewrites and migrations included), and the user wants it to end up working and tested. Asks only what is missing, writes a spec with acceptance criteria, then runs and verifies it in the background. Not for questions, small edits, or an existing Seed (use run).

Quality

78%

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/auto/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense with genuinely non-obvious operational specifics and concrete tool-call signatures, making it highly actionable, but it is written as enormous nested sentences that hurt readability and pack three separable policies into one monolithic file. It would benefit from flattening conditions into checklists and moving sub-policies into reference files.

Suggestions

Flatten the ~90-word nested conditional in Background monitoring #2 (and similar sentences) into a bulleted fail-closed checklist so the sentinel validation rules are scannable instead of parseable.

Move the Synapse intent refinement, Active Conductor decision policy, and observer-contract validation details into one-level-deep references/ files, keeping a 1-2 line pointer in SKILL.md.

Replace the prose-heavy flag translation notes and interview relay rules with compact tables or step lists to match the clarity already achieved by the CLI flag → MCP arg table.

DimensionReasoningScore

Conciseness

Almost every sentence carries non-obvious operational facts (no padding with concepts Claude already knows), but the prose is severely over-nested — e.g., the sentinel-validation clause in Background monitoring #2 is a single ~90-word sentence with five stacked conditions, and several similar constructions. Mostly earns its tokens but could be tightened substantially into checklists, so it sits at anchor 3 rather than 4.

3 / 5

Actionability

Provides concrete, near copy-paste-ready calls: the full `ouroboros_job_wait(job_id=..., cursor=..., timeout_seconds=180, view="summary", stream="linked", wait_for="attention_or_ac_change")` signature, the CLI flag → MCP arg translation table, and exact signal parameters. Not a 5 because the `orchestrate_subagents` spawn mechanics and tool-schema loading are described but never shown, leaving execution gaps.

4 / 5

Workflow Clarity

Background monitoring is sequenced 1-6 (hand off → spawn one observer → relay events → interview Q&A → fallback wait → result) with explicit error-recovery branches for detached/blocked/failed statuses, spawn failure, and observer exit. Not a 5 because the dense nesting makes some checkpoints implicit and the fallback conditions in #5 require re-reading to reconstruct the decision order.

4 / 5

Progressive Disclosure

Sections are clearly headed, but this is one monolithic ~210-line file with no bundle references, and three detailed sub-policies (observer sentinel validation, Synapse intent refinement, Active Conductor decision policy) are inlined when they would sit better as one-level-deep reference files. Structure exists but content that should be separate is inline — anchor 3.

3 / 5

Total

14

/

20

Passed

Description

83%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 description: it explicitly states what the skill does, when to use it with concrete trigger terms, and when not to use it with redirects to sibling skills. Minor improvements possible by adding synonyms like "refactor" or "port" and tightening the broad "working and tested" trigger.

DimensionReasoningScore

Specificity

Names a concrete domain ("replaces a framework, language, auth, storage, or API layer (rewrites and migrations included)") and several specific actions ("Asks only what is missing, writes a spec with acceptance criteria, then runs and verifies it in the background"). Not a 5 because the action inventory is not comprehensive; above a 3 because it lists more than 1-2 concrete actions tied to a specific domain.

4 / 5

Completeness

Explicitly answers both: what ("Asks only what is missing, writes a spec with acceptance criteria, then runs and verifies it in the background") and when ("Use when the work spans several files or replaces a framework, language, auth, storage, or API layer... and the user wants it to end up working and tested"), with concrete trigger phrases plus explicit negative scope ("Not for questions, small edits, or an existing Seed").

5 / 5

Trigger Term Quality

Contains natural phrases users would say: "rewrites and migrations", "framework", "auth", "storage", "API layer", "working and tested". Missing common synonyms like "refactor", "port", or "overhaul", so coverage is good but not comprehensive (anchor 4, not 5).

4 / 5

Distinctiveness Conflict Risk

Clear niche (end-to-end multi-file/layer-replacement builds) with explicit disambiguation ("Not for questions, small edits, or an existing Seed (use run)"). Not a 5 because "work spans several files" and "wants it to end up working and tested" are broad triggers that overlap with general coding skills; above a 3 because the explicit exclusions sharply reduce misfires.

4 / 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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

Q00/ouroboros

Path

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