CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seed

Use when goal, constraints, and success criteria are already settled and the user wants them frozen into a formal spec an agent can execute and verify: 'turn this into a spec', 'write it up as a Seed', or right after an interview. Returns an immutable Seed with acceptance criteria. Not for vague requests (use interview first).

Quality

88%

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

85%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 exceptionally actionable, well-sequenced operational skill with real validation checkpoints and error-recovery loops throughout. Its weakness is structural: everything lives inline in one long file, including boilerplate and long prose blocks that would serve better as one-level-deep reference files.

Suggestions

Move the long QA quality_bar prose and the ouroboros_python resolver function into a references/ file (e.g., references/qa-bar.md, references/runtime.md) and point to them with a single line, cutting the main file's boilerplate footprint.

Extract the Refinement pass (Wonder → Reflect → Refine → Restate) protocol into its own reference file, keeping only a short summary and the user-gate rules in SKILL.md so the core seed-generation flow reads at a glance.

Consider moving the prefs.json star-ask snippet to a scripts/ file invoked by a one-line command, so the body stays focused on the seeding workflow.

DimensionReasoningScore

Conciseness

The body is dense operational instruction with essentially no explanation of concepts Claude already knows — the 1-2 anchors' padding is absent. However, the ~130-word inline quality_bar string ("Seed must be internally consistent, acceptance_criteria must be measurable...") and the 24-line resolver shell function are boilerplate-heavy inline blocks that could be trimmed or moved to a reference, fitting the 4 anchor ('efficient; minor instances of over-explanation that could be trimmed') rather than the 5 anchor's every-token-earns-its-place.

4 / 5

Actionability

Fully executable, copy-paste ready: the complete `ouroboros_python` shell function, exact tool-call argument blocks (e.g., the `session_context` schema with field-by-field guidance), the runnable Python snippet for prefs.json, concrete paths (`~/.ouroboros/seed-revisions/<revision_key>.md`), and exact output templates ("QA advisory: <PASS|REVISE|FAIL>, score X.XX (bar 0.90)."). Placeholders like <the seed YAML> are appropriate data slots, matching the 5 anchor.

5 / 5

Workflow Clarity

Clear sequence with explicit validation and feedback loops: the Path A/B fork has a concrete decision rule (tool callable → Path A); the QA check is an explicit checkpoint with threshold ("must be <= 0.2", bar 0.90); error recovery is specified ("If the response has status: 'gap_questions_required'... merge the answers... and call again"; resolver exit 127 with message; "If the write fails, include the audit block"); and refinement is gated ("Run QA exactly once", opt-in per pass, User Adoption Gate). This matches the 5 anchor's feedback loops for error recovery.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and the body resolves agent prompts at runtime paths ($OUROBOROS_AGENTS_DIR, package install) rather than via a bundled references/ structure. At ~190 lines it is a monolith whose long reusable blocks — the inline quality_bar prose, the Python resolver, the prefs snippet, the refinement-pass protocol — belong in referenced files; however, sections are well organized with clear headers. This fits the 3 anchor ('some structure but could be better organized; content that should be separate is inline') better than 4, since several substantial blocks are inlined rather than split out.

3 / 5

Total

17

/

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 description: it explicitly covers what the skill does, when to use it with quoted natural trigger phrases, and even excludes the wrong cases. The only gaps are slightly thin action coverage and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Quotes: "frozen into a formal spec an agent can execute and verify" and "Returns an immutable Seed with acceptance criteria" name several specific, concrete actions with a clear domain. It falls short of the 5 anchor because it does not list the fuller range of concrete actions (e.g., scoring ambiguity, QA verification) that the skill actually performs — a minor coverage gap, so it is above the midpoint (3) but not comprehensive.

4 / 5

Completeness

It explicitly answers both: WHAT — "Returns an immutable Seed with acceptance criteria" and "frozen into a formal spec an agent can execute and verify"; WHEN — "Use when goal, constraints, and success criteria are already settled" with concrete trigger phrases quoted verbatim. This matches the 5 anchor ('clearly and explicitly answers both what AND when with concrete trigger phrases'); it cannot be 4 because the 'when' is not merely present but multi-trigger and specific, and there is nothing vague about the 'what'.

5 / 5

Trigger Term Quality

Quotes: "'turn this into a spec'", "'write it up as a Seed'", "right after an interview" — natural phrases a user would actually say, plus the domain keyword "spec". A few common variations are missing (e.g., 'spec it out', 'requirements doc', 'freeze the requirements'), matching the 4 anchor ('good keyword coverage; a few natural terms missing') rather than the 5 anchor's synonym-and-extension completeness.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Seed/spec crystallization) with distinct triggers ('Seed', 'turn this into a spec') and an explicit negative boundary: "Not for vague requests (use interview first)" — which also routes away from the sibling interview skill. Minimal conflict risk, matching the 5 anchor's 'clear niche with distinct triggers'.

5 / 5

Total

18

/

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/seed/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.