Skill Spotlights

Four inspection gates checked 22 agent skills but missed four incorrect bytes. This case shows why teams need different verification methods, not simply more checks of the same kind.

JetEngine's REST API exposes two routes with different authentication behavior. Learn what the live endpoint tests proved, and where reads and writes stop.

A slide deck passed its checks despite four-pixel text. Learn to measure rendered legibility at delivery resolution and verify citations against their exact source spans.

Design tokens need measurable adoption, not just a shared file. Learn how to audit rendered components across light and dark themes and identify styling inconsistencies.

An internal content audit missed defects because it checked stored text instead of rendered pages. Learn how to validate the reader-facing page before release.

A subscription reconciliation that never subtracts anything is not one. Why a cycle close must difference twice, and the repair order that survives contact.

Twelve parallel agents each reported success on a harvest that was quietly wrong. What a slice-level report cannot see, and the reconciliation that can.

A payment webhook acknowledgement proves delivery, not durable state. The four surfaces that return success while the money state they imply does not exist.

Why AI agents can retain accurate but outdated memories, how stale context affects decisions, and what to verify before reusing stored information.

Why a high AI code-review score can miss a truncated file, and how completeness checks, source context, and diff verification can reduce the risk.

An HTTP 200 response does not prove a WordPress post was saved or published correctly. Verify the response, saved record, and public page independently.

A look at AI-content ROI through publishing volume, automation credits, and actual search clicks, with a focus on meaningful results over output.

A 200 status, a passing grade, an integration marked active -- none of them proved anything actually worked. Three real failures we only caught by reading back the actual result.

A reviewer scored our slide gate top marks. A third checker found 18 logic faults — its checks ran on thumbnails where text was 4px tall. Here's the fix.

Our email send gate demanded a hash of content that included the hash itself. A third checker found 12 faults a top-scoring review missed. What we changed.

Our transcript skill was cut off mid-verification and still scored perfect on form. A third checker found 19 logic faults. How v1.1 proves every quote.

Our draft revision skill got a perfect review score. Then a third check found 13 hidden logic bugs. Here is what broke, and the hard gates that fixed it.

Our SEO preflight audit once let a page with no main heading pass at 80 percent. A third check found 20 logic bugs. Now a critical gate blocks outright.

An image production skill scored perfect on form. A third check found 18 logic bugs, including one that delivered the wrong file. Here is what changed.

A skill spotlight: the claims-first gate that runs this site, as a loadable skill — with the QA finding of the canary that was never planted.

A skill spotlight: numeric, machine-checkable voice rules and the self-contradiction v1.0 shipped with — banned lists of three, demanded three findings.

A skill spotlight: symbolic computation with a receipt — 200-bit cross-checks, class-specific verification, and the QA story of the flaw that would have failed correct answers.

A skill spotlight: the MIT-licensed project-planner procedure that makes an agent size tasks at 2-8 hours, estimate three ways, and put a risk table on everything.

An introduction to the SymPy skill for exact symbolic mathematics in AI agents: what it does, when to use it, and how to check the results.