CtrlK
BlogDocsLog inGet started
Tessl Logo

x-twitter-growth

X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

Highly actionable with concrete script calls, templates, and cadence tables, but it suffers from a progressive-disclosure gap (an orphaned reference file with its content duplicated inline) and missing validation checkpoints on batch operations that cap workflow clarity at 3.

Suggestions

Replace the inline 'What X rewards' table in Step 4 with a pointer to references/algorithm-signals.md so the reference file is actually used and the body stays lean.

Add explicit verification checkpoints to batch steps — e.g., after running competitor_analyzer.py or content_planner.py, instruct Claude to validate/sanity-check the output before proceeding.

De-duplicate the 'no links in tweet body' guidance so it lives in one canonical place rather than recurring across Step 3 and Step 4.

DimensionReasoningScore

Conciseness

Dense, scannable content using tables, checklists, and code blocks with little padding, but Step 4 inlines the algorithm-signal table that already exists in references/algorithm-signals.md and repeats the 'no links in tweet body' rule across sections.

4 / 5

Actionability

Fully executable guidance throughout — concrete script invocations with flags, structured tweet templates with character rules, hook format examples, and a posting-cadence table keyed by follower size covering the common cases.

5 / 5

Workflow Clarity

A clear 6-step sequence is present (audit → competitor research → content → algorithm → playbook → calendar), but batch operations like competitor analysis and calendar generation have no validation/verification checkpoints, which per the rubric caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Good section structure and a clean Scripts table, but references/algorithm-signals.md is orphaned — the body inlines the algorithm table instead of linking to it — so reference signaling is broken and content that belongs in a separate file is duplicated inline.

3 / 5

Total

15

/

20

Passed

Description

95%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 strong description: concrete actions, comprehensive natural trigger phrases, clear what/when guidance, and an explicit boundary against the related social-content skill. The only soft spot is a mild over-claim ('viral content') keeping specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions (build audience, analyze X profile, research competitors, plan posting strategy) plus X-specific depth areas, matching the 'several specific actions' anchor; falls short of 5 only because phrases like 'crafting viral content' are slightly soft over-claims.

4 / 5

Completeness

Explicitly answers both 'what' (growth engine for building audience, crafting content, analyzing engagement) and 'when' via a concrete 'Use when the user wants to...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases with synonyms — 'grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy' — covering what users would actually say.

5 / 5

Distinctiveness Conflict Risk

X-specific niche with distinct triggers and an explicit boundary statement distinguishing it from social-content ('Complements social-content... with X-specific depth'), minimizing conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-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.