twitter-engager
Expert Twitter marketing specialist focused on real-time engagement, thought leadership building, and community-driven growth. Builds brand authority through authentic conversation participation and viral thread creation.
32
16%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./marketing-twitter-engager/skills/SKILL.mdQuality
Discovery
32%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 reads more like a marketing professional's LinkedIn bio than a functional skill description. It relies heavily on buzzwords ('thought leadership', 'community-driven growth', 'brand authority') without specifying concrete actions Claude can perform. The lack of a 'Use when...' clause and the absence of natural user trigger terms significantly weaken its utility for skill selection.
Suggestions
Add an explicit 'Use when...' clause with natural trigger terms like 'write a tweet', 'Twitter thread', 'X post', 'social media engagement', or 'tweet reply'.
Replace marketing buzzwords with concrete actions such as 'Writes tweet threads, drafts replies, creates Twitter polls, and optimizes hashtag usage'.
Use third-person action verbs to describe capabilities (e.g., 'Creates viral Twitter threads, drafts engagement replies, builds content calendars for Twitter/X') instead of role-based framing like 'Expert Twitter marketing specialist'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Twitter marketing) and some actions like 'engagement', 'thought leadership building', 'viral thread creation', and 'conversation participation', but these are more like marketing buzzwords than concrete, actionable capabilities. It doesn't list specific discrete tasks like 'write tweet threads', 'draft replies', or 'schedule posts'. | 2 / 3 |
Completeness | The description addresses 'what' at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also vague enough to warrant a score of 1. | 1 / 3 |
Trigger Term Quality | Includes 'Twitter', 'engagement', 'thread creation', and 'brand authority' which are somewhat relevant keywords. However, it misses common user terms like 'tweet', 'X', 'social media post', 'hashtag', 'retweet', or 'Twitter thread'. The language leans more toward marketing jargon than natural user queries. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Twitter' and 'viral thread creation' provides some distinctiveness, but terms like 'marketing specialist', 'engagement', 'thought leadership', and 'community-driven growth' are generic enough to overlap with general social media marketing or content strategy skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a high-level marketing strategy document rather than an actionable skill for Claude. It is extremely verbose, entirely abstract, and provides no concrete examples, templates, or executable guidance. The content describes what good Twitter marketing looks like without ever showing Claude how to actually do it.
Suggestions
Replace abstract descriptions with concrete examples: include 2-3 example tweet templates, a sample thread structure with hook/body/CTA, and a specific crisis response template with fill-in-the-blank sections.
Cut sections that explain concepts Claude already knows (Identity & Memory, Communication Style, Learning & Memory) and deduplicate the success metrics that appear twice.
Add actionable workflow steps with specific outputs, e.g., 'Given a trending topic, produce: 1) a reaction tweet (≤280 chars), 2) a 5-tweet thread outline, 3) three reply-worthy questions for community engagement.'
Extract detailed sections (Thread Mastery, Crisis Management, Twitter Spaces Strategy, Advertising Integration) into separate referenced files, keeping SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive padding. Explains concepts Claude already knows (what Twitter engagement is, what crisis management means, what a conversational tone is). The 'Identity & Memory', 'Communication Style', and 'Learning & Memory' sections are largely unnecessary filler. Success metrics are duplicated. The entire document could be condensed to ~20% of its current length. | 1 / 3 |
Actionability | Almost entirely abstract and descriptive with no concrete, executable guidance. No example tweets, no thread templates, no actual response frameworks, no specific commands or tools. Statements like 'Monitor trending topics' and 'Educational content planning with viral potential' describe goals rather than instruct on how to achieve them. | 1 / 3 |
Workflow Clarity | The four phases are vague strategic categories rather than actionable sequential steps. There are no validation checkpoints, no feedback loops, no concrete decision points. Steps like 'Thread Strategy: Educational content planning with viral potential' provide no actual workflow guidance. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline with significant repetition (success metrics appear twice, crisis management appears in multiple sections). No navigation structure or links to detailed resources for advanced topics like crisis protocols or thread templates. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-openroster
- Commit
09aef5d
- 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.