twitter-queue
Show articles queued for posting on Twitter/X. Use when the user wants to see what to share.
74
Quality
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/twitter-queue/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a specific domain (Twitter/X article queue) but lacks depth in all dimensions. The trigger phrase 'what to share' is too vague and doesn't capture natural user language. The description would benefit from more specific actions and better trigger terms.
Suggestions
Add more specific trigger terms users would naturally say, such as 'scheduled tweets', 'tweet queue', 'pending posts', 'social media schedule', or 'X posts'.
Expand the 'Use when' clause with explicit triggers like 'Use when the user asks about scheduled tweets, pending X posts, or wants to review their Twitter posting queue'.
Add more concrete actions beyond 'show' such as 'view, filter, or manage articles queued for Twitter/X posting'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Twitter/X articles) and one action (show queued articles), but lacks comprehensive actions like filtering, sorting, or managing the queue. | 2 / 3 |
Completeness | Has a 'Use when' clause but the trigger 'what to share' is vague and doesn't provide explicit, actionable triggers. The 'what' is present but minimal. | 2 / 3 |
Trigger Term Quality | Includes 'Twitter/X' and 'queued for posting' but misses common variations users might say like 'scheduled posts', 'tweet queue', 'pending tweets', or 'social media queue'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to Twitter/X posting queue, but 'what to share' is generic and could overlap with other content sharing or social media skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
87%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 that efficiently communicates a multi-step workflow for managing a Twitter queue. It excels in conciseness and actionability with concrete commands and clear output formats. The main weakness is the lack of validation steps when modifying files in Step 5, which could lead to issues if updates fail partially.
Suggestions
Add validation after Step 5 file modifications: verify index.json was updated correctly and the view file was regenerated before confirming success to the user
Include error handling guidance for Step 5: what to do if obsidian-cli fails or if the note path doesn't exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable commands (obsidian-cli examples), specific file paths, exact JSON structure to read, and copy-paste ready bash commands. The output format template is explicit and actionable. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks explicit validation checkpoints. Step 5 involves file modifications (updating index.json, regenerating views) without validation or error recovery guidance for these potentially fragile operations. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines), the content is well-organized with clear sections (Usage, Options, Instructions with numbered steps, Notes). No external references needed and structure is easy to navigate. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.