ce-promote

Draft launch or promotion copy for a shipped feature.

Quality

69%

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-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 a well-structured, actionable workflow with strong sequencing, fallback/error-recovery loops, and clean progressive disclosure to one verified reference file; only minor conciseness trims and inlined generation-command details keep it from a perfect mark.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and action-focused with concrete commands and tight per-channel guidance, but carries minor over-explanation (e.g. the rationale in the opening paragraph and the 'spiral-agnostic' framing) that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor rather than the fully lean anchor at 5.	4 / 5
Actionability	It gives concrete, executable commands for detection and drafting (`gh pr view --json`, `git diff main...HEAD --stat`, `which spiral`, `spiral auth status --json`) plus specific per-channel formats, but the primary generation command's full flag set is deferred to references/spiral-cli.md, leaving a minor gap versus copy-paste-ready completeness at 5.	4 / 5
Workflow Clarity	Phases 1-4 are crisply sequenced with explicit decision checkpoints (Spiral state detection, the 'if you can't confidently tell what shipped, ask' guard) and clear feedback loops for error recovery (Path A failure silently falls back to Path B; Path 0 declines route to Path B), matching the anchor with explicit validation steps and recovery loops.	5 / 5
Progressive Disclosure	The body is a clear overview that pulls the detailed Spiral CLI reference into a single one-level-deep, well-signaled file (references/spiral-cli.md, verified present) referenced by explicit 'Read references/spiral-cli.md' cues, with content appropriately split and easy to navigate.	5 / 5
	Total	18 / 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 is clear and third-person with a distinct niche, but it states only one action and lacks an explicit 'Use when...' trigger clause, capping completeness and trigger coverage at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a feature has shipped and the user wants launch or promotion copy for it.'

List a couple more concrete deliverables to raise specificity, e.g. 'Draft launch or promotion copy — a tweet, changelog blurb, or LinkedIn post — for a shipped feature.'

Include natural synonyms users say, such as 'announcement', 'release notes', or 'social post', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("launch or promotion copy") and one concrete action ("Draft") tied to a target ("a shipped feature"), but lists only that single action and is not comprehensive — matching the 'Names domain and 1-2 concrete actions' anchor rather than the several-action anchors at 4-5.	3 / 5
Completeness	The 'what' is clear (draft launch/promotion copy) but 'when' is only weakly implied by 'for a shipped feature' and there is no explicit 'Use when...' trigger clause, which the guidelines cap at 3.	3 / 5
Trigger Term Quality	It includes some natural terms a user might say ("launch", "promotion copy", "shipped feature") but misses common variations and synonyms like "announcement", "tweet", "release notes", or "social post", fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct — promotion copy specifically for a shipped feature — with minor overlap risk against generic copywriting skills, fitting 'Mostly distinct; minor overlap risk' rather than the broader anchor at 3.	4 / 5
	Total	13 / 20 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: 26bf5b1

Reviewed: 4 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.