How to use the Build Daily Inspiration Sites agent skill

What an agent skill is and what this one does

An agent skill is a folder containing a SKILL.md file of instructions, plus optional reference files and scripts, that an AI agent loads when your request matches the skill's description. This skill is for a specific job: taking a completed five-item UI inspiration pack and producing five separate landing pages.

For each reference item, the skill defines a new brand, copy, pricing, proof points and imagery. It then creates one Codex task per item. Each task builds one single-route HTML landing page, runs a production build, commits the validated source and publishes it privately through Sites.

• Reads a dated *-ui-inspiration-capture article folder with manifest.json, content.md and full-page images.
• Validates the capture with scripts/validate_capture.mjs before building anything.
• Creates exactly five tasks, each attached to one full-page reference image.
• Reports a mapping of reference to replacement brand and each task's status.

Install the skill from the ZIP

Download the ZIP of this skill from our page and unzip it. The folder should contain SKILL.md, agents/openai.yaml, references/thread-brief-contract.md and scripts/validate_capture.mjs.

To make it available to Claude Code for all your projects, place the unzipped folder in ~/.claude/skills/. To make it available only inside one project, place it in that project's .claude/skills/ folder.

In the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

• Personal install: ~/.claude/skills/build-daily-inspiration-sites/
• Project install: .claude/skills/build-daily-inspiration-sites/ inside your project

Install the required Node.js and Sites tools

The validation script needs Node.js, because it runs scripts/validate_capture.mjs. The build workflow also needs Codex task and thread tools and the Sites plugin, specifically sites:sites-building and sites:sites-hosting. You need a Sites account for private deployment.

If these are missing, the skill is designed to stop and report a blocker rather than continue in a reduced form.

• Node.js installed and available on your command line.
• Codex task/thread tools available.
• Sites plugin with sites:sites-building and sites:sites-hosting.
• A Sites account for private deployment.

Prepare the capture folder

The skill expects a dated folder named articles/YYYY-MM-DD-ui-inspiration-capture/ in your Content workspace, unless you give it a path. The folder needs a manifest.json with itemCount set to 5 and exactly five items, a content.md file, and one non-empty full-page image per item. Live-site items also need a pageUrl, and each item needs a detailed builder prompt.

If a full-page image is missing, the skill will report it rather than substituting a still, video frame, crop or live-page capture.

• manifest.json with itemCount: 5 and five items
• content.md
• One non-empty local fullPageImage per item
• pageUrl for every live-site item
• One detailed builder prompt per item

How to trigger the skill with a natural request

Name the capture and say what you want built. The skill's description matches requests about turning the daily inspiration references, a five-item UI prompt pack, or a dated *-ui-inspiration-capture article into distinct HTML landing pages. You can also give an explicit article path.

The skill only creates separate tasks when you explicitly ask for separate tasks or threads, so say so in your request if you want that.

• "Turn today's ui-inspiration-capture article into five landing pages, one task each."
• "Use articles/2025-01-15-ui-inspiration-capture as a five-item prompt pack and build separate Sites pages for each item."
• "Build the five inspiration references as distinct HTML landing pages in separate Codex tasks."

What happens during a run

The agent validates the capture, then defines five distinct replacement identities and checks their names against each other. It fills a brief for each item from references/thread-brief-contract.md and creates five tasks. Each task inspects its attached full-page image, builds the page, runs the production build, commits only the site source and deploys privately.

When everything finishes, you get the deployed URL, source location, commit and change summary for each site. Treat a site as complete only after its task reports a successful build and deployment.

• Each task has its own isolated workspace and does not edit the others.
• Reference images are only used for layout and visual rhythm.
• Background tasks skip interactive browser preview unless a real blocker requires it.

Safety notes: scripts and network access

This skill runs a script and uses the network. The validation script is run with Node.js against your manifest.json. The build tasks use Sites to build and publish, so generated sites are deployed automatically to a private Sites deployment.

The skill also forbids reusing the reference brand, logo, copy, people, imagery, layout or any proprietary marks. Review the script and the instructions before installing if you need to audit what runs on your machine.

• Runs scripts/validate_capture.mjs with Node.js.
• Uses network access for Sites building and private deployment.
• Generated sites are published without a manual review step, so check them before any public launch.
• Do not point the skill at a competitor's site to copy it.

Tips for better results

Keep the capture tidy: complete manifest fields and one clear builder prompt per item give the tasks better direction. Use a fresh date folder for each pack so the latest-folder lookup picks the right one.

Review each deployed page against the originality rules before sharing it. Check that names, prices, statistics and testimonials all belong to the new brand.

• Give an explicit article path when you have more than one capture folder.
• Make sure every full-page image is present before you start.
• Check that no new brand name is too close to another item's name.