social-content

When the user needs to build a LinkedIn authority system, create social content strategy, define content pillars, write posts, or establish thought leadership positioning. Activate on "LinkedIn strategy," "content pillars," "what should I post," or "build my personal brand."

Quality

72%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/social-content/SKILL.md

Quality

Content

62%

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-organized content strategy skill with a clear workflow and good domain-specific frameworks. Its main weaknesses are the lack of fully concrete/executable examples (describing good output rather than showing complete sample posts and calendar entries) and some verbosity in sections where Claude could infer standard practices. The workflow sequencing and mode selection are strong points.

Suggestions

Include at least one complete, fully-written sample LinkedIn post (with hook, body, CTA, and hashtags) rather than just describing what good output looks like in the Examples section.

Show a concrete calendar entry format (e.g., a markdown table with 5 rows of real dates, pillars, formats, and hooks) so the output structure is unambiguous.

Move the Frameworks & Best Practices section (hook formulas, engagement strategy, platform rules) into a referenced file like LINKEDIN-FRAMEWORKS.md to reduce the main skill's token footprint.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some unnecessary elaboration that Claude would already know (e.g., explaining what short paragraphs are, explaining that personal accounts outperform brand accounts). The 'Core Philosophy' quote and some of the rationale text could be tightened. However, most content is domain-specific guidance that adds value.	2 / 3
Actionability	The skill provides concrete frameworks (hook formulas, pillar ratios, review criteria) and good structural guidance, but lacks executable examples — no actual complete sample post is provided, no real calendar template with formatting, and the examples section describes what 'good output' looks like rather than showing it. The guidance is specific but not copy-paste ready.	2 / 3
Workflow Clarity	The workflow is clearly sequenced with 7 numbered steps, includes a critical gate (positioning clarity must come first), offers three distinct modes (Quick/Standard/Deep) with clear scope for each, and the 30-day review process provides a feedback loop for adjustment. The progression from positioning → pillars → calendar → writing → review is logical and well-defined.	3 / 3
Progressive Disclosure	The skill references related skills at the bottom and has clear section headers, but the content is quite long and monolithic. The frameworks/best practices section contains substantial inline content (hook formulas, engagement strategy, platform rules) that could be split into referenced files. The structure is decent but the skill tries to contain everything in one document.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 description does well on completeness by explicitly stating both what the skill does and when to activate it, with good trigger terms that match natural user language. Its main weaknesses are moderate specificity (actions are somewhat high-level) and some overlap risk with general social media or branding skills. The description could benefit from more concrete deliverables and sharper domain boundaries.

Suggestions

Add more concrete deliverables to improve specificity, e.g., 'generate LinkedIn post drafts, create weekly content calendars, design carousel outlines, craft headline hooks'

Sharpen distinctiveness by explicitly scoping to LinkedIn only and excluding other platforms, e.g., 'Use exclusively for LinkedIn—not for Twitter, Instagram, or general social media strategy'

Dimension	Reasoning	Score
Specificity	Names the domain (LinkedIn content/authority) and lists some actions like 'create social content strategy,' 'define content pillars,' 'write posts,' and 'establish thought leadership positioning,' but these are somewhat high-level and not deeply concrete (e.g., no mention of specific formats, templates, or deliverables).	2 / 3
Completeness	Clearly answers both 'what' (build LinkedIn authority system, create content strategy, define pillars, write posts, establish thought leadership) and 'when' (explicit 'Activate on' clause with specific trigger phrases). Both components are explicitly stated.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would actually say: 'LinkedIn strategy,' 'content pillars,' 'what should I post,' 'build my personal brand,' 'thought leadership,' and 'write posts.' These cover a good range of how users would naturally phrase requests.	3 / 3
Distinctiveness Conflict Risk	While LinkedIn-specific terms help distinguish it, phrases like 'social content strategy' and 'personal brand' could overlap with broader social media or branding skills. The LinkedIn focus provides some distinctiveness but 'content pillars' and 'thought leadership' are generic enough to potentially conflict with general marketing skills.	2 / 3
	Total	10 / 12 Passed

Validation

90%

Warnings & errors only

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: shawnpang/startup-founder-skills
Commit: 4ad31b4

Reviewed: 3 months ago

Table of Contents

Discovery Implementation Validation

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.