typefully
Create, schedule, and manage social media posts via Typefully. ALWAYS use this skill when asked to draft, schedule, post, or check tweets, posts, threads, or social media content for Twitter/X, LinkedIn, Threads, Bluesky, or Mastodon.
83
81%
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 (create, schedule, manage social media posts via Typefully), when to use it (drafting, scheduling, posting, or checking social media content), and covers a comprehensive set of trigger terms including platform names and action verbs. The explicit 'ALWAYS use this skill when...' clause with enumerated platforms and actions makes it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create, schedule, and manage social media posts via Typefully.' These are clear, actionable verbs tied to a specific platform. | 3 / 3 |
Completeness | Clearly answers both 'what' (create, schedule, manage social media posts via Typefully) and 'when' (explicitly states 'ALWAYS use this skill when asked to draft, schedule, post, or check tweets, posts, threads, or social media content' with platform-specific triggers). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'draft, schedule, post, check, tweets, posts, threads, social media content, Twitter/X, LinkedIn, Threads, Bluesky, Mastodon.' These are highly natural and comprehensive. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'Typefully' and the enumeration of specific social media platforms. This creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent executable examples and clear workflows, but suffers significantly from verbosity and redundancy. The same information (e.g., cross-platform posting, analytics commands, scratchpad usage) is repeated across multiple sections—Common Actions, Workflow, Commands Reference, Examples, and Tips. The document would benefit greatly from splitting reference material into separate files and eliminating duplicate content.
Suggestions
Eliminate redundancy by removing the Examples section (or moving it to a separate EXAMPLES.md) since the Commands Reference and Common Actions table already provide the same information with syntax.
Move the Commands Reference tables to a separate REFERENCE.md file and link to it from the main skill, keeping only the Common Actions table and Workflow in SKILL.md.
Trim the 'Handling API key not found errors' section to 2-3 lines—the extensive list of DON'Ts is unnecessary for Claude and wastes tokens.
Remove the Tips section entirely as every tip duplicates information already present in other sections (character limits, thread syntax, scheduling, etc.).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines. There is significant redundancy: the same information appears in the Common Actions table, the Workflow section, the Commands Reference, and the Examples section. The 'Handling API key not found errors' section over-explains what NOT to do. The Tips section repeats information already covered elsewhere. Many concepts are explained that Claude would already understand. | 1 / 3 |
Actionability | Every command is fully executable with exact CLI syntax, flags, and expected outputs. Examples are copy-paste ready with concrete values, and the command reference tables provide comprehensive coverage of all available operations. | 3 / 3 |
Workflow Clarity | The workflow for creating posts is clearly sequenced with numbered steps and conditional branching (check default → list social sets → create draft → schedule/publish). The multi-platform workflow has explicit steps with validation. Safety notes about --use-default and publishing confirmation serve as validation checkpoints. | 3 / 3 |
Progressive Disclosure | While the content has clear section headers and tables for navigation, it's essentially a monolithic document with no content split into separate files. The Commands Reference, extensive Examples section, and detailed LinkedIn Mentions guide could all be separate referenced files. The document is far too long for a single SKILL.md overview. | 2 / 3 |
Total | 9 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (575 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
2c6f6e8
- 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.