SkillAgentSearch skills...

create-website

Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorec…

Install / Use

npx skills add wondelai/skills --skill create-website

Installs into whichever agent you are using.

About this skill
πŸ“„

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of create-website

create-website scores 87/100 on our quality scale, 259th of 395 Communication skills we index.

Its SKILL.md is 22 KB long, well organised into 19 sections and no code examples: a thorough specification that gives an agent plenty to work with.

With 2,248 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
13/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so create-website is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk β€” read a skill before letting an agent act on it.

create-website compared with similar skills

All 4 of these similar skills score higher than create-website; compare them before choosing.

SkillScoreStarsUpdatedFormat
create-website (this skill)by wondelai872.2k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install create-website?
Run npx skills add wondelai/skills --skill create-website. The install tabs above show the steps for each supported agent.
Which AI agents does create-website work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is create-website safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is create-website still maintained?
The repository was last updated about 2 months ago, so create-website is actively maintained.

name: create-website description: 'Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (POSITIONING.md, WEBSITE.md, CREATE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new website or landing page from scratch, turn a validated idea into a page that converts, or says ''build me a landing page for my SaaS''. Site already exists: use improve-website site-wide, conversion-optimization for one flow, or grow-website for traffic; building a software product, not a marketing site: create-app; no positioning yet: create-business first, or the positioning phase here. For one framework in isolation, invoke that skill directly.' license: MIT metadata: author: wondelai version: "1.0.2"

Create a Website

A blank page becomes a live, high-converting website through ten phases run in one dependency-respecting order: message, then design, then conversion, then a brutal review. This journey is interactive β€” the agent asks before every decision and never designs before the message is settled β€” and resumable, because every decision and artifact lives in the project's docs/ folder. You drive the phases; the constituent skills carry the method.

Core Principle

Message before design, design before conversion β€” in that order; looks-fine is the floor, not the goal. A visitor decides in five seconds whether to stay, and that decision rides on whether they instantly understand what you do and why it matters to them β€” so clarity comes first and design serves it. This skill sequences the phases, asks the questions, and records the decisions; the constituent skills carry the frameworks. Invoke them rather than improvising their method.

Journey Map

| Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1 | one-page-marketing | Who is this for, and what is the site's one job? | Creates docs/MARKETING.md; extends docs/CUSTOMER.md | | 2 | storybrand-messaging | What do we say, with the customer as hero? | Creates docs/POSITIONING.md, docs/WEBSITE.md | | 3 | made-to-stick | How do we make the message memorable? | Extends docs/POSITIONING.md, docs/WEBSITE.md | | 4 | top-design | What makes this page unforgettable to look at? | Creates docs/DESIGN.md | | 5 | web-typography | Is the type readable as well as dramatic? | Extends docs/DESIGN.md | | 6 | refactoring-ui | Is the design consistent and systematic? | Extends docs/DESIGN.md | | 7 | ux-heuristics | Can anyone use it without thinking? | Extends docs/DESIGN.md | | 8 | cro-methodology | Why don't visitors convert, and what answers them? | Extends docs/WEBSITE.md, docs/EXPERIMENTS.md | | 9 | scorecard-marketing | How do we capture the not-ready-to-buy majority? | Extends docs/WEBSITE.md, docs/MARKETING.md | | 10 | steve-jobs-design-review | Is it insanely great, or not done? | Extends docs/WEBSITE.md β€” GATE |

Operating Rules

  1. Resume first. Before anything else, read docs/CREATE-WEBSITE-PLAN.md and every artifact in the Journey Map. If the tracker exists, summarize the journey state in 3-5 lines and ask which phase to enter. Done when the user has confirmed an entry point. A journey with a tracker is resumed, never restarted.
  2. Intake on first run only. No tracker: run the Intake below, then create docs/CREATE-WEBSITE-PLAN.md with every phase statused pending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason. Done when the tracker exists and the user has confirmed the phase plan.
  3. Phase entry. Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed / skip / defer β€” phases marked GATE may be deferred, never skipped. Mark the phase in-progress on proceed. Done when the user chose.
  4. Skill invocation and fallback. Load the phase's skill and use it: each phase's Invoke line names the skill by slug β€” use that skill to run the phase. If it is not available, offer: npx skills add wondelai/skills/<slug> --global. If the user declines, run the phase from its Brief β€” the minimum viable method. State which mode you are in.
  5. In-phase decisions. Ask every question under "Decide with the user" β€” with concrete options and your recommendation. Record the choice in the tracker's Key Decisions. A decision made silently is a defect.
  6. Phase exit. Present the draft artifact content for sign-off before writing. On approval: write or extend the docs/ files, update the tracker (status, Key Decisions, Next Actions). Done when the files are written and the phase row shows done.
  7. Artifact discipline. Read before writing; create a file only if missing, otherwise extend β€” add or update your sections, preserve everyone else's. Files are UPPERCASE in docs/. Every recommendation lands as a checkbox or a table row with owner and priority. See references/artifact-templates.md when creating a docs/ file for the first time β€” create it from the full skeleton (all section headings), then fill the sections your phase names.
  8. Every scarcity claim, testimonial, and guarantee on the site must be true. When a persuasion tactic needs inventing evidence, replace it with a tactic that uses evidence you have.

Intake

Ask these before creating the tracker:

  1. What is the product or service, and who is it for? (Gates Phase 1's niche and avatar, and every word of the message.)
  2. Do docs/POSITIONING.md or docs/CUSTOMER.md already exist from a create-business run? (If yes, lighten Phases 1-2 and reuse them; if positioning is thin, add the obviously-awesome optional phase.)
  3. What is the single primary conversion goal β€” start a trial, book a demo, purchase, or take a quiz? (Gates every CTA decision in Phases 1, 8, 9.)
  4. Full multi-page site or a single landing page? (Gates sitemap scope and whether Phases 8-9 apply.)
  5. What is the tech stack and where does the code live? (So design and copy land in real files, not a hand-off doc.)
  6. What proof assets exist today β€” testimonials, results, logos, guarantees? (Gates the Phase 8 persuasion audit and Rule 8.)
  7. How much does craft matter β€” competing on design, or a functional site? (Gates whether Phases 4-5 run fully or lightly.)

Skip heuristics: skip Phase 1 when a prior run already fixed the niche, avatar, and USP; run Phases 4-5 lightly for an internal or throwaway page where craft does not sell (never skip refactoring-ui); skip Phase 9 when one direct CTA suffices and there is no nurture motion; skip Phase 3 only under a brutal timeline β€” and warn that clear-but-forgettable copy evaporates. Then create the tracker from the template and confirm the plan.

Done when docs/CREATE-WEBSITE-PLAN.md exists with every phase statused and the user has confirmed the plan.

Phases

Phase 1 β€” Frame the strategy and pick one niche (one-page-marketing)

Purpose: Decide who the site is for, the USP, and the single primary conversion goal before any page exists.

Brief (fallback): PVP Index β€” score candidate niches on Personal fulfillment, Value to the market, and Profitability, then pick one. "Speak to everyone, speak to no one." Write a USP that passes the swap test: if a competitor's name fits your tagline, it is too generic. Map the Before and During squares to concrete pages, each with one job.

Invoke: Use the one-page-marketing skill with the product and target from intake. Ask for (a) PVP scores for 2-3 niches, (b) a one-paragraph avatar, (c) a swap-test USP, (d) the Before/During squares mapped to homepage, landing, and lead-capture pages.

Decide with the user: Which niche to dominate (recommend the highest PVP score)? What is the single primary conversion goal β€” trial, demo, purchase, or quiz lead?

Artifact: Create docs/MARKETING.md with ## Target Market & Avatar (niche, avatar, USP, primary goal) and ## Before / During / After Grid. Extend docs/CUSTOMER.md with ## Segments & Best-Fit Customer. Update the tracker.

Done when: MARKETING.md names one niche, a swap-test USP, and one primary goal; CUSTOMER.md records the best-fit segment; the user confirmed the niche and goal.

Phase 2 β€” Write the message with StoryBrand (storybrand-messaging)

Purpose: Write the words the visitor judges in five seconds β€” customer as hero, you as guide.

Brief (fallback): SB7 β€” a Character who wants something, a Problem (external/internal/philosophical), a Guide with empathy and authority, a Plan, a call to Action, the stakes of Failure, a vivid Success. Name the internal problem (how it feels), not just the external one. One-liner: "We help [character] who struggle with [problem] to [solution] so they can [result]."

Invoke: Use the storybrand-messaging skill with the avatar and USP from MARKETING.md. Ask for a full BrandScript, homepage copy following the StoryBrand wireframe (header, stakes, value, guide, plan, CTA), and five one-liner variations ranked by repeatability.

Decide with the user: Which one-liner is most repeatable after a single hearing? Confirm the customer, not the brand, is the hero β€” no opening "We…".

Artifact: Create docs/POSITIONING.md with ## Brand Script (StoryBrand), ## One-Liner, ## Key Messages. Create docs/WEBSITE.md with ## Sitemap and ## Page Briefs (wireframe-derived copy blocks). Update the tracker.

Done when: POSITIONING.md holds a complete BrandScript and a locked one-liner; WEBSITE.md has a sitemap and a homepage page brief; the user approved the one-liner.

Phase 3 β€” Make the message stick (made-to-stick)

Purpose: Turn clear copy into memorable copy that survives the closed tab and gets repeated.

Brief (fallback): SUCCESs β€” Simple, Unexpected, Concrete, Credible, Emotional, Story. Fight the Curse of Knowledge. Highest leverage is Concrete: replace every abstraction with a picture ("report generation from 4 hours to 10 minutes"). Add one unexpected hook, one Sinatra-test proof, and one named-customer story.

Invoke: Use the made-to-stick skill with the copy in WEBSITE.md ## Page Briefs and the messages in POSITIONING.md. Ask for a SUCCESs score, concrete rewrites of every abstract benefit, one unexpected hero hook, and a short customer story.

Decide with the user: Approve the sticky rewrites and pick the hero hook. Which numbers and claims are true and citable (this feeds Rule 8)?

Artifact: Extend docs/POSITIONING.md ## Key Messages (sticky versions) and docs/WEBSITE.md ## Page Briefs (concrete copy). Update the tracker.

Done when: every abstract benefit is a concrete outcome with a real, true number, one unexpected hook and one customer story exist, and the copy is signed off.

Phase 4 β€” Design the signature moment (top-design)

Purpose: Make the page look agency-built, not template-built β€” starting from the one screenshot-worthy moment.

Brief (fallback): Every pixel intentional. Start with the signature moment (usually the hero), not the header: dramatic scale (min 10:1 display-to-body), an asymmetric composition, a choreographed load with ~80ms staggered word reveals. Custom cubic-beziers (expo-out 0.16,1,0.3,1), animate only transform/opacity, warm off-blacks (#0a0a0a) not pure black. Custom cursor only if the user opts in.

Invoke: Use the top-design skill with POSITIONING.md and the WEBSITE.md page briefs. Ask for the signature hero design, a custom color system (no AI purple-to-blue gradient), and a scored audit across typography, composition, motion, color, and details.

Decide with the user: What is the signature mom

Truncated for display β€” read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars2.2k
CategoryCommunication
Updated2mo ago
Forks228

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit β€” see the Safety scan above for what the skill file itself contains.

No cautions
create-website β€” Universal Skill: Install & Safety Check | SkillAgent