intelligence.md · Ep 03 · 22 October 2026 · 49 min
53 Free Agent Skills That Check Your AI's Work
with Christoffer Tyko · hosted by Kerstin Dallinger
The video loads from YouTube when you press play. Privacy
About this episode
Christoffer Tyko, founder of Tyko Tech, explains how he checks the work of AI coding agents instead of taking the model's word for it. He separates the application harness, which a tool such as Claude Code controls, from the user harness, which a person controls through skills, and describes why AI output varies and how Python scripts make steps repeatable. He then walks through Supreme Team, his open source set of 53 skills organised into teams under an agent called the Admiral, with intake and grilling, tiers for small and large changes, adversarial review gates and hooks that run outside the agent. He shows how run history is saved as files in the codebase, so work can move from Claude Code to Codex, reads an evidence log from a real run and installs the skill set live. The episode helps people who build with coding agents, including non-developers, and want a way to verify the results. Host Kerstin Dallinger moderates and passes on one audience question.
Key takeaways
What is the difference between an application harness and a user harness?
Christoffer Tyko describes the application harness as the part you do not control, such as the memory, chat session, hooks and rules that live inside Claude Code. The user harness is the side you do control, and he says the key to making it work is skills, which he treats as instructions, the way you would brief a capable colleague (4:30).
Why does an AI agent never give the same answer twice, and what helps?
He explains that AI systems are probabilistic, so you will never get exactly the same outcome every time. Agents increasingly run commands through Python or bash scripts, because a script always gets the same outcome (5:58). Later he adds that you cannot make the AI deterministic, but you can give it a deterministic tool set around it (36:24).
What is adversarial review and how does it check an agent's work?
Christoffer Tyko says language models are trained mostly on reward and punishment, and adversarial review uses that by rewarding the model for finding lies, discrepancies and bugs. The reviewer compares what the team built with the original specification and tries to tear the design down (13:20). He says this only works when an intake step has first produced a clear start and a clear goal to compare against (17:34).
Why use hooks and not only skills?
He says that without hooks there is no guaranteed way of executing the Python scripts, and you do not want the model to decide when a hook is triggered. Hooks sit between the model and the operating system, so commands pass through them first, and because they run outside the agent it cannot circumvent them (22:36, 42:38).
How can you keep an AI project's memory when you switch from Claude Code to Codex?
He saves the whole run history as files in a folder in the codebase, including intake files, artifacts, designs and revisions. Because the memory lives in the project and not in the application, a crashed tool can resume from a checkpoint and the work can continue in a different coding agent (25:50).
When does the human have to step in during an agent pipeline?
After the initial conversation and the intake, Christoffer Tyko says the responsibility passes to the Admiral. A failed step is first revised within the team, then by the Admiral, and each step gets three tries. If the same step fails three times, the person becomes the decision maker (45:27, 46:17).
Chapters
- 0:00Intro: Christoffer Tyko and Tyko Tech
- 2:08How do you check an AI agent's work?
- 3:41Application harness vs. user harness
- 5:00What skills really are
- 5:58Why AI never gives the same answer twice
- 7:08What was missing in other skill sets
- 10:4653 skills, teams and the Admiral
- 13:20Adversarial review: rewarding the AI for finding bugs
- 14:56Tiers: no full pipeline for a button change
- 16:36Intake and grilling
- 22:36Hooks: making the agent follow the rules
- 25:50Memory in your codebase: switch from Claude Code to Codex
- 28:54Supreme Team next to gstack, GSD and Superpowers
- 31:13How to install Supreme Team
- 33:40Reading a run: review gates and evidence logs
- 38:29Live demo: installing it and briefing the Admiral
- 42:14Q&A: why hooks and not just skills?
- 44:48When does the human step in?
- 46:49Wrap-up