twitter-profile-lookup

Look up Twitter/X profiles - get bio, followers, tweets, and engagement

Quality

76%

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/social/capabilities/twitter-profile-lookup/SKILL.md

Quality

Content

73%Weight 40%Scale 1-5

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

The body delivers executable, well-structured guidance for a simple two-endpoint lookup skill with good error-handling coverage. The main improvements are removing the redundant Tips section and extending examples to cover the profile operation.

Suggestions

Merge the Tips section into Error Handling and Parameters — "Protected/private accounts cannot be accessed" and the rate-limiting note are already stated there, so the duplication only costs tokens (lowest-scoring dimension: conciseness).

Add at least one worked example for the Get User Profile operation, since all three current examples exercise only Get User's Tweets.

Show the optional trim parameter in a request example (e.g. trim: "true" on the user-tweets call) so every documented parameter is demonstrated.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the Tips section largely duplicates Error Handling ("Protected/private accounts cannot be accessed", "Rate limiting may apply") and "How It Works" adds little value. Not 2 because there is no explanation of concepts Claude already knows; not 4 because the redundancy could be trimmed.	3 / 5
Actionability	Provides concrete, executable YAML request specs (provider/method/path/query) with documented parameters and intent-to-operation examples ("What has OpenAI been posting on X?" → Get User's Tweets with handle: openai). Not 5 because examples only cover the tweets operation and the trim parameter is never shown in use.	4 / 5
Workflow Clarity	A simple skill with two unambiguous single-step GET operations; each call is fully specified and error-recovery guidance is explicit ("retry after a few seconds", "add short delays between calls"). The simple-skill exception applies and this is a read-only operation, so no validation checkpoints are required.	5 / 5
Progressive Disclosure	No bundle files exist, and the single-file body is well-organized with clear section headers and appropriate placement of usage, parameters, and error handling. Not 5 because at ~90 lines with a redundant Tips section and detailed Response field listings, the organization could be tightened.	4 / 5
	Total	16 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 concise and specific about what the skill returns, with strong natural keywords and clear niche distinctiveness. Its main weakness is the absence of any "Use when..." trigger guidance, which caps completeness and limits discovery.

Suggestions

Add a "Use when..." clause with concrete triggers, e.g. "Use when the user asks about a Twitter/X account, wants to see someone's tweets, or asks who @username is" — this directly lifts the completeness score.

Include natural trigger variations users actually say, such as "X handle", "@username", or "recent posts", to improve trigger-term coverage.

Optionally name one or two more returned data points (e.g. verified status, media) to round out the action list toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("get bio, followers, tweets, and engagement") but the opening "Look up Twitter/X profiles" is generic and coverage has minor gaps (no following counts, media, or tweet-history scoping). Not 5 because the action list is not comprehensive; not 3 because it goes well beyond naming the domain with 1-2 actions.	4 / 5
Completeness	Has a clear "what" (profile lookup returning bio, followers, tweets, engagement) but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. Not 2 because the "what" is concrete, not vague.	3 / 5
Trigger Term Quality	Good natural keyword coverage ("Twitter/X", "tweets", "bio", "followers", "engagement") that users would plausibly say. Not 5 because common variations like "@username", "X handle", "recent posts", or "who is" phrasing are missing.	4 / 5
Distinctiveness Conflict Risk	Twitter/X profile lookup is a clear niche with distinct triggers (bio, followers, tweets) and minimal conflict risk with other skills. Clearly matches the anchor-5 example's pattern of a specific domain with concrete triggers.	5 / 5
	Total	16 / 20 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: gooseworks-ai/goose-skills
Path: skills/social/capabilities/twitter-profile-lookup/SKILL.md
Commit: cc3e518

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