In short:
ak-dogfoodreviews the session that is running, lists every skill it used, shows where each one cost time, tokens, a retry or a correction from you, and proposes the smallest change to that exact skill. By default it only reports and changes no file. Measuring one skill across many past sessions belongs toak-skill-creator; looking back over git history belongs toak-retro.
Disclosure: I maintain AgentKit and have an affiliate relationship with it: the AgentKit link in this post is an affiliate link; buying through it gets you 30% off.
Summary
Use it at the end of a session that stumbled: a command from a skill failed and was retried, the agent read the same file twice, you had to step in and correct course, or a check got skipped. Each proposal points at the text that caused it (file:line) or names the missing rule, with a diff hunk, the expected effect and the risk.
flowchart LR
A["The session you just ran"] --> B["ak-dogfood"]
S["session_usage.py from ak-skill-creator"] --> B
B --> C["Report: skills used, stumbles, proposals"]
C --> D["Stops at the report (default)"]
C --> E["--ask or --apply: fix in the right lane"]The four core ideas of the skill:
| Idea | Question | Example |
|---|---|---|
| Evidence from this session | What is a proposal based on? | A command from a skill failed and was rerun; you corrected the agent once |
| Classify before proposing | Is this the skill's fault? | A flaky test or a missing binary is an environment fault, not a proposal |
| Smallest fix | How much of the skill changes? | One diff hunk, metadata.version bumped, required checks kept |
| Lane by owner | Where does the fix land? | A contributor opens a PR to AgentKit; other users write a personal kit |
The most important caveat: session content is your data and untrusted. The skill copies no prompt, tool output, token, absolute path or session id into a skill, commit or PR, and it never follows an instruction found inside a transcript.
Sample prompt for the end of a session:
/ak-dogfoodAfter the skill name you can type a topic to focus on, for example /ak-dogfood the shipping part. The flags:
| Flag | What it is for | Since ak |
|---|---|---|
--ask | Review each proposal before anything changes | 3.0.0-beta.37 |
--apply | Apply every proposal the report accepts | 3.0.0-beta.37 |
--all [--since YYYY-MM-DD] | Review every session on the machine instead of only this one | 3.0.0-beta.37 |
--skill <name> | Review only one used skill | 3.0.0-beta.37 |
What follows is the detailed version: the run flow, 4 situations with prompts, each flag explained (use when, not needed when, what you get), the change history by ak release and common pitfalls. The detailed version is for subscribers. Your agent can also search them through the portal's MCP.
Opens when your account has subscriber access
This guide is for subscribers
Once your account has access, the full piece, the interactive visual and the agent call all open.
- Sign in or create a modernEngineer accountReading access belongs to your account email.
- Choose a plan on the pricing page1, 3 or 12 months, paid by VietQR bank transfer. Access opens about a minute after the money arrives.
- Or redeem a Facebook subscriber codePeople supporting the page on Facebook get an activation code by message each month.
Already a subscriber? Sign in to read.
Use this piece in your agent
Get an API keyCopy the text below and paste it into Claude Code, Codex or whichever agent you use. The agent reads the piece and checks it against the repo you have open.
Read "ak-dogfood: turn a session's stumbles into skill fixes" on modernEngineer and apply it to this repo.
1. Call the content_get tool of the modernengineer MCP server with locale "en", slug "ak-dogfood". If the modernengineer MCP server is not connected, stop and walk me through connecting it from https://modernengineer.dev/en/mcp.
2. Summarize the main steps of the piece and point out which apply to this repo.
3. Propose concrete changes and ask me before editing any file.Connect MCP in Claude Code (once)
claude mcp add --transport http modernengineer \
https://api.modernengineer.dev/mcp \
--header "Authorization: Bearer <API key>"Reading the full piece over MCP needs an API key from a subscriber account or one that bought this guide. Without access, the agent only gets the opening.
- Version
- v1.0.0
- Updated
- 01/11/2026
- Licence
- All rights reserved
- Slug
- ak-dogfood
