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.
Install with Tessl CLI
npx tessl i github:jimliu/baoyu-skills --skill baoyu-danger-x-to-markdownOverall
score
95%
Does it follow best practices?
Validation for skill structure
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 a well-crafted skill description that excels across all dimensions. It clearly specifies the capability (tweet/article to markdown conversion), uses natural trigger terms users would actually say, includes an explicit 'Use when' clause with multiple trigger variations, and has a distinct niche that won't conflict with other skills. The mention of the reverse-engineered API requiring consent adds helpful context about the implementation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Converts X (Twitter) tweets and articles to markdown with YAML front matter' and notes the technical approach 'Uses reverse-engineered API requiring user consent'. Multiple specific capabilities are clearly stated. | 3 / 3 |
Completeness | Clearly answers both what ('Converts X tweets and articles to markdown with YAML front matter') and when ('Use when user mentions "X to markdown", "tweet to markdown", "save tweet", or provides x.com/twitter.com URLs'). Explicit 'Use when' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'X to markdown', 'tweet to markdown', 'save tweet', 'x.com/twitter.com URLs'. Includes both platform names (X and Twitter), file format, and URL patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with distinct triggers specific to X/Twitter content conversion. The combination of platform-specific URLs (x.com, twitter.com) and specific output format (markdown with YAML front matter) makes it highly distinguishable from other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%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-crafted skill with excellent actionability and workflow clarity. The consent flow is particularly well-documented with explicit steps and validation. Minor redundancy exists between the Preferences and Extension Support sections, but overall the content is efficient and executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Content is lean and efficient, using tables and code blocks without explaining concepts Claude already knows. No unnecessary padding or explanations of what X/Twitter is or how APIs work. | 3 / 3 |
Actionability | Provides fully executable bash commands and script invocations. The consent flow has specific file paths, exact JSON structure, and copy-paste ready commands for all platforms. | 3 / 3 |
Workflow Clarity | The consent flow is clearly sequenced with explicit steps (1-5) and decision points. Each step has clear conditions and outcomes, with proper validation checkpoints before proceeding. | 3 / 3 |
Progressive Disclosure | References EXTEND.md for customization but the explanation of EXTEND.md support is somewhat redundant (mentioned in Preferences section and again in Extension Support section). The structure is good but could be tighter. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
87%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' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
- 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.