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.

64

Quality

76%

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/content/capabilities/create-x-content/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 strong, highly actionable agent-executed skill with a clear phased workflow, explicit validation feedback loops, and concrete copy-paste-ready schemas. Its only weakness is mild redundancy between the 'Tips' section and earlier workflow phases.

DimensionReasoningScore

Conciseness

The body is largely efficient and never explains concepts Claude already knows, but the 'Tips' section restates workflow guidance already in Phase 2 ('Quality > quantity'), Phase 3 ('Don't write five variants with the same opening hook'), and Phase 4 (the 'meat' check), so it 'could be tightened'.

2 / 3

Actionability

Provides copy-paste-ready specifics: a full framing table with structure and when-to-use, an explicit self-check checklist, a concrete file-naming pattern, and a complete frontmatter schema — matching 'Fully executable... specific examples; copy-paste ready' for an instruction-only skill.

3 / 3

Workflow Clarity

Six clearly sequenced phases (Load → Parse → Generate → Self-check → Save → Deliver) with an explicit validate→fix→retry feedback loop ('two rewrite attempts don't fix it, drop the variant') and a 4-item checklist, matching 'Clear sequence with explicit validation steps; feedback loops for error recovery'.

3 / 3

Progressive Disclosure

No bundle files exist and none are warranted — all content (framing table, self-checks, schema) is core to every run and appropriately inline, organized under clear section headers with easy navigation and no nested references.

3 / 3

Total

11

/

12

Passed

Description

67%

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 distinctive, naming concrete actions and a clear niche. It is weakened by the absence of an explicit 'Use when...' trigger clause and by relying on skill-internal jargon rather than the natural terms (e.g. 'tweet') a user would actually say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to write X/Twitter posts or tweets, or wants several voice-matched variants of a brief.'

Surface natural trigger terms users actually say — include 'tweet' and 'thread' alongside 'X (Twitter) post'.

Trim skill-internal jargon ('framings', 'mechanism-breakdown', 'banned phrases') from the description; those belong in the body, not the trigger surface.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Draft voice-tuned X post variants', 'Reads a personal voice guide', 'produces 2-5 variants with distinct framings', 'self-checks against the voice guide's banned phrases' — matching the 'Lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what' (drafts variants, reads the guide, self-checks) but provides no 'Use when...' clause or equivalent explicit trigger guidance for 'when', which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Core natural terms 'X (Twitter) post' are present, but the most common trigger 'tweet' is absent and the bulk of the text uses jargon ('voice-tuned', 'framings', 'mechanism-breakdown', 'banned phrases') that users would not naturally say, fitting 'Some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific — voice-tuned X/Twitter post variants driven by a personal voice guide — making it unlikely to trigger for unrelated skills, matching 'Clear niche with distinct triggers; unlikely to conflict'.

3 / 3

Total

10

/

12

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.

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