twitter

Search and retrieve content from Twitter/X. Get user info, tweets, replies, followers, communities, spaces, and trends via twitterapi.io. Use when user mentions Twitter, X, or tweets.

5.61x

Quality

—

Does it follow best practices?

Impact

73%

5.61x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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

A tight, fully executable command reference that excels on conciseness and actionability and gives a clear quick-check verification. The only gap is progressive disclosure: a large inline command catalog with no offloaded reference file.

Suggestions

Move the full per-endpoint command catalog into a references/ file (e.g. ENDPOINTS.md) and keep SKILL.md as a concise overview with the most common commands plus a pointer, to improve progressive disclosure.

Add a one-line note on error/empty-result handling (e.g. what a failed auth or rate-limit response looks like) so Claude can diagnose without guessing.

Dimension	Reasoning	Score
Conciseness	Lean command reference with no explanatory filler about Twitter or APIs; every line is an executable command, flag, or genuinely useful metadata, assuming Claude's competence.	3 / 3
Actionability	Every entry is a copy-paste-ready command with concrete arguments and flags (e.g. `--limit 20`, `--type Latest`), plus worked search-syntax examples.	3 / 3
Workflow Clarity	For this single-action-per-request CLI skill the workflow is unambiguous, and the Quick Check provides a concrete verification step; no batch/destructive operations require validation loops.	3 / 3
Progressive Disclosure	Well-organized into labeled sections with all referenced scripts existing on disk, but it is a flat ~95-line command catalog with no overview pointing to deeper reference docs, keeping it at the structure-could-be-better level.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 well-crafted description: specific actions, explicit use-when triggers, and a clearly distinct niche. It cleanly satisfies every dimension with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Enumerates seven concrete action categories ("Get user info, tweets, replies, followers, communities, spaces, and trends"), matching the multiple-specific-actions anchor rather than just naming a domain.	3 / 3
Completeness	Explicitly answers both what ("Search and retrieve content... Get user info, tweets, replies...") and when ("Use when user mentions Twitter, X, or tweets"), the verbatim score-3 pattern.	3 / 3
Trigger Term Quality	"Use when user mentions Twitter, X, or tweets" supplies the natural terms users actually say, with good coverage of the platform's common variations.	3 / 3
Distinctiveness Conflict Risk	A clear niche (Twitter/X via twitterapi.io) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: resciencelab/opc-skills
Commit: 282acb4

Reviewed: 1 day 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.