CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-showcase

Generate a comprehensive marketing website for a web app — multi-page with real screenshots, animated GIF walkthroughs, feature deep-dives, and workflow demonstrations. Browses the running app, captures screens and sequences, and produces a deployable site that actually teaches people what the product does. Especially useful for complex or agentic apps that are hard to explain. Triggers: 'showcase site', 'product page', 'show off the app', 'marketing site', 'demo site', 'product showcase', 'explain the app', 'how do I market this'.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

A concrete, well-sequenced generation skill with strong copy-paste examples and useful domain-specific patterns, but it is a long monolithic SKILL.md that inlines reference-grade material, references a bundled script that is not shipped, and carries trimmable common-knowledge content. Fixing the broken bin/ reference and splitting heavy sections into reference files would raise quality on both dimensions.

Suggestions

Ship the capture-screenshots script (or inline the equivalent Playwright commands) so the core workflow step is executable from the bundle as delivered.

Move reference-grade material — browser-frame/phone-frame CSS, enquiry-form patterns, deployment options, agentic-app pattern tables — into files under references/ and keep SKILL.md as a lean overview with clearly signaled one-level-deep links.

Trim common-knowledge passages (SEO meta-tag boilerplate, form-field rationale table) and fix the duplicate '### 5.' section numbering (Explaining Agentic / AI Apps and Screenshot Presentation) so the workflow is easier to navigate.

DimensionReasoningScore

Conciseness

Most content is genuinely domain-specific (browser-frame CSS, GIF capture guidelines, agentic-app patterns), but the ~490-line body includes passages Claude does not need: SEO meta-tag basics, the rationale table for form fields, and multi-section elaboration on deployment and enquiry forms that could each be compressed. It is not 4 because several sections can be meaningfully tightened; not 2 because there is no extensive explanation of concepts Claude already knows.

3 / 5

Actionability

Guidance is mostly executable and copy-paste ready: capture-screenshots invocations with flags, a working Pillow one-liner for GIF assembly, complete HTML/CSS snippets, and concrete deploy commands. It is not 5 because the core capture tool ('shipped in bin/') is not actually present in the skill's bundle, the Playwright MCP GIF-recording steps 1–5 are high-level direction rather than runnable code, and the wrangler example uses placeholder paths.

4 / 5

Workflow Clarity

The Workflow is clearly sequenced (gather input → capture screenshots → generate site → GIFs → presentation → navigation → output) with a depth-levels table and browser-tool detection up front, and the Output step acts as a light verification checkpoint (preview, list placeholder content, report GIF sizes). It is not 5 because there is no explicit validate-and-retry loop, e.g. confirming screenshots/GIFs were actually produced and under size limits before building pages around them.

4 / 5

Progressive Disclosure

The body is one monolithic ~490-line file: substantial material that clearly belongs in separate reference files (browser/phone-frame CSS, form patterns, deployment options, agentic-app patterns) is all inline, and the referenced bin/capture-screenshots script does not exist in the bundle. There is also a section-numbering error (two consecutive '### 5.' headings) that hurts navigation. It is not 2 because section headers and the depth-tiered structure do provide usable organization.

3 / 5

Total

14

/

20

Passed

Description

88%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.

A strong description: concrete third-person capability statements, explicit trigger guidance with natural user phrasings, and a well-defined niche. The only gaps are a couple of common trigger synonyms ('landing page' in particular) and slight overlap risk with generic site-generation skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete, third-person actions — 'Browses the running app, captures screens and sequences, and produces a deployable site' plus 'multi-page with real screenshots, animated GIF walkthroughs, feature deep-dives, and workflow demonstrations' — comprehensively covering what the skill does. It is not the level below (4) because no meaningful capability is left unstated.

5 / 5

Completeness

It explicitly answers both 'what' (generate multi-page marketing sites with real screenshots, GIF walkthroughs, deep-dives; browse the app, capture, produce deployable output) and 'when' ('Especially useful for complex or agentic apps that are hard to explain. Triggers: ...') with concrete trigger phrases. Not 4, because the 'when' is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Eight natural trigger phrases are provided ('showcase site', 'marketing site', 'demo site', 'show off the app', 'how do I market this'), giving good synonym coverage. It is not 5 because very common phrasings a user would naturally say — notably 'landing page' and 'website for my app' — are missing.

4 / 5

Distinctiveness Conflict Risk

The niche (marketing/showcase sites for web apps) is clear and the triggers are fairly specific, but 'marketing site' and 'product page' could also fire for generic website-generation or landing-page skills — the body itself references a sibling 'landing-page' skill, confirming minor overlap risk. Not 3, because the triggers are far more distinctive than 'Works with document files'.

4 / 5

Total

18

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jezweb/claude-skills

Path

plugins/frontend/skills/product-showcase/SKILL.md

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.