Use case

Free tools that work before they ask for anything.

Turn a utility idea into a working page in your repo — input, output, examples, CTA, FAQ, and schema included. No signup wall. No fake lead magnet.

$ bunx skills add ReScienceLab/pagewell --skill pagewell

Installs the Pagewell agent skill via skills.sh.

Try the page brief generator

Value first

Value first, ask later

The free-tool playbook rejects fake tools that only collect email. The utility has to work before any CTA asks for more.

Built in your repo

Astro, Next.js, static HTML, or custom routes should reuse existing layouts, metadata, styles, and client-script conventions.

SEO-ready

SEO-ready out of the box

A durable tool page needs crawlable copy, how-to-use content, FAQ, related links, schema, and a useful deterministic result.

When to use it

Use Pagewell when a free utility can answer demand better than another article.

Free tools work well when the audience has a repeatable input/output job: validate a file, convert text, score a draft, preview output, calculate a number, or generate a starter artifact.

Validator

Check before publishing

Examples: llms.txt validator, PAGEWELL.md validator, schema checker, metadata checker.

Generator

Create a useful starter artifact

Examples: page brief generator, FAQ outline generator, internal-link map generator.

Analyzer

Turn pasted text into a decision aid

Examples: claim-risk analyzer, SEO page genericness grader, search-intent classifier.

Workflow

A Pagewell free-tool run starts with a tool brief, not just a keyword.

tool brief

route: /tools/pagewell-context-validator
pageType: free-tool
primaryKeyword: PAGEWELL.md validator
tool.category: validator
tool.input: PAGEWELL.md draft text
tool.output: score, passes, warnings, required fixes
privacy: client-side only; input is not uploaded

Implementation

The agent should pick the smallest working implementation.

Read PAGEWELL.md and DESIGN.md first so the route matches the site's patterns.
Reuse the existing layout, button, form, card, metadata, schema, and discovery conventions.
Prefer deterministic client-side logic for v1 unless an API is truly necessary.
Add copy/download actions for text outputs when useful.
Include visible how-to-use, examples, FAQ, related links, and product CTA content.

A free tool fails if it is only a landing page.

Pagewell QA checks that the tool works without authentication, validates input, returns useful output, includes WebApplication schema when indexable, and keeps product CTAs after the first useful result.

Check	Pass condition	Why it matters
First value	Primary action works on page load	Avoids fake lead magnets
Privacy	Client-side behavior is truthful	Prevents unsupported data claims
Discovery	Sitemap and llms.txt stay factual	Keeps durable tools findable

FAQ

Common questions, answered directly.

Can Pagewell generate free tools as code?

Yes. Pagewell has a free-tool workflow for no-signup utilities with a working input/output interface, crawlable SEO shell, product CTA, FAQ, and QA checks.

Does Pagewell require React for free tools?

No. Pagewell follows the target repo's conventions. In Astro or static sites, a small framework-free client script is often enough for a first version.

What makes a Pagewell free tool acceptable?

The tool must provide useful output before signup, avoid fake lead capture, include labels and helpful errors, and route users to the product only after first value.

Install Pagewell

Ready to generate pages as code?

Give your coding agent the context, playbooks, adapters, and QA gates it needs before the next page request.