Agent skill · Code Review & Quality

debugging-broken-jobs

Triage entry-point for any "the job ran but something's wrong" situation in a Friday workspace. Loads when a job tool returns `output-error`, `success: false`, `summary: ""`, `artifactIds: []`, or any session with `status: failed`. Routes to the right sibling debug skill. Required reading before declaring "platform bug" / "FSM wiring is broken" / "this is a known issue" — those claims are FORBIDDEN without first walking this triage table.

Friday Platform98★ · 1 repos on radarProfile →
claude-codeNOASSERTION
Install
npx skills add friday-platform/friday-studio --skill debugging-broken-jobs --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: packages/system/skills/debugging-broken-jobs/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 98
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Debugging broken jobs Stop. Before you form a hypothesis, walk this triage. The job tool's return shape and the session's `agentBlocks[].toolCalls` carry the diagnosis 95% of the time. The remaining 5% is rarely a platform bug and almost always a contract violation by the agent or the FSM. ## Diagnostic discipline (non-negotiable) You may NOT claim "platform bug" / "FSM wiring is broken" / "this

More from friday-studio
All skills →
workspace-apiCreate, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYD_URL. Use…Testing & QAauthoring-skillsAuthors new agent skills that follow the Anthropic + agentskills.io specification. Use when the…Code Review & Qualitycomposing-contextInternal pattern guide for composing turn-local retrieval-gated context into a synthetic…AI & Agentsdebugging-empty-outputLoads when a workspace job tool returns `success: true, status: completed` AND (`summary: ""` OR…Workflow & Productivitydebugging-job-invocationLoads when a workspace job tool (called from chat) returns `output-error` with no meaningful error…AI & Agentscomposing-emailsGeneral styling and tone guidelines for composing HTML emails. Use when writing email copy that…Data & Analytics
About this skill
What does the debugging-broken-jobs skill do?

Triage entry-point for any "the job ran but something's wrong" situation in a Friday workspace. Loads when a job tool returns `output-error`, `success: false`, `summary: ""`, `artifactIds: []`, or any session with `status: failed`. Routes to the right sibling debug skill. Required reading before declaring "platform bug" / "FSM wiring is broken" / "this is a known issue" — those claims are FORBIDDEN without first walking this triage table.

How do I install it?

Run `npx skills add friday-platform/friday-studio --skill debugging-broken-jobs --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.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.