CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-promise

Generate 3 promise options that create anticipation for what's to come. Invoke with /cw-promise or /cw-promise [topic/context].

Quality

73%

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

Quality

Content

78%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 content is well-structured, actionable, and concise, with a clear generation workflow and a ready-to-use output template. Its only weak spot is that the body references an external context file that is not present in the bundle.

Suggestions

Resolve the dangling reference to ../../references/context-contract.md: either add the file to a references/ bundle or replace the instruction with inline guidance so the skill is self-contained.

Make the workflow's verification step explicit (e.g., 'Check each option against the Quality Checks before presenting') to push workflow clarity to the top anchor.

Tighten the 'Essential Ingredients' and 'Forms It Might Take' lists, which read as craft background Claude largely already knows.

DimensionReasoningScore

Conciseness

The body is largely efficient and assumes craft competence, with only minor over-explanation in the 'What Makes a Promise Work' criteria lists that could be trimmed, sitting just below the lean-and-efficient top anchor.

4 / 5

Actionability

A concrete 4-step generation process plus an explicit, copy-ready output-format template with placeholders and a 'What to Avoid' checklist gives mostly executable guidance with only minor gaps, matching the 'mostly executable' anchor.

4 / 5

Workflow Clarity

The 'How to Generate' section lays out a clear, ordered sequence (analyze -> select approaches -> generate one per approach -> present all three); this is non-destructive so the validation cap does not apply, though checkpoints are implicit rather than explicit.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized sections and no bundle files, and at roughly 100 lines of simple single-purpose guidance it meets the simple-skill exception that allows a 5 with clean structure.

5 / 5

Total

17

/

20

Passed

Description

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

The description states a clear single-purpose action but omits explicit 'Use when...' trigger guidance and leans on invocation syntax rather than natural user phrases. It is distinct but not as complete or trigger-rich as the top anchors.

Suggestions

Add a 'Use when...' clause naming natural user triggers (e.g., 'Use when the user wants a hook, lead, or opening promise that builds anticipation for a piece').

Include common synonyms users would actually say ('hook', 'lead', 'opening', 'teaser') alongside 'promise' to broaden trigger coverage.

State multiple specific actions (e.g., 'Generate, vary, and refine 3 opening promises') to lift specificity toward the top anchor.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ('Generate 3 promise options that create anticipation') but stays at a single-task level without enumerating multiple specific actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

It gives a clear 'what' (generate 3 promise options) but no 'when'/'Use when...' guidance, so per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

The phrase 'promise options that create anticipation' supplies some relevant keywords, but the only trigger guidance is invocation syntax ('Invoke with /cw-promise') rather than natural user phrases a person would say, so common variations are missing.

3 / 5

Distinctiveness Conflict Risk

The 'promise' framing and dedicated slash-command invocation carve out a fairly distinct niche with only minor overlap risk against sibling copywriting skills, sitting just below a fully distinct niche.

4 / 5

Total

13

/

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

EveryInc/compound-writing

Path

skills/cw-promise/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.