CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

popnow-landing-page-from-mockup

Designs a landing page as pictures first and code second - two or three full-page mockups in clearly different art directions, the user picks one, then the agent builds it as semantic, responsive HTML/CSS (or in the user's framework) with real copy, accessible contrast and properly sized imagery, screenshots it on desktop and phone, compares it with the mockup, and runs a de-AI pass before delivery. Use it when someone wants a marketing or product landing page that does not look like every other generated page, or when a page they have reads as generic and needs a redesign. The skill is free; generating images through the PopNow API is paid from the separate API USD balance, and the agent quotes USD before any paid run.

Quality

87%

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

81%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 highly actionable, well-sequenced workflow with real commands, thresholds, validation gates and a sensible one-level reference structure. Its weaknesses are token efficiency — the PopNow sections read as vendor marketing rather than instructions — and a broken `evals/` entry in the Files table. Trimming the promotional material would raise an otherwise strong skill.

Suggestions

Cut the promotional copy: drop the four justification bullets under "PopNow generation" ("Made for this skill", "Finished media, not loose files", "No surprise bills", "Yours to use") and the entire "About PopNow" section, keeping only the procedural rules (quote -> confirm -> create) and the model/cost table; move any needed rationale into references/mockups.md.

Fix the Files table: remove the `evals/` row or actually ship the directory — it currently points at a path that does not exist in the bundle.

Trim pricing chatter from the description and body to a single line near the payment step ("paid from the separate API USD balance; quote before every run") so the trigger text and workflow stay focused on capability.

DimensionReasoningScore

Conciseness

The workflow itself is lean and instructional, but the "PopNow generation" section carries promotional justification bullets ("Made for this skill", "No surprise bills", "Yours to use") and the entire "About PopNow" section is marketing copy ("the AI studio for finished, on-brand media… 140+ one-tap trending video effects") that teaches the agent nothing. This is "mostly efficient but includes some unnecessary explanation" rather than the minor-trimming case of a 4, yet not padded enough across the board for a 2.

3 / 5

Actionability

Guidance is fully executable throughout: exact commands ("node scripts/mockup-prompts.mjs work/brief.json --out work/prompts.json", "node scripts/shoot-diff.mjs review site/index.html --mockup <mockup.png> --out review", "python3 scripts/popnow.py quote"), concrete numeric thresholds ("breakpoints around 1100 / 900 / 600 px, contrast 4.5:1", "score 80+", "under about 250 KB at 1600 px"), and a model/cost table with per-step prices. Specific commands cover the common cases end-to-end, matching the copy-paste-ready anchor.

5 / 5

Workflow Clarity

The ten-step workflow is clearly sequenced with explicit validation checkpoints and feedback loops: quoting is gated ("only after a clear yes run the create commands"), the review/lint loop is bounded ("Fix, re-run 8 and 9; three rounds at most"), and a Quality checks section plus the delivery checklist close the process. Paid and batch operations all have verify-before-proceed gates, matching the top anchor.

5 / 5

Progressive Disclosure

Structure is good: detail files are one level deep, linked inline at the exact workflow step where they matter ([references/art-directions.md], [references/mockups.md], [references/mockup-to-code.md], [references/review-loop.md], [references/de-ai-pass.md]), all of which exist in the bundle, plus a Files table indexing every script and reference. It falls short of a 5 because the Files table lists an `evals/` directory that does not exist in the bundle — a broken navigation entry; it is well above a 3 since content split and signaling are otherwise clean.

4 / 5

Total

17

/

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 third-person description that comprehensively states concrete capabilities and pairs them with an explicit, well-phrased "Use it when" clause. Keyword coverage is good but not exhaustive of natural synonyms, and the generic web-build framing creates slight overlap risk. The trailing pricing/billing sentences add length without improving trigger matching.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the whole workflow: "two or three full-page mockups in clearly different art directions", "builds it as semantic, responsive HTML/CSS (or in the user's framework) with real copy, accessible contrast and properly sized imagery", "screenshots it on desktop and phone, compares it with the mockup, and runs a de-AI pass". This matches the comprehensive-coverage anchor; it is not a 4 because there are no meaningful gaps across design, build, verification and delivery.

5 / 5

Completeness

Both halves are explicit: the "what" is a full mockup-first build-and-verify pipeline, and the "when" is a concrete "Use it when someone wants a marketing or product landing page that does not look like every other generated page, or when a page they have reads as generic and needs a redesign". This matches the anchor for clear and explicit what AND when with concrete trigger phrases; a 4 would require the when-clause to be less specific than it is.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "marketing or product landing page", "needs a redesign", "reads as generic". It falls short of the 5 anchor because common synonyms and variations ("homepage", "one-pager", "launch page", "startup site") are missing; it is above a 3 because the included terms are exactly what a user would naturally say.

4 / 5

Distinctiveness Conflict Risk

A clear niche (mockup-first landing page design) with distinct triggers, but "builds it as semantic, responsive HTML/CSS (or in the user's framework)" leaves minor overlap with general web-page-building skills on requests like "build me a website". Mostly distinct with minor overlap risk matches the 4 anchor; the 5 anchor's "minimal conflict risk" is not fully met.

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

popnow-ai/popnow-skills

Path

skills/popnow-landing-page-from-mockup/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.