CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cw-emergent

Compose existing Compound Writing skills and runtime capabilities for open-ended writing outcomes that no single skill covers, such as cross-draft analysis, source-to-outline comparison, or multi-pass revision.

Quality

67%

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

Quality

Content

60%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 well-structured with a clear composition loop, concrete example table, and useful judgment guidance, but it carries some motivational padding, abstract primitives, and a broken external reference.

Suggestions

Remove the empty 'Lessons' placeholder and tighten motivational prose ('This is what makes the system agent-native...') to improve token efficiency.

Make the 'Primitives' column of the example table concrete (e.g. name the actual find/read/compare operations) instead of generic phrases like 'Find and read the relevant pieces'.

Fix or remove the broken reference to '../../references/context-contract.md' since no such file exists in the skill bundle.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized sections, but motivational padding ('This is what makes the system agent-native...'), the elaborated 'Ultimate Test' example, and an empty 'Lessons' placeholder add tokens that could be trimmed.

3 / 5

Actionability

The example table maps concrete requests to named skills and approaches, but the operational 'primitives' are described abstractly ('Find and read the relevant pieces') and key execution details are missing rather than concrete.

3 / 5

Workflow Clarity

The Composition Loop is a clear 6-step numbered sequence with an adapt/continue feedback loop and a Failure Modes section, though explicit validation checkpoints are only weakly present.

4 / 5

Progressive Disclosure

Content is well-organized into clear single-level sections with one clearly signaled external reference, but that reference path ('../../references/context-contract.md') points to a file that is not present in the bundle.

4 / 5

Total

14

/

20

Passed

Description

58%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 is specific and distinct, naming concrete example outcomes and a clear niche, but it omits an explicit 'Use when...' trigger clause and relies on specialized jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause with natural user phrasing, e.g. 'Use when a writing request spans multiple drafts or combines feedback types and no single skill covers it.'

Broaden trigger terms with common user phrasings like 'compare drafts', 'find patterns across my writing', or 'revise in multiple passes' alongside the existing jargon.

Lead with the concrete action(s) the skill takes rather than the abstract verb 'compose' to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('Compound Writing skills and runtime capabilities') and several concrete example outcomes ('cross-draft analysis, source-to-outline comparison, or multi-pass revision'), though the primary verb 'compose' is somewhat abstract so it is not a comprehensive 5.

4 / 5

Completeness

Has a clear 'what' (compose skills/capabilities for open-ended outcomes) but no explicit 'Use when...' clause; the 'when' is only weakly implied by 'that no single skill covers', which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes some relevant natural terms ('cross-draft analysis', 'multi-pass revision') but these are specialized jargon and common variations/synonyms a user might actually say are missing.

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (emergent composition when no single skill covers the request) with a distinct trigger, leaving only minor overlap risk with general orchestration skills.

4 / 5

Total

14

/

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