Skill Spotlights
-
Agent Skills: The Four Bytes Four Gates Missed
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…
-
What the JetEngine REST API actually reaches
JetEngine’s REST API exposes two routes with different authentication behavior. Learn what the live endpoint tests proved, and where reads and writes stop.
-
The Slide Deck Check That Read Four-Pixel Text
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 Are a Count, Not a Convention
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.
-
Our content audit measured the wrong surface
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.
-
Why subscription reconciliation closes on a stale number
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 Reported Success on Wrong Data
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.
-
When a payment webhook lies about the money
A payment webhook acknowledgement proves delivery, not durable state. The four surfaces that return success while the money state they imply does not exist.
-
Stale but true: the hardest bug in AI agent memory
Why AI agents can retain accurate but outdated memories, how stale context affects decisions, and what to verify before reusing stored information.
-
AI Code Review Gave Five Stars to a Truncated File
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.