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.
94
88%
Does it follow best practices?
Impact
100%
1.88xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates what the skill does, when to use it, and includes highly specific trigger terms. It uses proper third-person voice, covers both platform name variations (X and Twitter), and occupies a distinct niche that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: converts tweets and articles to markdown with YAML front matter, uses reverse-engineered API requiring user consent. These are clear, concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both what (converts tweets/articles to markdown with YAML front matter) and when (explicit 'Use when' clause with specific trigger phrases and URL patterns). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'X to markdown', 'tweet to markdown', 'save tweet', 'x.com/twitter.com URLs'. These are terms users would naturally use and include both platform name variations (X and Twitter). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — converting X/Twitter content to markdown is very specific and unlikely to conflict with other skills. The mention of x.com/twitter.com URLs and specific trigger phrases make it clearly distinguishable. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with clear multi-step workflows and explicit validation/consent flows. Its main weakness is moderate verbosity — some information is repeated across sections (media download behavior, EXTEND.md paths), and the preferences section is quite detailed for inline content. Overall it provides excellent guidance for Claude to execute the task correctly.
Suggestions
Consider moving the detailed EXTEND.md preferences and first-time setup content to a separate reference file, keeping only a summary in SKILL.md
Remove the redundant 'Extension Support' section at the end since it just points back to the Preferences section already covered in detail
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly detailed and well-structured, but includes some redundancy (e.g., the EXTEND.md paths are shown in both bash commands and a table, media download behavior is explained in multiple places). The consent flow and preferences sections are thorough but could be tightened. Some sections like 'Extension Support' at the end add little value. | 2 / 3 |
Actionability | The skill provides concrete, executable bash commands, specific CLI flags, exact file paths, JSON structures for consent files, and clear AskUserQuestion parameters with specific option text. The guidance is copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Multi-step processes (consent flow, first-time setup, media download ask-each-time flow) are clearly sequenced with numbered steps, explicit validation checkpoints (check consent → display disclaimer → ask → create file), and clear branching logic with tables showing different settings and their behaviors. | 3 / 3 |
Progressive Disclosure | There is one reference to an external file (references/config/first-time-setup.md) which is good, but the SKILL.md itself is quite long with detailed inline content for preferences/EXTEND.md that could be split into a separate reference file. The structure is reasonable but the skill is somewhat monolithic for its complexity. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 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 | 8 / 11 Passed | |
- Repository
- jimliu/baoyu-skills
- Commit
8e2967d
- 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.