xurl

X/Twitter via xurl CLI: raw post search, posting, DM, media.

Quality

75%

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-media/xurl/SKILL.md

Quality

Content

81%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 a highly actionable, well-structured CLI reference with strong validation-gated workflows for destructive X actions. Its main weakness is conciseness: the command reference is duplicated across Quick Reference and Command Details, and the auth pitfall is repeated in three sections.

Suggestions

Collapse the Quick Reference table and Command Details into one section to remove duplicated command listings, or keep the table as the index and limit Details to non-obvious cases (media workflow, articles, raw API).

State the default-app auth pitfall once in Troubleshooting and reference it from Agent Workflow rather than repeating the full explanation in three places.

Move the lengthy Docker HOME pitfall block into a short note plus a reference, or trim it to the essential HOME=/opt/data/home commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference with no concept-over-explanation padding, but the ~430 lines include real tightening opportunities: the 29-row Quick Reference table is largely re-expanded in Command Details, and the default-app auth pitfall is restated in three places (callout, Troubleshooting, Agent Workflow).	3 / 5
Actionability	Fully executable throughout: copy-paste-ready bash commands for every operation, a complete Quick Reference table, and concrete examples covering post/search/DM/media/raw-API cases.	5 / 5
Workflow Clarity	The Agent Workflow gives a clear 9-step sequence with explicit validation checkpoints for state-changing actions (verify prerequisites, confirm reachability via cheap reads, confirm intent before writes, require xurl output as proof of success), satisfying the destructive-ops feedback-loop requirement.	5 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and the skill is a single well-sectioned file with clear headers and no nested references; the Quick Reference vs Command Details duplication is a minor organization gap keeping it just below a clean 5.	4 / 5
	Total	17 / 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 specific and highly distinct, naming the xurl CLI and four concrete X/Twitter actions, but it lacks an explicit "Use when..." trigger clause, which caps its completeness. Adding a trigger phrase would lift the weakest dimension.

Suggestions

Append an explicit trigger clause, e.g. "Use when posting to or searching X/Twitter, sending DMs, or uploading media via the xurl CLI."

Expand the action list to hint at fuller coverage (e.g. add "engagement" or "timelines") so specificity reaches comprehensive.

Include a common synonym like "tweet" alongside "post" to broaden natural trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain ("X/Twitter via xurl CLI") and lists several concrete actions — "raw post search, posting, DM, media" — but omits many other capabilities (like, repost, follow, timeline, bookmark), so it stops at minor-gaps coverage rather than comprehensive.	4 / 5
Completeness	The "what" is clear (X/Twitter access via xurl CLI for search/posting/DM/media), but there is no "Use when..." clause or equivalent explicit trigger guidance, so per the rubric cap completeness cannot exceed 3.	3 / 5
Trigger Term Quality	"X/Twitter", "post search", "posting", "DM", "media" are natural user phrases with good coverage of both platform names; a few common terms (tweet, timeline, like, follow) are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	"X/Twitter via xurl CLI" carves out a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

81%

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 — 13 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/social-media/xurl/SKILL.md
Commit: 6680afb

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