Guide · Agent skill
How to use the Product Proof SaaS agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The product-proof-saas skill is a set of instructions that an AI coding agent loads so it can create or redesign a software or AI product landing page. Instead of relying on vague marketing claims, the skill pushes the page to show how the product works, using a deterministic demo or clearly labeled sample workflow as the central proof. This guide explains what the skill does, how to install it, how to ask for it, and what to watch for. No prior experience with agent skills is needed.
Quick start
- 1Download the ZIP. Get the product-proof-saas ZIP from the page where you found this guide.
- 2Unzip into a skills folder. Place the product-proof-saas folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder.
- 3Or upload in the Claude apps. Go to Settings → Capabilities → Skills and upload the ZIP.
- 4Describe your landing page. Explain your product, audience and the workflow you want to show in the hero.
- 5Name the skill if needed. Use $product-proof-saas in your request to make the trigger explicit.
- 6Review the sample states. Check that every generated or sample output is real or clearly labeled before publishing.
What the skill makes the agent do
When the skill is active, the agent follows a design playbook for SaaS and AI product pages. The page is organized around one user friction, a hero with a product stage that shows one complete outcome, and a workflow that explains input, processing, draft, edit, approval and publish states.
The skill also sets visual rules: white-to-pale-blue surfaces, near-black text, thin borders, 12–16px radii, one cool signal color, and black primary actions. It includes motion defaults such as 160–220ms control feedback and reduced-motion handling, plus a validation checklist for keyboard use, focus, contrast, 200% zoom and mobile wrapping.
- Pricing comparisons with aligned limits, usage units and footnotes
- FAQ answers linked from ambiguous plan terms
- Removal of invented customers, outcomes, security claims and metrics
Install the skill from the download ZIP
Download the ZIP for this skill from the page where you found this guide. Unzip it so that the product-proof-saas folder, which contains SKILL.md, is placed in your skills directory.
For a personal install, unzip into ~/.claude/skills/. For a single project, unzip into the project's .claude/skills/ folder so the skill applies only to that repository.
You can also upload the skill in the Claude apps. Open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal: ~/.claude/skills/
- Project only: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills
Trigger the skill with natural requests
You do not need a special command. Describe the landing page you want and mention the kind of proof you need. The skill's description covers requests about pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons and FAQ handoffs.
The demo prompts in the package name the skill directly with $product-proof-saas. Using that name makes the trigger explicit.
- Use $product-proof-saas to create an original SaaS landing page where an honest, deterministic workflow demo is the central proof.
- Redesign our AI product homepage so the hero shows the prompt-to-output flow, with every sample state labeled.
- Build a pricing section for our SaaS that aligns usage limits and links ambiguous plan terms to FAQ answers.
Examples of what to ask for
The package includes a demo prompt that recreates an editorial-workflow demo as a standalone index.html. The requested stage shows editable input, a deterministic sample output, a selected direction, version context, progress, and an explicit Sample · not published label.
The skill asks for the run action to move through processing and ready states without pretending to contact a model. Reference links for a Verseo template are listed in REFERENCES.md, but you should treat them as reference material, not as code to copy.
What you need and safety notes
The skill lists no requirements. It does not run scripts and does not use the network. Its files are agents/openai.yaml, demo/index.html, demo/PROMPT.md, REFERENCES.md and SKILL.md.
Because the skill runs no scripts and makes no network calls, the risk is mainly in the generated page content. Review any sample data, claims, prices and outputs before publishing, and remove anything that is not real or not clearly labeled as a sample.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
Tips for better results
Give the agent your real product workflow, real limits and real prices. The skill replaces placeholders, but it cannot know what your product does unless you tell it.
If you have no real outputs, ask for a clearly labeled sample workflow instead of fabricated results. The skill itself says to avoid fake dashboards, fake typing and unlabeled sample output.
- Name the user friction in one sentence before you start.
- Ask for the reduced-motion and keyboard checks to be included in the result.
- Ask the agent to run the validation checklist against the finished page.
What people use it for
- Building a hero with a product stage that shows a prompt-to-output flow
- Redesigning an AI product homepage around one central workflow
- Creating a pricing section with aligned limits and footnotes
- Adding a FAQ linked from ambiguous plan terms in the comparison table
Frequently asked questions
How do I install the product-proof-saas skill?
Download the ZIP from the page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.
Does the product-proof-saas skill require anything else?
The skill lists no requirements. It does not run scripts and does not use the network.
Is the product-proof-saas skill free to use?
The skill is published under the MIT licence. Check the licence file in the repository for the full terms.
What is the difference between a sample workflow and a real one?
A real workflow uses the product's actual application state. Otherwise the skill asks you to label the path as Sample workflow, and it never fakes generation speed or output quality.
Can I use this skill to add testimonials or metrics?
The skill says to remove invented customers, outcomes and metrics. Use only verified examples, real customer evidence or clearly labeled samples.
Who should pick a different tool?
Non-software businesses and simple brochure sites do not fit the product-demo structure, so a different approach is better for them.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits front-end developers, designers, founders and marketers building a landing page for a SaaS or AI product that should show the product working. It is less useful for brochure sites, non-software businesses, or anyone who needs fabricated outputs or metrics presented as real.
Download the skill