debugging-runtime-errors
Loads when a session ends with `status: failed` AND a structured error message. Recognize: `did not call complete` (agent never called the injected complete tool); `emitted empty output` (called complete with `{}`); `emitted an empty response` (called complete with empty string); `LLM step failed:` (agent called failStep); `output does not match schema` (outputType validation failed); `Invalid job config` / `Invalid signal config` (Zod schema rejection on upsert). Each pattern has a one-line fix in the table below.
Profile →npx skills add friday-platform/friday-studio --skill debugging-runtime-errors --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Debugging runtime errors When a session emits `status: failed` with a specific error message, the message itself names the contract violation. This skill maps each error pattern to its fix. ## Error → fix table ### `LLM action with outputTo '<doc>' did not call complete` The action set `outputTo` so the runtime injected a `complete` tool. The LLM finished without calling it. **Fix:** update the
What does the debugging-runtime-errors skill do?
Loads when a session ends with `status: failed` AND a structured error message. Recognize: `did not call complete` (agent never called the injected complete tool); `emitted empty output` (called complete with `{}`); `emitted an empty response` (called complete with empty string); `LLM step failed:` (agent called failStep); `output does not match schema` (outputType validation failed); `Invalid job config` / `Invalid signal config` (Zod schema rejection on upsert). Each pattern has a one-line fix in the table below.
How do I install it?
Run `npx skills add friday-platform/friday-studio --skill debugging-runtime-errors --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From friday-platform/friday-studio, a repository with 98 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.