Analyzes social media campaign performance across platforms with engagement metrics, ROI calculations, and audience insights for data-driven marketing decisions
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-code-skill-factory --skill social-media-analyzer53
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
60%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 effectively communicates specific capabilities around social media analytics with concrete actions like ROI calculations and engagement metrics. However, it lacks explicit trigger guidance ('Use when...') and could benefit from more natural user keywords including specific platform names. The description is well-written in third person but needs clearer activation criteria.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when analyzing social media performance, reviewing ad campaigns, or when the user mentions Facebook, Instagram, Twitter, LinkedIn analytics, or marketing ROI'
Include specific platform names and common variations users would naturally say: 'Facebook ads', 'Instagram insights', 'Twitter analytics', 'ad spend', 'campaign metrics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'analyzes social media campaign performance', 'engagement metrics', 'ROI calculations', and 'audience insights'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' (analyzes campaigns, calculates ROI, provides insights) but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied through the domain description. | 2 / 3 |
Trigger Term Quality | Contains relevant keywords like 'social media', 'campaign', 'engagement metrics', 'ROI', 'marketing', but missing common variations users might say like 'Facebook ads', 'Instagram analytics', 'Twitter metrics', 'ad performance', or specific platform names. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to social media marketing analytics, but could overlap with general analytics skills, marketing skills, or data analysis skills. The 'social media campaign' focus helps but isn't strongly distinctive. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a product description or README than actionable guidance for Claude. It extensively describes capabilities and limitations but fails to provide any executable code, concrete workflows, or step-by-step instructions. The mentioned scripts are never shown or explained, leaving Claude without the actual tools to perform the analysis.
Suggestions
Add executable Python code examples showing how to use calculate_metrics.py and analyze_performance.py with sample input/output
Create a clear numbered workflow: 1) Load data, 2) Validate completeness, 3) Calculate metrics, 4) Generate report - with specific commands at each step
Replace the 'Capabilities' bullet list with a quick-start example showing a complete analysis from input data to output report
Include actual metric calculation formulas or code snippets (e.g., engagement_rate = (likes + comments + shares) / reach * 100)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some unnecessary sections like 'Capabilities' that list features Claude could infer. The 'How to Use' examples and 'Best Practices' add value but could be tighter. | 2 / 3 |
Actionability | The skill lacks any concrete, executable code or commands. It mentions scripts like 'calculate_metrics.py' but provides no actual code, function signatures, or usage examples. The guidance is entirely descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | No clear workflow or sequence is provided. The skill describes what it can do but never explains how to actually perform an analysis step-by-step. No validation checkpoints or error handling guidance exists. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, but it's somewhat monolithic. References to scripts exist but no links to detailed documentation. The structure is reasonable but could better separate overview from detailed reference material. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
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.