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".
86
86%
Does it follow best practices?
Impact
Pending
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 a strong skill description that clearly communicates what the skill does (post content and articles to X/Twitter with media support), how it works (Chrome with CDP), and when to use it (with four natural trigger phrases). It is concise, specific, and distinctive with excellent trigger term coverage across both platform name variants.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: posting content, posting articles, supporting images/videos, long-form Markdown articles, and describes the technical approach (real Chrome with CDP). Very concrete and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (posts content and articles to X with image/video support and long-form Markdown articles) and 'when' (explicit 'Use when...' clause with four specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'post to X', 'tweet', 'publish to Twitter', 'share on X'. Also includes both platform names (X and Twitter), and mentions 'articles', 'images/videos' which users would naturally reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific platform (X/Twitter) with specific posting actions. The mention of CDP and anti-automation bypass further narrows the niche. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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, actionable skill with clear executable commands for each post type and good progressive disclosure via reference files. Its main weaknesses are some repetition (the manual publish note appears four times, extension support is mentioned twice) and a lack of explicit end-to-end workflow with validation checkpoints beyond the article image check. The template variable approach ({baseDir}, ${BUN_X}) is practical but adds some cognitive overhead.
Suggestions
Consolidate the repeated 'Script opens browser with content filled in. User reviews and publishes manually' note into a single prominent callout at the top of the post types section rather than repeating it four times.
Add a brief end-to-end workflow sequence (e.g., 'pre-flight check → compose → run script → verify browser output → user publishes') with explicit validation checkpoints, especially for first-time use.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables, but has some redundancy — the 'Note: Script opens browser with content filled in. User reviews and publishes manually.' is repeated four times verbatim, and the Extension Support section at the bottom duplicates the Preferences section. The script directory resolution instructions are somewhat verbose. | 2 / 3 |
Actionability | Provides fully executable bash commands for every post type with clear parameter tables. The troubleshooting section includes a concrete kill command. Pre-flight checks have specific fix guidance per platform. All commands are copy-paste ready (modulo the template variables which are clearly explained). | 3 / 3 |
Workflow Clarity | The agent execution instructions provide a clear 4-step setup sequence, and post type selection logic is well-defined. However, there's no explicit end-to-end workflow with validation checkpoints — e.g., no 'run pre-flight → post → verify success' sequence. The troubleshooting auto-retry for Chrome debug port is good, but the Post-Composition Check for articles is the only validation step mentioned, and there's no general error recovery flow. | 2 / 3 |
Progressive Disclosure | Well-structured with a clear overview, script reference table up front, and appropriate delegation to reference files (references/regular-posts.md, references/articles.md) and EXTEND.md. References are one level deep and clearly signaled. Content is appropriately split between the main skill file and supporting documents. | 3 / 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
505a7e1
- 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.