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.
70
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 its specific purpose, includes natural trigger terms users would use, and explicitly states both what it does and when to use it. The mention of the reverse-engineered API adds useful context about implementation details. The description is concise yet comprehensive, with strong distinctiveness from other potential 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 common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining X/Twitter content with markdown conversion. The specific platform references (x.com, twitter.com) and format (YAML front matter) make it very unlikely to conflict with other skills. | 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 checkpoints. Its main weakness is length — several sections (first-time setup questions, consent flow details, media workflow) could be moved to reference files to keep the SKILL.md as a concise overview. The skill does a good job of specifying exact commands, file paths, and decision trees for Claude to follow.
Suggestions
Move the detailed first-time setup questions (Question 1-3 with all options) to the referenced `references/config/first-time-setup.md` and keep only a summary in SKILL.md
Consolidate media download information — it's currently spread across Preferences, Options, Output, and Media Download Workflow sections with overlapping content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy — the media download workflow is explained in multiple places (preferences section, media download workflow section, options table), and the user input tools preamble is generic boilerplate that could be trimmed. The consent flow and first-time setup are detailed but necessarily so given the complexity. | 2 / 3 |
Actionability | Provides concrete, executable bash commands, specific file paths, exact JSON structures for consent files, CLI flags with clear descriptions, and precise AskUserQuestion parameters. The consent flow, setup flow, and conversion workflow are all copy-paste ready with specific commands and expected outputs. | 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 decision points, and branching logic. The consent flow includes validation (check file → verify version → proceed or prompt), and the media workflow has a clear conditional check before prompting. The BLOCKING annotation on first-time setup is an explicit checkpoint. | 3 / 3 |
Progressive Disclosure | References a `references/config/first-time-setup.md` file and `scripts/main.ts` for deeper details, which is good. However, the SKILL.md itself is quite long with substantial inline detail (the full first-time setup questions, consent flow, media workflow) that could be split into reference files. The EXTEND.md preferences section is particularly verbose for an overview document. No bundle files were provided to verify reference accuracy. | 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
a44bb08
- 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.