Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Triage entry-point for any "the job ran but something's wrong" situation in a Friday workspace.
Install Debugging Broken Jobs
$ npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install friday-platform/friday-studio debugging-broken-jobs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system/skills/debugging-broken-jobs .claude/skills/debugging-broken-jobs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugging-broken-jobs" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-broken-jobs into .claude/skills/debugging-broken-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-broken-jobs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-broken-jobsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install friday-platform/friday-studio debugging-broken-jobs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system/skills/debugging-broken-jobs .agents/skills/debugging-broken-jobs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-broken-jobs" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-broken-jobs into .agents/skills/debugging-broken-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-broken-jobs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install friday-platform/friday-studio debugging-broken-jobs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system/skills/debugging-broken-jobs .cursor/skills/debugging-broken-jobs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugging-broken-jobs" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-broken-jobs into .cursor/skills/debugging-broken-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-broken-jobs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/friday-platform/friday-studio.git --path packages/system/skills/debugging-broken-jobs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install friday-platform/friday-studio debugging-broken-jobs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system/skills/debugging-broken-jobs .gemini/skills/debugging-broken-jobs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugging-broken-jobs" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-broken-jobs into .gemini/skills/debugging-broken-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-broken-jobs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install friday-platform/friday-studio debugging-broken-jobsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system/skills/debugging-broken-jobs .github/skills/debugging-broken-jobs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugging-broken-jobs" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-broken-jobs into .github/skills/debugging-broken-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-broken-jobs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install friday-platform/friday-studio debugging-broken-jobs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system/skills/debugging-broken-jobs .opencode/skills/debugging-broken-jobs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugging-broken-jobs" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-broken-jobs into .opencode/skills/debugging-broken-jobs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-broken-jobs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debugging-broken-jobs- GitHub stars
- 104
- Token cost
- ~1.2k tokens
- SKILL.md length
- 485 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Triage entry-point for any "the job ran but something's wrong" situation in a Friday workspace.
- Works in 3 steps: Called describe_session(sessionId) on… → Read agentBlocks[].toolCalls to see what… → Verified the contracted exit (complete…
- Tasks that involve Debugging
- SKILL.md covers Diagnostic discipline…, Symptom triage table, What "diagnostic discipline"… and Cross-references
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Debugging Broken Jobs is an agent skill from friday-platform/friday-studio. 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.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The repository describes itself as: Agent Harness Platform — shareable workspaces, MCP tools, skills, memory, and cron/webhook automations. Self-hosted and transparent.
When your agent uses it
- Tasks that involve Debugging
Example prompts
- “the job ran but something”
- “platform bug”
- “FSM wiring is broken”
- “/debugging-broken-jobs”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Called describe_session(sessionId) on the failing session.
- Read agentBlocks[].toolCalls to see what tools the agent
- Verified the contracted exit (complete for outputTo actions,
What it can do on your machine
Read from SKILL.md and the folder at commit fb3069a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugging Broken Jobs loads about 1.2k tokens when it runs. Until then it costs about 116 tokens; SKILL.md has 485 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 485 words (~1,244 tokens).
“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…”
- name
- debugging-broken-jobs
Files
Just SKILL.md in packages/system/skills/debugging-broken-jobs of friday-platform/friday-studio.
Open the folder on GitHubat commit fb3069a
Compare with similar skills
Debugging Broken Jobs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugging Broken Jobs this skillfriday-platform/friday-studio | 104 | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Debugging Executionsn8n-io/n8n | 207k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
More from friday-platform/friday-studio
All 20 skills in this repoAuthoring Skills
friday-platform/friday-studio
Authors new agent skills that follow the Anthropic + agentskills.io specification.
Friday CLI
friday-platform/friday-studio
Interacts with a running Friday daemon via CLI and HTTP — lists/creates/modifies workspaces, triggers signals, watches sessions, publishes skills and agents.
Workspace API
friday-platform/friday-studio
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.
Writing Workspace Signals
friday-platform/friday-studio
Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.
Composing Emails
friday-platform/friday-studio
General styling and tone guidelines for composing HTML emails.
Repairing Workspaces Agents
friday-platform/friday-studio
Repairs and upgrades existing Friday workspaces, jobs, user agents, and generated agents to current runtime contracts.
Related
Categories
Questions about Debugging Broken Jobs
What does Debugging Broken Jobs do?
Triage entry-point for any "the job ran but something's wrong" situation in a Friday workspace. Debugging Broken Jobs is an agent skill from friday-platform/friday-studio. Triage entry-point for any "the job ran but something's wrong" situation in a Friday workspace.
When should I use Debugging Broken Jobs?
Debugging Broken Jobs fits situations like: tasks that involve Debugging.
How do I install Debugging Broken Jobs in Claude Code?
Run `npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a claude-code`. Or copy the skill folder (packages/system/skills/debugging-broken-jobs in friday-platform/friday-studio) into .claude/skills/debugging-broken-jobs in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Broken Jobs in Codex?
Run `npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a codex`. Or copy the skill folder (packages/system/skills/debugging-broken-jobs in friday-platform/friday-studio) into .agents/skills/debugging-broken-jobs in your project. Codex loads it when a task matches its description.
Can I use Debugging Broken Jobs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add friday-platform/friday-studio --skill debugging-broken-jobs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-broken-jobs, .gemini/skills/debugging-broken-jobs, .github/skills/debugging-broken-jobs and .opencode/skills/debugging-broken-jobs in your project.
What does Debugging Broken Jobs need to run?
SKILL.md names no scripts, command-line tools or credentials: Debugging Broken Jobs is instructions for the agent only.
Does Debugging Broken Jobs access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debugging Broken Jobs safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debugging Broken Jobs use?
Debugging Broken Jobs has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Debugging Broken Jobs use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debugging Broken Jobs?
Skills that share tags, products or a category with Debugging Broken Jobs: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugging Broken Jobs?
friday-platform (a GitHub organization) maintains it in friday-platform/friday-studio, which has 104 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 5, 2026.
Source: friday-platform/friday-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.