Agent skill

Debugging Runtime Errors

by friday-platform in friday-platform/friday-studio

Loads when a session ends with status: failed AND a structured error message.

Custom licenceAuto-check passedDevelopment

Install Debugging Runtime Errors

skills CLI
$ npx skills add friday-platform/friday-studio --skill debugging-runtime-errors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install friday-platform/friday-studio debugging-runtime-errors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-runtime-errors .claude/skills/debugging-runtime-errors && rm -rf skills-src

Use ~/.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/

Facts

Skill name
debugging-runtime-errors
GitHub stars
104
Token cost
~1k tokens
SKILL.md length
449 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
Custom licence

At a glance

Loads when a session ends with status: failed AND a structured error message.

  • Tasks that involve Debugging
  • SKILL.md covers Error → fix table, What NOT to do and Cross-references
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Debugging Runtime Errors is an agent skill from friday-platform/friday-studio. 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.

Its SKILL.md is about 1k 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. It works with Zod. 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

  • “Use the debugging-runtime-errors skill to load when a session ends with status: failed AND a structured error message”
  • “/debugging-runtime-errors”

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 Runtime Errors loads about 1k tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 449 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~136
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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 449 words (~1,040 tokens).

“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.”

— opening of SKILL.md by friday-platform, Custom licence
name
debugging-runtime-errors

Read the full SKILL.md on GitHub

Files

Just SKILL.md in packages/system/skills/debugging-runtime-errors of friday-platform/friday-studio.

Open the folder on GitHubat commit fb3069a

Compare with similar skills

Debugging Runtime Errors 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.

Debugging Runtime Errors compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debugging Runtime Errors this skillfriday-platform/friday-studio104—~1kAutomated safety check: PassCustom licence
Skill Managerseasonedcc/remix-forms514—~6.1kAutomated safety check: PassMIT
MCP DeveloperJeffallan/claude-skills12k—~1.5kAutomated safety check: PassMIT
Trellis Session Insightmindfold-ai/Trellis15k4 repos~1.7kAutomated safety check: PassAGPL-3.0
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Aoti Debugpytorch/pytorch104k1 repos~1.7kAutomated safety check: PassCustom licence

Similar skills

  • Skill Manager

    seasonedcc/remix-forms

    Create, manage, and debug Claude Code Agent Skills. An agent skill from seasonedcc/remix-forms.

    514 GitHub stars~6.1k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed
  • MCP Developer

    Jeffallan/claude-skills

    Builds and debugs MCP servers and clients in TypeScript or Python, from tool and resource definitions to transport setup and inspector-based protocol checks.

    12k GitHub stars~1.5k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed
  • Trellis Session Insight

    mindfold-ai/Trellis

    Reach into past AI conversation history through the trellis mem CLI.

    15k GitHub starsUsed in 4 repos~1.7k tokens
    DevelopmentAuto-check passed
  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes
  • Aoti Debug

    pytorch/pytorch

    Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.

    104k GitHub starsUsed in 1 repo~1.7k tokens
    DevelopmentAuto-check passed
  • 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.

    43k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

More from friday-platform/friday-studio

All 20 skills in this repo
  • Authoring Skills

    friday-platform/friday-studio

    Authors new agent skills that follow the Anthropic + agentskills.io specification.

    104 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • 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.

    104 GitHub stars~4.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Workspace API

    friday-platform/friday-studio

    Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.

    104 GitHub stars~9.3k tokensUpdated 1 mo ago
    Auto-check: notes
  • Writing Workspace Signals

    friday-platform/friday-studio

    Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.

    104 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Composing Emails

    friday-platform/friday-studio

    General styling and tone guidelines for composing HTML emails.

    104 GitHub stars~648 tokensUpdated 1 mo ago
    Auto-check passed
  • Repairing Workspaces Agents

    friday-platform/friday-studio

    Repairs and upgrades existing Friday workspaces, jobs, user agents, and generated agents to current runtime contracts.

    104 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Debugging Runtime Errors

What does Debugging Runtime Errors do?

Loads when a session ends with status: failed AND a structured error message. Debugging Runtime Errors is an agent skill from friday-platform/friday-studio. Loads when a session ends with status: failed AND a structured error message.

When should I use Debugging Runtime Errors?

Debugging Runtime Errors fits situations like: tasks that involve Debugging.

How do I install Debugging Runtime Errors in Claude Code?

Run `npx skills add friday-platform/friday-studio --skill debugging-runtime-errors -a claude-code`. Or copy the skill folder (packages/system/skills/debugging-runtime-errors in friday-platform/friday-studio) into .claude/skills/debugging-runtime-errors in your project. Claude Code loads it when a task matches its description.

How do I install Debugging Runtime Errors in Codex?

Run `npx skills add friday-platform/friday-studio --skill debugging-runtime-errors -a codex`. Or copy the skill folder (packages/system/skills/debugging-runtime-errors in friday-platform/friday-studio) into .agents/skills/debugging-runtime-errors in your project. Codex loads it when a task matches its description.

Can I use Debugging Runtime Errors 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-runtime-errors -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-runtime-errors, .gemini/skills/debugging-runtime-errors, .github/skills/debugging-runtime-errors and .opencode/skills/debugging-runtime-errors in your project.

What does Debugging Runtime Errors need to run?

SKILL.md names no scripts, command-line tools or credentials: Debugging Runtime Errors is instructions for the agent only.

Does Debugging Runtime Errors 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 Runtime Errors 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 Runtime Errors use?

Debugging Runtime Errors 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 Runtime Errors use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Runtime Errors?

Skills that share tags, products or a category with Debugging Runtime Errors: Skill Manager (seasonedcc/remix-forms, 514 stars), MCP Developer (Jeffallan/claude-skills, 12k stars), Trellis Session Insight (mindfold-ai/Trellis, 15k stars) and Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debugging Runtime Errors?

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.