Skip to content

aicraftbook/aicraftbook-skills / skills/answer-ready

answer-ready

Verified

Audits one web page's content for how well people, search engines and AI answer engines (Google AI Overviews and AI Mode, Bing Copilot, ChatGPT search, Perplexity) can understand and quote it. Checks the answer-first opening, question-style headings, self-contained sections, unsourced claims, dates and authorship, and unclear entities, then returns prioritised fixes and rewritten passages that keep every fact. Use when someone asks to make a page "AI search ready", optimise it for AI Overviews, GEO or AEO, improve how quotable or citable it is, or review a page's structure for search. Makes no ranking or citation promises.

FileKindSize
CHANGELOG.mdmarkdown903 B
LICENSEother1.0 KB
README.mdmarkdown10.1 KB
SKILL.mdskill md5.1 KB
evals/independent-2026-10-21.jsonconfig66.9 KB
evals/results-2026-10-22.jsonconfig5.2 KB
evals/tasks.jsonconfig8.4 KB
examples/requests.mdmarkdown1.1 KB
references/checklist.mdmarkdown5.6 KB
references/guidance.mdmarkdown5.3 KB
references/rewrites.mdmarkdown3.6 KB
skill.jsonconfig1.3 KB

references/rewrites.md

View on GitHub
# Rewrite patterns

Every rewrite keeps every fact. After each one, list the facts from the original and tick each one in
the rewrite. Placeholders mark what only the owner can supply.

## 1. Answer-first opening

Before:

> Choosing a heating system is one of the biggest decisions a homeowner makes. We've been in the
> business since 2009 and have seen it all. In this article we'll explore heat pumps. Heat pumps can work
> well in cold climates if they are sized correctly, and our customers in Vermont have used them down to
> -15°C.

After:

> Heat pumps can work well in cold climates if they are sized correctly. Our customers in Vermont have
> used them down to -15°C. We have been in business since 2009.

Facts kept: heat pumps can work in cold climates (with the condition "if sized correctly") ✓; Vermont
customers used them down to -15°C ✓; in business since 2009 ✓. Removed: scene-setting sentences with
no facts.

## 2. Generic heading to a question heading

Before: `## Overview` / `## More info` / `## Learn more`

After: `## How much does a parking permit cost?` / `## How long does approval take?` /
`## Where do I apply?`

Each new heading must match what its section actually answers. If a section answers two questions,
split it.

## 3. A section that relies on context

Before:

> ### Pricing
> As mentioned above, it starts at the same price as the previous plan, and the new tier adds SSO.

After:

> ### How much does Atlas Cloud cost?
> Atlas Cloud starts at the same price as the previous plan [ADD: the price, currency and billing
> period]. The new tier adds single sign-on (SSO).

Facts kept: starts at the same price as the previous plan ✓; new tier adds SSO ✓. The product is named
in full, the acronym is spelled out, and the missing price is a placeholder rather than a guess.

## 4. Unsourced statistic

Before:

> Heat pumps cut energy bills by 50%.

After (owner has a source):

> Heat pumps cut energy bills by 50% [ADD: source and date for the 50% figure, and which homes it
> applies to].

If the owner has no source, the rewrite still keeps the figure with the placeholder, and the Fixes table
says: "Source the 50% figure or remove it." Removing it is the owner's decision; do not write a softer
replacement claim for them, because that would be a new fact.

## 5. Opinion stated as fact

Before:

> This is the easiest permit to get in the region.

After:

> In our experience, this is the easiest permit to get in the region.

Facts kept: none changed; the sentence was an opinion and is now labelled as one. Flag that "easiest"
is a superlative with no source.

## 6. Facts locked in an image or table without text

Before: a price table as an image with the caption "See our prices".

After: the same table in HTML (or a list) with every row and column from the image, and alt text that
names what the image shows. If you cannot read the image, ask for the values; do not reconstruct them.

## 7. Dates and byline

Before: "Updated today" at the top; structured data says `"dateModified": "2026-06-01"`.

After: "Last updated [ADD: the real date of the last substantive change]" and the same date in
`dateModified`. Byline: "By [ADD: author name], [ADD: role]" linked to an author page if one exists.

Do not suggest moving the date forward unless the content really changed.

## What a rewrite must never do

- Add a number, name, date, source, quote, example or claim that is not in the original.
- Drop a hedge or condition ("if sized correctly", "may", "in most cases").
- Merge two facts into a new one ("50% savings in Vermont" when the page gives them separately).
- Change the author's position or recommendation.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall