CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/viral-generator-builder/SKILL.md

The canonical home for this skill is viral-generator-builder in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

The body is a well-structured, reasonably concise design guide with real executable code for the two most common patterns. Its main weaknesses are mis-fenced code blocks containing markdown, a duplicated persona opening, and the absence of explicit workflow checkpoints.

Suggestions

Fix the ```javascript fenced blocks in 'Generator Architecture' and 'Quiz Builder Pattern' that actually contain markdown tables/text — either remove the fences or switch them to plain markdown so the formatting renders correctly.

Drop the redundant opening Role paragraph that restates the frontmatter description, and trim the marketing phrases to tighten conciseness toward a 5.

Add a short explicit build workflow with checkpoints (e.g. define input → implement algorithm → render shareable result card → verify it passes the Screenshot Test) to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body is efficient — tables, bullet lists, and compact code blocks carry most of the content; the only over-explanation is the opening Role paragraph that restates the frontmatter description and some marketing phrasing ('spreads like wildfire', 'OMG you have to try this') that could be trimmed.

4 / 5

Actionability

It provides mostly executable guidance — real JS for weighted quiz scoring and a deterministic name-hash generator, plus concrete tables for input/result types; minor gaps include ```javascript fenced blocks that actually contain markdown (a formatting error) and pseudocode-ish formula lines.

4 / 5

Workflow Clarity

A loose sequence exists (Input → Magic → Result) and each pattern has a 'When to use' clause, but there are no explicit checkpoints or feedback loops; for this design-guide skill that is acceptable but keeps it at the 'sequence present, checkpoints implicit' anchor rather than above.

3 / 5

Progressive Disclosure

Content is well-organized into Capabilities, Patterns, Anti-Patterns, Related Skills, and When to Use; no external bundle files exist or are needed, and the patterns are compact enough to stay inline, with only minor organization gaps (the three generator patterns could be split into reference files if the skill grows).

4 / 5

Total

15

/

20

Passed

Description

48%Weight 40%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.

The description reads as a marketing persona rather than a precise capability+trigger statement: it conveys the niche but lacks concrete actions and any explicit 'Use when' guidance. Second-person voice and missing trigger phrases keep it middling.

Suggestions

Rewrite in third person and lead with concrete actions, e.g. 'Builds shareable generator tools — quizzes, name generators, avatar generators — and designs results optimized for screenshots and social sharing.'

Add an explicit trigger clause: 'Use when the user wants to build a quiz, personality test, name generator, or other tool designed to be shared on social feeds.'

Replace aspirational fluff ('spreads like wildfire', 'OMG you have to try this') with the concrete trigger terms users actually say.

DimensionReasoningScore

Specificity

The description names the domain (viral/shareable generator tools) with a couple of actions ('You build tools that create identity moments', 'You optimize for the screenshot, the share'), but the actions are generic and persona-flavored rather than concrete; the second-person voice ('You build', 'You optimize') triggers the -1 specificity penalty per the rubric, dropping an otherwise borderline-3 to 2.

2 / 5

Completeness

A recognizable 'what' is present (build shareable generator tools that produce identity moments), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It surfaces some natural terms a user might say ('share', 'screenshot', 'viral', 'spreads like wildfire'), but framed as a persona pitch rather than trigger guidance, and it omits common synonyms users would actually request ('quiz', 'personality test', 'name generator', 'avatar generator').

3 / 5

Distinctiveness Conflict Risk

The viral/shareable-generator niche is mostly distinct with clear triggers, with only minor overlap risk against closely related frontend/landing-page skills; not a 5 because terms like 'share' and 'screenshot' are broad.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.