CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baoyu-post-to-x

Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown). In Codex, honor explicit requests for the Codex Chrome plugin/@chrome by using the Chrome Extension workflow; otherwise use Chrome Computer Use when available and fall back to real Chrome CDP scripts only when allowed. Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

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

Highly actionable content with fully executable commands, exact UI targets, and exemplary validation checkpoints and error-recovery loops, including a proper confirmation gate before public publishing. The only weaknesses are minor: some repeated guardrail phrasing and a long main body that could offload more detail to the existing reference files.

DimensionReasoningScore

Conciseness

The body is dense and operational, explaining nothing Claude already knows, and it assumes competence throughout. Minor repetition of guardrail phrasing ('Never use the in-app Browser', 'Do not switch to CDP silently', ask-before-Post restated per flow) could be trimmed, matching anchor 4's 'minor instances' rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

Fully executable guidance: copy-paste commands for all four post types with parameter tables, exact URLs ('https://x.com/compose/post'), exact keystrokes ('super+v'), exact UI targets ('aria-label="Add photos or video"'), and exact error strings with specific remedies ('Not allowed', 'native pipe is closed'). Matches anchor 5's 'copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

Multi-step flows are clearly sequenced with explicit validation checkpoints ('Verify that placeholder's count is 0 before continuing', 'Verify no XIMGPH_ remains', post-composition check, Preview review), feedback loops for error recovery (retry once after 2 seconds; pkill and retry for the CDP port), and a strict publish confirmation gate on the outward-facing action. This matches anchor 5.

5 / 5

Progressive Disclosure

Well-sectioned body with clearly signaled, verified, one-level-deep references ('references/articles.md', 'references/regular-posts.md') that contain the promised detail, plus a script inventory table. However, the ~220-line body carries deep troubleshooting and per-mode recovery detail that could partly live in reference files, so it is not the lean overview-with-references pattern of anchor 5; anchor 4's 'minor organization gaps' fits.

4 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 description with a clear 'what', an explicit 'Use when...' clause containing natural trigger phrases, and a distinct niche. Weaknesses are minor: quote tweets are absent from the capability list, and Codex-internal mode routing consumes description space without adding user-facing capability.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Posts content and articles to X (Twitter)', 'regular posts with images/videos', 'X Articles (long-form Markdown)'), but omits quote tweets and spends a sentence on Codex browser-routing implementation detail rather than capability. Anchor 4 fits: several specific actions with minor coverage gaps, more concrete than the 1-2 actions of anchor 3.

4 / 5

Completeness

Explicitly answers both: what ('Posts content and articles to X (Twitter). Supports regular posts with images/videos and X Articles (long-form Markdown)') and when ('Use when user asks to "post to X", "tweet", "publish to Twitter", or "share on X"') with concrete quoted trigger phrases. This matches anchor 5; the 'when' clause is fully explicit, so anchor 4's 'could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural trigger phrases are well chosen ('post to X', 'tweet', 'publish to Twitter', 'share on X') with synonym coverage across X/Twitter, but a few natural terms are missing (e.g., quote tweet, a .md/Markdown-file trigger). Good coverage with a few gaps matches anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (publishing to X/Twitter) with distinct, unambiguous triggers ('tweet', 'post to X', 'publish to Twitter'); minimal overlap with any other skill category. Matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository

JimLiu/baoyu-skills

Path

skills/baoyu-post-to-x/SKILL.md

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.