Home/Work/Case 06

Agent
Skills OS

A content system and test lab for the skills AI agents load at runtime. Skills are A/B tested against real agents, and the losers get rewritten.

RoleArchitect & builder
WhenMay–Aug 2026 · Decasonic
StackTypeScript · OpenRouter · Zod
StatusLive
206live agents synced
6steps in the skill loop
2runs per test, with and without
0agents broken when it goes down
01 / The problem

Skills written once,
and never tested.

A skill is a block of instructions an agent loads at runtime. Most teams write one, paste it into a prompt and hope it helps. Nobody can say whether a given skill made a given agent better or worse.

With hundreds of agents in production, that guesswork compounds. A bad skill quietly degrades every agent it is assigned to, and nothing flags it.

02 / How it works

Write, test,
judge, improve.

Createwrite, upload or generate a SKILL.md
Versionevery save is an immutable snapshot
A/B testsame prompt, real agent, twice
Judgestructured verdict
Improvelosers rewritten
Deployassign and pin per agent
03 / Decisions worth explaining

Why it’s
built this way.

01

Test on the real agent

The lab runs the same prompt through a synced production agent twice, once with its normal system prompt and once with the skill, on that agent’s own model. No simulations.

02

Let the loser be rewritten

If a skill loses, a frontier model rewrites it into a new version from both outputs and the judge’s reasoning. Then it gets tested again.

03

Fail open

Agents pull skills at prompt-fetch time. If the service is down they fall back to their base prompts instead of breaking. An outage here must never take down the fleet.

04

Filter what the model suggests

A suggestions engine proposes new skills from real usage. Any agent or skill ID it hallucinates is dropped by schema validation before it reaches the screen.

04 / What I learned

The integration
was the hard part.

  • Wiring it into the Agent Control Panel took three debugging rounds: two path mismatches, then auth, solved with a dedicated inbound key instead of a fake app row that would have polluted the dashboard.
  • A 5-minute cache on the control-plane side means skill changes need a cache clear after reassignment. Documented, not hidden.
  • My own audit caught a real bug: pinned versions should have overridden the “ready” filter, and didn’t.
  • 206 agents synced and pulling skills in production.

Need something like this? I build these end to end, as a full-time engineer, on contract, or with SKAI Group.

Book a 30-min call
Next case · 07AI Product Enhancer
Contact

Let's build

Need your content in Arabic, or an AI product built this carefully? One email is enough to start.