twitter-hand-skill

Expert knowledge for AI Twitter/X management — API v2 reference, content strategy, engagement playbook, safety, and performance tracking

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./crates/openfang-hands/bundled/twitter/SKILL.md

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable examples but is a monolithic wall of reference material that should be split into referenced files, and it lacks validation/feedback loops for risky batch/destructive posting operations.

Suggestions

Split the API v2 reference, content strategy, and engagement playbook into separate reference files (e.g. REFERENCES/api-v2.md, content-strategy.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add explicit validation checkpoints to destructive/batch workflows, e.g. after posting a thread verify each tweet_id returned before continuing, and confirm deletes succeeded before reporting success.

Trim padding prose (e.g. "the hook is everything") and move full rate-limit/posting-time tables to a reference file to reduce token load.

Dimension	Reasoning	Score
Conciseness	Largely dense and useful, but ~360 lines keep full API curl references, rate-limit tables, and posting-time tables inline that could be offloaded to reference files; some prose ("the hook is everything") could be trimmed.	2 / 3
Actionability	Fully executable curl commands, concrete content-type templates, formulas, and copy-paste-ready examples throughout; specific and immediately usable.	3 / 3
Workflow Clarity	Sequences exist (thread posting, content calendar) but there are no explicit validation checkpoints or feedback loops for destructive/batch operations like posting or deleting tweets, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Monolithic single file with no bundle files; API reference, strategy, and engagement playbook are all inline rather than split into well-signaled one-level-deep references.	2 / 3
	Total	9 / 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 distinct but lacks an explicit 'Use when' trigger clause and natural user-facing trigger phrases, capping completeness and trigger-term quality at 2. It reads as a capability inventory rather than a discovery/trigger description.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when managing a Twitter/X account, scheduling tweets or threads, replying to mentions, or tracking engagement metrics.'

Swap jargon-leaning phrasing ('Expert knowledge for AI Twitter/X management') for concrete actions users would request, such as 'post tweets, build threads, reply to mentions, and analyze engagement.'

Mirror the good-example structure: state the concrete actions first, then the trigger conditions.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete capabilities — "API v2 reference, content strategy, engagement playbook, safety, and performance tracking" — rather than vague language.	3 / 3
Completeness	Clearly answers "what" but has no "Use when..." clause or explicit trigger guidance, so "when" is only implied — which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Includes relevant domain terms ("AI Twitter/X management") but misses common natural phrasings a user would say ("post tweets", "schedule a thread", "grow my Twitter"); the leading "Expert knowledge for" framing is jargon-leaning.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Twitter/X account management) with distinct triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: RightNow-AI/openfang
Path: crates/openfang-hands/bundled/twitter/SKILL.md
Commit: acf2587

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.