x-api

Read and post to X/Twitter via API. Check mentions, post tweets, search. Use app bearer tokens for read-only fetches and OAuth 1.0a user context for account actions.

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 ./skills/x-api/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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, specific code and a clear reply/context workflow, but it is a monolithic single-file skill with some inline troubleshooting verbosity and no validation feedback loops around destructive operations like tweet deletion.

Suggestions

Add an explicit pre-flight validation/retry loop for destructive and account-scoped actions (e.g., verify the target tweet ID exists and Joel approves before delete/post) to raise workflow_clarity.

Move dated troubleshooting (PIN OAuth note, bookmark caveat) into a deprecated/notes section or a separate reference file to reduce inline verbosity and improve conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code earning its place, but inline PIN-OAuth troubleshooting notes and dated caveats add length that could be tightened or moved aside, so it is not fully lean.	2 / 3
Actionability	Provides fully executable, copy-paste-ready bash/python and curl snippets with specific endpoints and named secret leases, matching the executable-and-complete anchor.	3 / 3
Workflow Clarity	The reply/context pass is a clear 5-step sequence, but destructive operations (deleting tweets) and account actions lack explicit validate-fix-retry checkpoints, so validation is present for auth but missing for batch/destructive ops.	2 / 3
Progressive Disclosure	Content is well-sectioned but entirely inline in a single ~240-line file with no bundle files (references/scripts/assets absent); rate limits, account info, and secrets could be split out for clearer navigation.	2 / 3
	Total	9 / 12 Passed

Description

67%Weight 40%Scale 1-3

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, naming concrete actions and the two auth modes, but it omits an explicit 'Use when...' trigger clause and lacks common phrasings a user would naturally say, which limits completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause such as 'Use when posting to or reading from X/Twitter, checking mentions, or searching tweets' to lift completeness from 2 to 3.

Broaden trigger terms with natural user phrasings like 'post to X', 'send a tweet', or 'reply to a tweet' to improve trigger_term_quality.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('Check mentions, post tweets, search') plus the specific auth strategies for each class, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly answers 'what does this do' but lacks any 'Use when...' trigger clause, so 'when' is only implied — capped at 2 per the missing-trigger guideline.	2 / 3
Trigger Term Quality	Includes natural terms ('X/Twitter', 'mentions', 'tweets', 'search') but omits common variations users would say like 'post to X', 'send a tweet', or 'DM', so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	A clearly scoped X/Twitter API niche with distinct auth triggers ('app bearer tokens for read-only', 'OAuth 1.0a user context for account actions') makes conflict with other skills unlikely.	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: joelhooks/joelclaw
Path: skills/x-api/SKILL.md
Commit: 979b138

Reviewed: 10 days 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.