baoyu-danger-x-to-markdown

Converts X (Twitter) tweets and articles to markdown with YAML front matter. Uses reverse-engineered API requiring user consent. Use when user mentions "X to markdown", "tweet to markdown", "save tweet", or provides x.com/twitter.com URLs for conversion.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

75%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 is well-structured, actionable, and concise with clear sequenced workflows and a verified one-level reference, scoring consistently at 4 across dimensions. It could reach 5 by tightening redundant preference sections and adding explicit validate->fix->retry feedback loops for batch/destructive media operations.

Suggestions

Consolidate the Preferences table and Supported Keys table to remove redundancy and tighten the conciseness score.

Add an explicit validate->fix->retry feedback loop for the --download-media re-run step (e.g., re-scan for remaining remote URLs after the second run) to lift workflow_clarity to 5.

Move the detailed first-time-setup question text into references/config/first-time-setup.md and keep only a brief pointer in SKILL.md to improve progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, using compact tables and direct commands with no concept over-explanation; a few sections (Preferences table vs. Supported Keys, repeated AskUserQuestion guidance) could be tightened, matching 'efficient; minor instances that could be trimmed'.	4 / 5
Actionability	Provides concrete, mostly copy-paste ready bash commands, JSON snippets, and explicit AskUserQuestion prompts, with only minor gaps such as the runtime placeholder ${BUN_X} needing resolution, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The consent flow is a clearly sequenced 5-step process with a version-check checkpoint and explicit decline branch, and the media ask-each-time flow is similarly sequenced; not quite reaching explicit validate->fix->retry feedback loops throughout, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with a one-level-deep reference to references/config/first-time-setup.md (verified to exist) and scripts in a subdirectory; minor organization gaps (some preference detail inlined that could live in the reference) keep it at 4.	4 / 5
	Total	16 / 20 Passed

Description

95%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 strong, concise, and third-person, clearly stating both the capability and explicit trigger guidance with natural user phrases. Minor room to enumerate more conversion variants would push specificity to a 5.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Converts X (Twitter) tweets and articles to markdown with YAML front matter', article extraction) but coverage of the conversion variants is slightly less than fully comprehensive, fitting 'several specific actions; minor gaps'.	4 / 5
Completeness	Explicitly answers both 'what' (converts tweets/articles to markdown with YAML front matter, reverse-engineered API) and 'when' (an explicit 'Use when...' clause with concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Includes comprehensive natural trigger phrases users would say ('X to markdown', 'tweet to markdown', 'save tweet') plus concrete URL domains (x.com, twitter.com), matching the 'comprehensive coverage including synonyms' anchor.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (X/Twitter content to markdown) with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	19 / 20 Passed

Validation

68%

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 — 11 / 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
relative_links	Relative link issues: 1 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 2 deeper-than-1-level	Warning

	Total	11 / 16 Passed

Repository: JimLiu/baoyu-skills
Path: skills/baoyu-danger-x-to-markdown/SKILL.md
Commit: 1567581

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