CtrlK
BlogDocsLog inGet started
Tessl Logo

baoyu-post-to-x

Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown). Uses real Chrome with CDP to bypass anti-automation. Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X".

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is baoyu-post-to-x in jimliu/baoyu-skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with executable commands, a preview/submit validation pattern, and correctly signaled one-level references. The only weakness is mild verbosity from redundant EXTEND.md ASCII tables.

Suggestions

Remove the EXTEND.md path/location ASCII table — the bash block immediately above already shows both paths; keep only the code.

Drop the Found/Not-found action table and replace it with a single line ('Read and apply if found, otherwise use defaults').

Trim the Notes and Extension Support footer, which restates guidance already covered in Preferences and the per-section examples.

DimensionReasoningScore

Conciseness

Mostly lean (code blocks and tables, no concept explanations), but the EXTEND.md ASCII path/location table duplicates paths already shown in the bash block, and the Found/Not-found action table states the self-evident.

2 / 3

Actionability

Copy-paste-ready bash commands for every post type with inline preview/submit variants and concrete parameter tables.

3 / 3

Workflow Clarity

Each post type has a clear preview-then-submit sequence, and 'Always preview before --submit' plus default-preview semantics provide an explicit verification checkpoint for the irreversible post action.

3 / 3

Progressive Disclosure

Body is an overview with a scripts table and one-level-deep references to references/regular-posts.md and references/articles.md, both of which exist as real bundle files.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, third-person description that states concrete capabilities and provides explicit, natural-language triggers. It matches the rubric's good-overall pattern of capabilities plus a 'Use when...' clause.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'regular posts with images/videos', 'X Articles (long-form Markdown)', and the CDP-based mechanism — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (post content/articles to X) and when ('Use when user asks to...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Natural triggers users would actually say are covered: 'post to X', 'tweet', 'publish to Twitter', 'share on X'.

3 / 3

Distinctiveness Conflict Risk

Niche is narrow (posting to X/Twitter) with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anbeime/skill
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.