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.

67

Quality

84%

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

The canonical home for this skill is fable-goal in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

73%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-crafted, dense instructional body with an exemplary process structure (clear sequencing, verification steps, self-check feedback loop, concrete worked example) that assumes Claude's intelligence. Its one significant defect is that both referenced bundle files — the per-medium patterns reference and the self-check script — are missing from the bundle, breaking progressive disclosure and making one stated command unrunnable.

Suggestions

Ship the missing bundle files: create references/goal_prompt_patterns.md (per-medium verification defaults, failure-mode detail, second worked example) and scripts/goal_prompt_self_check.py, or inline the per-medium verification defaults into the body and drop the reference.

If the self-check script cannot be bundled, replace the runnable command in step 5 with the explicit manual checks (word count, goal line, autonomy directive, freedom/verification/destination language) so no instruction points at a nonexistent file.

Trim 'The philosophy' section to its two operative rules (get out of the model's way; done must be observable) to cut the remaining over-explanation.

DimensionReasoningScore

Conciseness

The body is tight and imperative throughout ('Pull out six slots', 'Name only what you verified AND what is load-bearing'), assumes Claude's competence, and contains no padding about known concepts. The 'philosophy' section and some repeated emphasis (creative freedom and verification each restated in the self-check and anti-patterns) are minor instances that could be trimmed, matching the 'efficient; minor over-explanation' anchor rather than the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

Highly concrete guidance: a six-slot extraction list, explicit ask-only-when categories, a seven-part anatomy with specific content per part, a 150–350 word length target, a full worked example, and an exact runnable command ('python3 scripts/goal_prompt_self_check.py -'). It falls short of fully-executable because that script does not exist in the bundle, so one concrete command cannot actually run — a minor gap rather than pseudocode or missing steps, fitting anchor 4 rather than 5.

4 / 5

Workflow Clarity

A clearly sequenced five-step process (extract → fill gaps → verify before naming → write → self-check) with explicit validation checkpoints: step 3's 30-second resource verification and step 5's six-point checklist with a fix-any-miss-before-shipping feedback loop. This matches the anchor for clear sequence with explicit validation steps, feedback loops, and a checklist for a complex process; it is above anchor 4, which tolerates missing checkpoints.

5 / 5

Progressive Disclosure

The body is well-sectioned and its references are clearly signaled ('See references/goal_prompt_patterns.md for per-medium defaults', 'Failure-mode detail and a second worked example... live in references/goal_prompt_patterns.md', 'python3 scripts/goal_prompt_self_check.py'), but scored against the actual bundle structure neither file exists — there is no references/ or scripts/ directory at all. The load-bearing deferred content (per-medium verification defaults, failure-mode detail, second worked example, and the self-check tool) is unreachable, so the disclosure structure sends the session on a dead-end hunt — the skill's own named anti-pattern. This sits noticeably below the midpoint: the navigation exists but the destinations do not.

2 / 5

Total

15

/

20

Passed

Description

91%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 that explicitly states the transformation, the output artifact, comprehensive natural trigger phrases, and an explicit negative trigger excluding the wrong-tool case, all in third person. Its only weakness is minor overlap risk with generic prompt-writing requests.

DimensionReasoningScore

Specificity

Concrete actions are named in third person: 'Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt' plus the output form ('a single copy-paste prompt, never the build itself'). It lists the transformation and its output clearly but is a single-action skill, so coverage is inherently narrower than the comprehensive multi-action anchor — fitting 'several specific actions; minor gaps' rather than 'not comprehensive' (it is more complete than the 1–2-action anchor).

4 / 5

Completeness

Explicitly answers both questions: what ('Convert a rambling description... into one polished, autonomous /goal prompt ready to paste into a fresh session') and when ('Use when the user says...'), with concrete trigger phrases and an additional explicit exclusion ('Do NOT use when the user wants the thing built right now in this session'). This matches the anchor for clearly and explicitly answering both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-phrase coverage with synonyms and the slash command: '/fable-goal', 'turn this into a goal prompt', 'write me a fable prompt', 'write the prompt that builds X', plus the descriptive trigger 'rambles about something they want made and asks for the prompt that makes it happen'. These are exactly the phrasings a user would naturally say; no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (autonomous /goal prompt authoring) and the do-NOT-use clause deftly separates it from build-it-now requests. However, 'write the prompt that builds X' and 'write me a fable prompt' could also fire for a closely related general prompt-writing/improvement skill, leaving minor overlap risk — fitting 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

14

/

16

Passed

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.