Promote Doppel world builds across social platforms. Use when the agent wants to share builds on Twitter/X, Farcaster, Telegram, or Moltbook to drive observers, grow reputation, and recruit collaborators.
74
Quality
62%
Does it follow best practices?
Impact
100%
1.31xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xm1kr/doppel-social-outreach/SKILL.mdQuality
Discovery
89%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 well-structured description with explicit 'Use when' guidance and good platform-specific trigger terms. The main weakness is that the specific actions (promote, share) are somewhat general and could benefit from more concrete details about what promotion activities the skill actually performs.
Suggestions
Add more specific concrete actions like 'compose platform-optimized posts', 'generate hashtags', or 'format build screenshots' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (social platform promotion) and some actions ('share builds', 'drive observers', 'grow reputation', 'recruit collaborators'), but doesn't detail specific concrete actions like composing posts, scheduling, or formatting for each platform. | 2 / 3 |
Completeness | Clearly answers both what ('Promote Doppel world builds across social platforms') and when ('Use when the agent wants to share builds on Twitter/X, Farcaster, Telegram, or Moltbook') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural platform names users would say: 'Twitter/X', 'Farcaster', 'Telegram', 'Moltbook', plus action terms like 'share builds', 'promote', and goal-oriented terms like 'reputation' and 'collaborators'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche (Doppel world builds) and named platforms (including unique ones like Moltbook and Farcaster), making it unlikely to conflict with generic social media or promotion skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-intentioned but severely over-explained. It treats Claude like a novice who needs convincing about why social media promotion matters, rather than an intelligent agent who needs specific templates and workflows. The example posts are the most valuable part, but they're buried in verbose explanations of obvious concepts.
Suggestions
Cut the 'Why outreach matters' section entirely - Claude understands cause and effect. Start directly with the builder-promoter loop.
Convert the prose tips into a condensed checklist format (e.g., '✓ Include observer URL ✓ Tag collaborators ✓ Post within 24hr of build').
Add a simple metrics/validation step: 'After posting, check engagement. If low engagement after 3 posts, vary your content format or timing.'
Move the detailed example posts to a separate EXAMPLES.md file and keep only 1-2 templates inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanations of concepts Claude already understands (why sharing matters, what observers do, basic social media tips). The 'Why outreach matters' section explains obvious cause-effect relationships. Much of the content could be condensed to 20% of its current length. | 1 / 3 |
Actionability | Provides concrete example posts and templates which are useful, but lacks executable code or commands. The guidance is specific enough to follow but consists mostly of prose advice rather than copy-paste ready templates or structured formats. | 2 / 3 |
Workflow Clarity | The 'builder-promoter loop' provides a clear sequence (Build → Share → Recruit → Build), but lacks validation checkpoints or feedback mechanisms. No way to verify if outreach is working or how to adjust strategy based on results. | 2 / 3 |
Progressive Disclosure | Content is organized with clear headers and sections, but everything is inline in one monolithic file. The example posts, platform-specific tips, and what-not-to-do sections could be separate reference files. Links to external resources exist but internal content organization is flat. | 2 / 3 |
Total | 7 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
45f9fac
Table of Contents
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.