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

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/x-api/SKILL.md

Quality

Content

64%

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

This is a solid, highly actionable skill with complete executable code for both authentication flows and all common X/Twitter API operations. Its main weaknesses are the lack of error handling/validation workflows (especially important for posting and deletion operations) and the monolithic structure that could benefit from splitting detailed reference material into separate files. The content is mostly concise but has room for tightening.

Suggestions

Add explicit validation steps after posting/deleting tweets (e.g., check r.status_code, print r.json() to confirm, handle rate limit 429 responses) to improve workflow clarity for destructive operations.

Split rate limits, full-archive search details, and X Articles guidance into separate reference files to improve progressive disclosure and reduce the main skill's token footprint.

Dimension	Reasoning	Score
Conciseness	Generally efficient with good use of code examples, but includes some unnecessary explanation (e.g., explaining what bearer tokens are for, listing what read-only access covers). The full-archive search notes and some inline commentary could be tightened. The account info section is appropriately brief.	2 / 3
Actionability	Excellent actionability — provides fully executable Python scripts for both auth flows, complete curl commands, and copy-paste ready API call patterns for all common operations. Secret leasing, signing, and revocation are all concrete with real code.	3 / 3
Workflow Clarity	The two auth flows are clearly separated and the common operations section is well-organized. However, there's no explicit validation/error-handling workflow — e.g., no guidance on checking response status codes after posting, no feedback loop for failed API calls, and the destructive operations (delete tweet, post tweet) lack verification steps.	2 / 3
Progressive Disclosure	The content is well-structured with clear headers and logical sections, but it's a fairly long monolithic file (~150+ lines) with no references to external files. The full-archive search details, rate limits, and article handling could be split into separate reference files for better organization.	2 / 3
	Total	9 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description with excellent specificity and trigger term coverage, clearly identifying the X/Twitter platform and listing concrete actions like posting tweets, checking mentions, and searching. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The inclusion of authentication details (bearer tokens, OAuth 1.0a) adds useful technical context but doesn't substitute for explicit trigger guidance.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to tweet, check Twitter/X mentions, search tweets, or interact with the Twitter/X API.'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: read, post, check mentions, post tweets, search. Also specifies authentication methods (app bearer tokens, OAuth 1.0a), which adds technical specificity.	3 / 3
Completeness	Clearly answers 'what does this do' (read/post to X/Twitter, check mentions, post tweets, search) but lacks an explicit 'Use when...' clause. The when is only implied by the actions listed, which caps this at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'X', 'Twitter', 'API', 'mentions', 'tweets', 'search', 'post'. Covers both the old and new platform names (X/Twitter), which is excellent for matching user queries.	3 / 3
Distinctiveness Conflict Risk	Very clearly scoped to X/Twitter API interactions with distinct triggers like 'tweets', 'mentions', 'X', 'Twitter'. Unlikely to conflict with other skills given the platform-specific terminology.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 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: joelhooks/joelclaw
Commit: 2ca3686

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.