xurl

xurl X API CLI: install, auth, app choice, shortcuts, raw endpoints.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/xurl/SKILL.md

Quality

Content

87%

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

The content is a lean, highly actionable CLI reference with strong conciseness and clear organization. Its main gap is workflow clarity: destructive operations are listed without validation checkpoints or feedback loops.

Suggestions

Add a validation checkpoint before destructive commands, e.g. 'Run `xurl read <POST_ID>` to confirm the target before `xurl delete`', to introduce a feedback loop for destructive operations.

Make the auth verification step explicit in the Auth flow (e.g. 'After `xurl auth oauth2`, run `xurl whoami` to confirm credentials work') rather than only surfacing it later in Quick checks.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable commands with minimal prose, assumes Claude's competence, and avoids explaining concepts Claude already knows, matching the level-3 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands throughout (install, auth, shortcuts, raw endpoint mode), matching the level-3 anchor of specific, executable examples.	3 / 3
Workflow Clarity	Sequenced flows exist (Auth: status -> oauth2; Quick checks: version -> auth status -> whoami), but destructive operations such as 'xurl delete', 'unfollow', and 'unrepost' lack validation checkpoints or feedback loops, which the rubric caps at 2 for destructive operations.	2 / 3
Progressive Disclosure	It is a single self-contained file with no nested references, organized into clear, well-signaled sections (Install, Safety, Auth, Common shortcuts, Raw endpoint mode, Quick checks) with easy navigation, appropriate for a CLI cheat-sheet that needs no external reference files.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 distinctively scoped to the X API CLI, but it relies on category labels rather than concrete actions and omits any explicit "Use when..." trigger guidance. Adding verb-driven actions and a trigger clause would raise the specificity, trigger-term, and completeness dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to interact with the X/Twitter API via the CLI — posting, searching, or managing auth' to lift completeness from 2 to 3.

Replace category labels with concrete verb-driven actions (e.g. 'post and reply to tweets, search timelines, manage OAuth apps, call raw endpoints') to improve specificity.

Include natural user variations such as 'Twitter API', 'tweets', and 'post to X' alongside 'X API' for broader trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists concrete capability areas ("install, auth, app choice, shortcuts, raw endpoints") but these are domain/category labels rather than the verb-driven concrete actions of the level-3 anchor (e.g. "Extract text..., fill forms, merge documents"); it is not vague, yet stops short of comprehensive concrete actions.	2 / 3
Completeness	It answers "what" (the CLI's capability areas) but contains no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	"X API" is a natural term a user would say, but the rest is jargon ("app choice", "raw endpoints", "shortcuts") and common variations like "Twitter", "tweets", or "post to X" are missing, matching the level-2 anchor of some relevant keywords but missing common variations.	2 / 3
Distinctiveness Conflict Risk	"xurl X API CLI" names a clear, specific niche with distinct triggers that is very unlikely to overlap with or wrongly trigger other skills, matching the level-3 anchor.	3 / 3
	Total	9 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: steipete/agent-scripts
Path: skills/xurl/SKILL.md
Commit: bb36883

Reviewed: about 13 hours 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.