CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable, well-sequenced growth playbook with concrete commands, templates, and quantified guidance. The main structural flaw is bundle organization: the algorithm-signals reference file is orphaned while its content is duplicated inline, wasting tokens and splitting the source of truth.

Suggestions

Replace the Step 4 "What X rewards" table with a pointer to references/algorithm-signals.md (e.g., "See [references/algorithm-signals.md](references/algorithm-signals.md) for the full signal-weight table") so the reference file is discoverable and the table isn't duplicated.

State the "never put links in tweet body — put in first reply" rule once (e.g., in the Algorithm Mechanics section) and drop the repetitions in the tweet rules and Common Pitfalls to recover tokens.

Add an explicit checkpoint between steps (e.g., after Step 1: "Only proceed to content creation once the bio/pinned checklist passes") to close the validation gap in the workflow.

DimensionReasoningScore

Conciseness

The body is dense and lean — checklists, tables, and templates with no explanation of concepts Claude already knows (no "what is Twitter" padding). It falls short of 5 because guidance is repeated: "No links in tweet body (kills reach)" appears in the tweet rules, the algorithm table, "What kills reach", and Common Pitfalls, and Step 4's signal table duplicates references/algorithm-signals.md.

4 / 5

Actionability

Copy-paste ready commands throughout ("python3 scripts/profile_auditor.py --handle @username", "site:x.com \"topic\" min_faves:100"), concrete tweet templates ("10 tools I use daily:\n\n1. X — for Y"), a cadence table quantified by account size, and a week-by-week playbook. Specific examples cover the common cases; a 4 would require missing key details, which are absent.

5 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced (audit → competitive intel → content → algorithm → playbook → calendar) with concrete commands at each stage and a feedback loop in Week 3-4 ("Review what formats got most engagement... Double down on top 2"). Not 5: there are no explicit validation checkpoints (e.g., verifying the audit was completed before moving to content creation); not 3, since sequence and a review loop are present — this is not a destructive/batch skill so no cap applies.

4 / 5

Progressive Disclosure

Sections and the Scripts table are well organized and all script paths resolve to real files, but references/algorithm-signals.md is never linked from the body ("Buried" reference — orphaned), and its content is duplicated inline in Step 4's "What X rewards" table. This matches anchor 3 ("references present but not clearly signaled; content that should be separate is inline") rather than 4, which requires references to be mostly clear with only minor organization gaps.

3 / 5

Total

16

/

20

Passed

Description

92%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 capabilities, explicit 'Use when...' triggers with natural phrasing, and active differentiation from neighboring social-media skills. Voice is third person throughout. Only minor gap is a few missing colloquial trigger terms (followers, impressions).

DimensionReasoningScore

Specificity

"building audience, crafting viral content, and analyzing engagement" plus the capability list "algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence" names multiple specific concrete actions with comprehensive coverage of the skill's scope. It matches the 5 anchor ("Extract text and tables from PDF files, fill forms, merge documents"-style completeness) rather than 4, which would require noticeable coverage gaps.

5 / 5

Completeness

The "what" is explicit ("X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement") and the "when" is explicit with concrete trigger phrases ("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"). This exactly matches the 5 anchor's what+when pattern; a 4 would require a vaguer 'when' clause.

5 / 5

Trigger Term Quality

"grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement" gives good natural-phrase coverage including the X/Twitter synonym pair. It is below 5 because common user terms like "followers", "viral", and "post" are only partially covered (viral appears once; followers/impressions never).

4 / 5

Distinctiveness Conflict Risk

"Complements social-content (generic multi-platform) with X-specific depth" explicitly disambiguates from the closest overlapping skills, and the X/Twitter niche triggers (tweets, threads, X profile) are distinct. Minimal conflict risk, matching the 5 anchor's clear-niche pattern; 4 would leave overlap unaddressed.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alirezarezvani/claude-skills

Path

marketing-skill/skills/x-twitter-growth/SKILL.md

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.