viral-generator-builder

You understand why people share things. You build tools that create "identity moments" - results people want to show off. You know the difference between a tool people use once and one that spreads like wildfire. You optimize for the screenshot, the share, the "OMG you have to try this" moment.

Quality

16%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/viral-generator-builder/SKILL.md

Quality

Content

32%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a loosely organized collection of tips, tables, and partial code snippets about building viral generators. It lacks a clear executable workflow, over-explains concepts Claude already knows about UX and sharing psychology, and would benefit significantly from being restructured into a concise overview with separate detailed pattern files. The code examples, while present, are incomplete and embedded in confusingly nested markdown.

Suggestions

Restructure into a concise SKILL.md overview (under 50 lines) with separate files for each pattern (quiz-builder.md, name-generator.md, etc.) to improve progressive disclosure.

Add a clear sequential workflow: e.g., 1. Choose generator type → 2. Design minimal input → 3. Build scoring/generation logic → 4. Design result card → 5. Test screenshot appearance → 6. Add share mechanics.

Remove explanations of obvious concepts (why long forms are bad, why bland cards don't work) and replace anti-patterns with a brief 'avoid' checklist.

Fix the code blocks: they contain nested markdown inside JavaScript fences. Provide complete, executable examples (e.g., a full minimal quiz generator) rather than fragments.

Dimension	Reasoning	Score
Conciseness	Significant verbosity throughout. The 'Capabilities' list is unnecessary padding, the anti-patterns section over-explains obvious points (e.g., 'Every field is a dropout point. People want instant gratification.'), and the role description at the top repeats the frontmatter. Many sections explain concepts Claude already understands about UX and virality.	2 / 5
Actionability	There are some concrete code snippets (scoring logic, deterministic name generator) but much of the content is high-level guidance tables and conceptual frameworks rather than executable, copy-paste-ready implementations. The code examples are fragments embedded in markdown code blocks labeled as JavaScript but containing mixed markdown, reducing executability.	3 / 5
Workflow Clarity	There is no clear sequential workflow for building a viral generator. The content presents patterns and tables but lacks a step-by-step process with validation checkpoints. For a skill involving building tools, there's no build-test-iterate cycle, no validation steps, and no clear sequencing of when to apply which pattern.	2 / 5
Progressive Disclosure	Everything is inlined in a single monolithic file with no bundle files. The content is long enough (well over 50 lines) that it would benefit from splitting patterns into separate reference files. The 'Related Skills' section references other skills but the main content has no structured references to supporting documents.	2 / 5
	Total	9 / 20 Passed

Description

0%Scale 1-5

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 is almost entirely composed of vague, aspirational language and buzzwords with no concrete actions, no trigger terms, and no 'when to use' guidance. It uses second person voice ('You understand,' 'You build') throughout, which further reduces its effectiveness. It would be nearly impossible for Claude to correctly select this skill from a list of available skills.

Suggestions

Replace abstract language with concrete actions the skill performs, e.g., 'Designs shareable quiz results, personality badges, and social media cards that encourage viral sharing.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about viral features, shareable content, social sharing mechanics, or building tools that encourage word-of-mouth growth.'

Switch from second person ('You understand,' 'You build') to third person ('Builds tools that...', 'Optimizes for...') to match the expected voice for skill descriptions.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. There are no specific capabilities listed—only abstract concepts like 'identity moments' and 'optimize for the screenshot.' It never says what the skill actually does.	1 / 5
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause, no concrete description of functionality, and no trigger guidance. Both dimensions are entirely missing.	1 / 5
Trigger Term Quality	There are no natural keywords a user would say when needing this skill. Terms like 'identity moments,' 'spreads like wildfire,' and 'OMG you have to try this' are not phrases users would use to request help. No domain-specific or actionable trigger terms are present.	1 / 5
Distinctiveness Conflict Risk	The description is so vague and abstract that it could apply to virtually any creative, marketing, or product-building skill. There is nothing that carves out a distinct niche or differentiates it from other skills.	1 / 5
	Total	4 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/viral-generator-builder/SKILL.md
Commit: 900c504

Reviewed: 3 hours 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.