CtrlK
BlogDocsLog inGet started
Tessl Logo

twitter-profile-lookup

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

65

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/social/capabilities/twitter-profile-lookup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 content is tight and highly actionable, with concrete call examples and clean sectioning appropriate to a simple single-purpose skill. Only minor redundancy (repeated rate-limiting guidance) keeps it from being perfectly lean.

Suggestions

Deduplicate the rate-limiting guidance that appears in both 'Error Handling' and 'Tips'.

Consider noting the optional 'trim' parameter's value in the Tweets example for completeness.

DimensionReasoningScore

Conciseness

Lean and well-organized with minimal padding, though the rate-limiting note is repeated across 'Error Handling' and 'Tips' and could be consolidated.

4 / 5

Actionability

Provides concrete, copy-paste-ready YAML call examples with required/optional parameters and clear example mappings ('handle: sama').

5 / 5

Workflow Clarity

A simple single-purpose skill with two clearly defined, unambiguous operations and no destructive/batch steps, qualifying for the simple-skill exception.

5 / 5

Progressive Disclosure

Under 50 lines with well-organized sections (Setup, When to Use, Usage, Parameters, Response, Examples, Error Handling, Tips) and no bundle files to reference.

5 / 5

Total

19

/

20

Passed

Description

66%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 specific and reasonably distinctive, naming concrete outputs (bio, followers, tweets, engagement). Its main weakness is the absence of an explicit 'Use when...' clause, which leaves the trigger guidance implicit.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when the user asks about a Twitter/X account, wants someone's tweets, or asks who @username is').

Include a few more natural synonym trigger terms like 'X account', 'timeline', or 'recent posts' to broaden keyword coverage.

Reframe in consistent third person (already third person) and ensure both 'what' and 'when' are concretely answered.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('get bio, followers, tweets, and engagement'), giving specific coverage of what the lookup returns.

4 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Twitter/X profiles', 'tweets', 'followers', 'bio'), though it omits some variations like 'X account' or 'timeline'.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Twitter/X profile lookup) with distinct triggers and only minor overlap risk with general social-media skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
Reviewed

Table of Contents

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.