When the user wants to build personal brand, thought leadership, or IP as a founder on Twitter/X or LinkedIn. Also use when the user mentions "founder brand", "personal content", "build audience", or "grow my following".
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/founder-thought-leadership/SKILL.mdQuality
Discovery
54%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 has strong trigger terms and clear 'when to use' guidance, but critically fails to describe what the skill actually does — no concrete actions, outputs, or capabilities are mentioned. It reads more like a trigger condition than a complete skill description, leaving Claude unable to understand the skill's actual functionality.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Drafts Twitter/X threads, LinkedIn posts, and content calendars for founder personal branding' or 'Creates hook-driven social posts, repurposes long-form content into social snippets, and develops posting strategies.'
Restructure to lead with capabilities before the trigger clause, e.g., 'Drafts social media posts, creates content strategies, and develops brand voice guidelines for founders. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lacks concrete actions entirely. It mentions goals like 'build personal brand' and 'thought leadership' but never specifies what the skill actually does (e.g., draft posts, create content calendars, analyze engagement). There are no specific capabilities listed. | 1 / 3 |
Completeness | The 'when' is well-covered with explicit trigger phrases and a 'Use when' equivalent clause. However, the 'what' is essentially missing — the description never explains what the skill actually does or produces, only the context in which it should be triggered. | 2 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'founder brand', 'personal content', 'build audience', 'grow my following', 'Twitter/X', 'LinkedIn', 'thought leadership', 'personal brand'. These are terms users would naturally use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | The focus on founder personal branding on Twitter/X and LinkedIn provides some niche specificity, but without concrete actions, it could overlap with general social media content skills, marketing skills, or copywriting skills. The founder-specific angle helps but isn't enough to fully distinguish it. | 2 / 3 |
Total | 8 / 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 solid, actionable skill with a clear workflow and well-structured output format. Its main weakness is moderate verbosity — some platform-specific tips and common mistakes sections explain things Claude already knows about social media strategy. The workflow is well-sequenced with a feedback loop, and the examples section effectively illustrates expected output quality.
Suggestions
Trim the 'Platform differences' and 'Building in public works when' sections to only include non-obvious, founder-specific insights rather than general social media knowledge Claude already has.
Consider moving the 'Frameworks & Best Practices' and 'Common mistakes' sections into a separate reference file to keep the main SKILL.md leaner and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanation that Claude would already know (e.g., explaining what 'building in public' means, basic platform differences like posting times, explaining that LinkedIn rewards comments over likes). The 'Common mistakes' section and some best practices are somewhat verbose for an AI that understands social media strategy. | 2 / 3 |
Actionability | The skill provides a concrete workflow with specific steps, a detailed output template with markdown formatting, specific posting cadences (1-2/week pillar, 2-3/week proof, daily engagement), and clear examples of what good output looks like for different prompts. The content calendar table format and IP library structure are copy-paste ready. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced from defining IP territory through to setting up feedback loops. Each step builds logically on the previous one, and step 6 establishes a metrics-based feedback loop. For a non-destructive content strategy skill, this level of workflow clarity with a feedback mechanism is appropriate and well-structured. | 3 / 3 |
Progressive Disclosure | The skill references related skills at the bottom (social-content, content-strategy, landing-page) which is good navigation, but the main content is somewhat monolithic — the frameworks/best practices, common mistakes, and examples sections could potentially be split out. For a skill of this length (~100 lines), the inline content is borderline but leans toward being too much in one file. | 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 | |
4ad31b4
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.