ce-promote

Draft launch or promotion copy for a shipped feature.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/ce-promote/SKILL.md

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, highly actionable workflow with clear sequencing, error-recovery loops, and clean one-level-deep reference usage. Its only weakness is conciseness: the embedded editorial/social fundamentals add length that could be trimmed or partially offloaded.

Dimension	Reasoning	Score
Conciseness	The body is dense and directive rather than padded with basics Claude knows, but at ~140 lines it includes editorial fundamentals ('Lead with the user-facing outcome', channel shape lists) that could be tightened; it is 'mostly efficient but could be tightened' rather than fully lean.	2 / 3
Actionability	It gives concrete, copy-pasteable commands — 'gh pr view --json title,body,url', 'which spiral', 'spiral auth status --json', 'spiral write "..." --instant --json' — plus worked examples, matching the score-3 'fully executable commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Phases 1–4 are explicitly sequenced, with a readiness classification tree (Absent/Ready/Unauthed) and error-recovery feedback loops ('If the spiral write call errors or returns no usable drafts, silently fall back to Path B'), matching the score-3 'clear sequence with explicit validation/feedback' anchor.	3 / 3
Progressive Disclosure	The body is an overview that repeatedly and clearly signals a single one-level-deep reference 'references/spiral-cli.md' (verified to exist) for Spiral setup details, while keeping the main flow inline — matching the score-3 'clear overview with well-signaled one-level-deep references' anchor.	3 / 3
	Total	11 / 12 Passed

Description

57%Weight 40%Scale 1-3

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 third-person, clean, and occupies a distinct niche, but it is a single-clause sentence with no explicit 'Use when' trigger guidance and limited coverage of natural channel keywords. It sits at the score-2 band on most dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when you ship a feature and need a tweet, changelog blurb, LinkedIn post, or other launch/promotion copy.'

Broaden trigger terms to include channels users actually name (tweet/X thread, changelog, release notes, LinkedIn, announcement).

List a couple more concrete actions (e.g. 'drafts channel-specific copy and a changelog blurb') to lift specificity toward the score-3 anchor.

Dimension	Reasoning	Score
Specificity	Quotes 'Draft launch or promotion copy for a shipped feature' — it names the domain (launch/promotion copy) and one action (draft), but does not list multiple concrete actions like the score-3 anchor 'Extract text and tables... fill forms, merge documents'.	2 / 3
Completeness	It states what ('Draft launch or promotion copy') but lacks an explicit 'Use when...' trigger clause; per the guideline a missing explicit trigger guidance caps completeness at 2 even though 'for a shipped feature' loosely implies when.	2 / 3
Trigger Term Quality	'launch or promotion copy', 'shipped feature' are relevant but it omits common user variations such as 'tweet', 'LinkedIn', 'changelog', 'release notes', or 'announcement', matching the score-2 anchor of some relevant keywords missing common variations.	2 / 3
Distinctiveness Conflict Risk	'Draft launch or promotion copy for a shipped feature' carves a clear niche (post-ship announcement copy) with distinct triggers unlikely to fire for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: EveryInc/compound-engineering-plugin
Path: skills/ce-promote/SKILL.md
Commit: a9f6d53

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.