or run

tessl search
Log in

baoyu-danger-x-to-markdown

tessl install https://github.com/jimliu/baoyu-skills --skill baoyu-danger-x-to-markdown

github.com/jimliu/baoyu-skills

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.

Average Score

95%

Content

92%

Description

100%

SKILL.md
Review
Evals

Generated

Validations

Total score

14/16
CriteriaScore

skill_md_line_count

SKILL.md line count is 145 (<= 500)

frontmatter_valid

YAML frontmatter is valid

name_field

'name' field is valid: 'baoyu-danger-x-to-markdown'

description_field

'description' field is valid (254 chars)

description_voice

'description' uses third person voice

description_trigger_hint

Description includes an explicit trigger hint

compatibility_field

'compatibility' field not present (optional)

allowed_tools_field

'allowed-tools' field not present (optional)

metadata_version

'metadata' field is not a dictionary

metadata_field

'metadata' field not present (optional)

license_field

'license' field is missing

frontmatter_unknown_keys

No unknown frontmatter keys found

body_present

SKILL.md body is present

body_examples

Examples detected (code fence or 'Example' wording)

body_output_format

Output/return/format terms detected

body_steps

Step-by-step structure detected (ordered list)

Content

Total score

11/12
DimensionScore

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

Overall Assessment

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.

Description

Total score

12/12
DimensionScore

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

Overall Assessment

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.