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.
90
88%
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
77%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, highly actionable skill with excellent executable examples and clear workflow sequencing. Its main weakness is length and some redundancy—the same concepts (multi-platform posting, default social sets, scratchpad usage) are repeated across multiple sections. The content would benefit from splitting the command reference and examples into separate files to improve scannability.
Suggestions
Move the detailed Commands Reference and Examples sections into separate files (e.g., COMMANDS.md, EXAMPLES.md) and link to them from the main skill, keeping only the Common Actions table and core workflow inline.
Consolidate the multi-platform posting guidance—it's explained in Common Actions, Workflow, and its own section. A single authoritative section with a cross-reference would reduce redundancy.
Trim the 'Handling API key not found errors' section—the three-bullet 'DO NOT' list is overly prescriptive and could be reduced to a single sentence like 'Do not attempt to find or construct API keys; tell the user to run setup and wait.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300+ lines) with some redundancy—the multi-platform workflow is explained in the Common Actions table, the Workflow section, and the Publishing to Multiple Platforms section. The API key error handling section is overly verbose with explicit 'DO NOT' lists. The Tips section repeats information already covered elsewhere. However, most content is genuinely useful reference material rather than explaining concepts Claude already knows. | 2 / 3 |
Actionability | Every command is fully executable with exact CLI syntax, flags, and expected outputs. The examples section provides copy-paste ready commands covering a wide range of use cases including media upload, cross-platform posting, scheduling, tags, and setup. The command reference tables are comprehensive with clear descriptions. | 3 / 3 |
Workflow Clarity | The main workflow is clearly sequenced (check default → list social sets → create drafts → schedule/publish) with explicit decision points. The publishing confirmation safety check is well-placed, the --use-default safety note prevents accidental operations, and the API key error handling has a clear stop-and-wait checkpoint. The multi-platform workflow has explicit steps with validation (create then update pattern). | 3 / 3 |
Progressive Disclosure | The content is largely monolithic—everything lives in a single long file. While it uses sections and tables for organization, the extensive command reference, examples, and detailed workflows could benefit from being split into separate reference files. The skill does reference external URLs (API docs, GitHub repo) but doesn't split its own content across files. For a skill this long, inline command reference tables and 20+ examples make it harder to scan. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- freekmurze/dotfiles
- Commit
05d40bb
- 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.