CtrlK
BlogDocsLog inGet started
Tessl Logo

create-x-content

Draft voice-tuned X (Twitter) post variants from a free-form brief. Reads a personal voice guide (generated via generate-voice-guide), produces 2–5 variants with distinct framings (simple-howto, problem-first, hype, mechanism-breakdown, etc.), and self-checks against the voice guide's banned phrases before returning.

66

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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-structured, highly actionable agent-workflow skill: clear phase sequencing with an explicit self-check feedback loop, concrete schemas and examples, and disciplined token usage. The only notable gaps are minor redundancy between the Tips and Phase 2 sections and a single-file layout that is slightly long for the leanest overview.

DimensionReasoningScore

Conciseness

The body is efficient throughout — no explanations of concepts Claude already knows, and every section carries operational weight (flag table, framing catalog, self-check rules). It is not level 5 because there is minor redundancy: the Tips section restates Phase 2's 'Quality > quantity. 2 strong variants beat 5 watered-down ones' as 'Five weak ones is worse than two strong ones', and the framing 'when to use' guidance slightly overlaps the variant-count heuristics. It is above level 3 because these are small trimmings, not unnecessary explanations.

4 / 5

Actionability

For an instruction-only, agent-executed skill the guidance is fully executable: exact invocation syntax ('/create-x-content --brief "..."'), a flag table with defaults, a 4-step voice-guide resolution chain with fallback options, a concrete framing table mapping label → structure → when-to-use, a 4-item self-check with a rewrite-then-drop rule, exact file naming ('variant-<letter>-<framing-slug>.md' with examples) and a complete output frontmatter schema. This matches 'specific examples cover the common cases' (two worked brief examples with resulting variant counts). Per the rubric's scoring note, absence of code is not penalized in instruction-only skills when guidance is this actionable; it is not below 5 because no key execution detail is left implicit.

5 / 5

Workflow Clarity

Six explicitly sequenced phases (load guide → parse brief/decide count → generate → self-check → save → deliver) with an explicit validation checkpoint: Phase 4's banned-phrase, length, 'meat', and voice-match checks plus a feedback loop — 'If a variant fails any check and two rewrite attempts don't fix it, drop the variant rather than ship something weak.' This matches the level-5 anchor ('clear sequence with explicit validation steps; feedback loops for error recovery'). The operation is neither destructive nor batch, so no cap applies; it is not level 4 because the checkpoints are already explicit rather than minor-gapped.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the single SKILL.md is well-organized with clear section headers (Quick Start, Inputs, Voice Guide Resolution, Workflow phases, Outputs, Examples, Tips) and no nested references. It is not level 5 under the simple-skill carve-out because the body is ~150 lines — the framing catalog and worked examples could plausibly live in a reference file, keeping the overview leaner. It is not level 3 because nothing is buried or mis-filed: structure is clean, the external dependency (generate-voice-guide) is clearly signaled, and no content obviously belongs in a separate file to the point of hurting navigation.

4 / 5

Total

18

/

20

Passed

Description

71%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 specific, third-person description with concrete actions and good natural terminology, but it omits any 'Use when...' trigger guidance, which caps its completeness. Adding an explicit trigger clause and the 'tweet' synonym would lift the two weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to write tweets/X posts, draft social content in their own voice, or generate post variants from a brief.'

Include the synonym 'tweet' (and 'thread' if supported) alongside 'X (Twitter) post' to broaden natural keyword coverage.

Consider naming the primary actor context ('the agent drafts...') only if it aids clarity — the current third-person voice is already correct.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Draft voice-tuned X (Twitter) post variants from a free-form brief', 'Reads a personal voice guide', 'produces 2–5 variants with distinct framings (simple-howto, problem-first, hype, mechanism-breakdown, etc.)', 'self-checks against the voice guide's banned phrases' — comprehensively covering the skill's capability surface. This matches the level-5 anchor ('multiple specific concrete actions; comprehensive coverage') and exceeds level 4, which allows coverage gaps; the only unlisted step (saving output files) is minor. It is not level 4 because every listed action is concrete with no generic filler.

5 / 5

Completeness

The 'what' is clear and detailed (draft variants, read voice guide, self-check), but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not level 2 because the 'what' half is concrete and multi-part rather than vague; it is not level 4 because level 4 requires both 'what' and a present-but-imperfect 'when'.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'X (Twitter) post', 'post variants', 'brief', 'voice guide', 'voice-tuned' — users drafting social content would plausibly say several of these. It is below level 5 because common variations are missing: 'tweet', 'thread', 'social media post' never appear, so a user asking to 'write a tweet' gets only partial term overlap. It is above level 3 ('Works with PDF files'-level) because it covers multiple distinct natural phrases plus synonyms (X/Twitter), not a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

The voice-guide pairing ('Reads a personal voice guide (generated via generate-voice-guide)', 'self-checks against the voice guide's banned phrases') carves out a clear niche distinct from generic writing skills, matching 'mostly distinct; minor overlap risk'. It is not level 5 because it could overlap with sibling social-content skills (the body references a /social-kit skill) and with general copywriting/tweet-drafting requests that don't mention a voice guide; not level 3 because the voice-guide mechanism and named framings make it substantially more specific than 'Works with document files'-level descriptions.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-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.