CtrlK
BlogDocsLog inGet started
Tessl Logo

fable-goal

Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.

76

Quality

95%

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

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

A well-engineered instruction-only skill: a precise five-step workflow with real validation checkpoints (including a runnable self-check script), a complete worked example, and a clean split between the overview and a single one-level-deep reference file whose contents match the body's promises. The only weakness is mild: a few sentences of rationale in the body duplicate material already in the reference file.

Suggestions

Trim the 'The philosophy' section to its operative rules (observable-done corollary, brand-profile note) and move the persuasive rationale for the seven-part anatomy entirely into references/goal_prompt_patterns.md, which already covers it under 'Why each part exists'.

Shorten or drop the trailing derivation footer ('Derived from duncan-buildroom/freeskills...') — provenance adds tokens without changing execution.

DimensionReasoningScore

Conciseness

The body is dense and directive, and it correctly pushes the 'why' rationale (per-part explanations, failure-mode detail) into references/goal_prompt_patterns.md. Minor over-explanation remains: the 'The philosophy' section's rationale ('Get out of the model's way', the 'Make it good is a wish' illustration) partially duplicates the reference file's 'Why each part exists', and the derivation footer could be trimmed — so it sits above 'mostly efficient' (3) but short of 'every token earns its place' (5).

4 / 5

Actionability

Guidance is fully concrete and executable: six named extraction slots, a one-batch question rule, a verify step with literal actions ('ls the paths, glance at the available-tools list'), a quoted verbatim goal-line template, a 150-350 word target, a runnable check ('python3 scripts/goal_prompt_self_check.py -' on stdin, exit 0 semantics), and a complete worked example covering the common case. Nothing is pseudocode or hand-wavy; the instruction-only nature carries no penalty since the guidance is directly actionable.

5 / 5

Workflow Clarity

A clearly sequenced five-step process (extract → fill gaps/ask once → verify resources → write → self-check and deliver) with explicit validation checkpoints: the step-3 resource verification, the six-point self-check checklist, and a mechanical script check with a fix-any-miss-before-shipping feedback loop. This matches the anchor for clear sequence + explicit validation + error-recovery loop + checklist; the destructive/batch cap does not apply since the skill produces text, not risky operations.

5 / 5

Progressive Disclosure

SKILL.md is a 79-line overview; per-medium verification defaults, the failure-mode catalog, and the second worked example live one level deep in references/goal_prompt_patterns.md (verified to exist and contain exactly what the links promise), and the mechanical self-check lives in scripts/goal_prompt_self_check.py (verified to match its described behavior). Links are inline, clearly signaled, and state what each file contains; no inlined content belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

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

An exemplary description: it states the transformation concretely, lists natural verbatim trigger phrases including the slash command, and adds an explicit negative trigger that disambiguates it from build-the-thing skills. Third-person voice is used throughout, and the only (minor) limitation is that it describes one well-specified action rather than several.

DimensionReasoningScore

Specificity

The description specifies a concrete transformation with input, output, and medium ('Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session', 'The output is a single copy-paste prompt, never the build itself'). It centers on one action rather than listing several distinct actions, so it falls between the 1-2-action anchor (3) and the comprehensive multi-action anchor (5), but noticeably above the midpoint given the precise input/output/negative-scope specification.

4 / 5

Completeness

Both 'what' (convert a ramble into one polished, paste-ready /goal prompt; output is a single copy-paste prompt, never the build) and 'when' ('Use when the user says...') are explicit, with concrete trigger phrases and an additional negative trigger ('Do NOT use when the user wants the thing built right now in this session'). This meets and exceeds the anchor for a clear what-and-when with concrete triggers; not below 5 because neither half is weakly implied.

5 / 5

Trigger Term Quality

Five natural trigger phrases are quoted verbatim ('turn this into a goal prompt', 'write me a fable prompt', 'write the prompt that builds X', 'rambles about something they want made and asks for the prompt that makes it happen') plus the slash command '/fable-goal'. These are the exact phrasings a user would naturally say, comprehensively covering the niche's synonyms; not below 5 since no common variation is missing for this domain.

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (writing prompts for fresh autonomous sessions, not building) with distinct triggers and an explicit anti-trigger ('Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT'). This boundary sharply separates it from general build/prompt-engineering skills, so conflict risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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
alirezarezvani/claude-skills
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.