Agent skill

Debug

by suboss87 in suboss87/FDEOps

Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced.

MITAuto-check passed

Install Debug

skills CLI
$ npx skills add suboss87/FDEOps --skill debug -a claude-code

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

GitHub CLI
$ gh skill install suboss87/FDEOps debug --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/suboss87/FDEOps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/debug .claude/skills/debug && 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
debug
GitHub stars
954
Token cost
~349 tokens
SKILL.md length
142 words
Files
12 (incl. references)
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced.

  • Works in 2 steps: Read the task context contract. → Read the method.
  • Diagnosis and repair
  • SKILL.md covers Purpose and Principles
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Debug is an agent skill from suboss87/FDEOps. Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.

Its SKILL.md is about 350 tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files (for example `.fde-generated.json`, `agents/openai.yaml` and `references/build.md`).

The repository describes itself as: Forward deployed engineering skills for AI coding agents. The licence is MIT.

When your agent uses it

  • Diagnosis and repair
  • Follow incident authority for live mitigation

Example prompts

  • “/debug”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Read the task context contract.
  2. Read the method.

What it can do on your machine

Read from SKILL.md and the folder at commit 64d1d8a. 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

Debug loads about 349 tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 142 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~349
With references · SKILL.md plus every file in references/, read only if the agent opens them
~13k

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

The full file from suboss87/FDEOps at commit 64d1d8a, republished under its MIT licence (© suboss87). 142 words, ~349 tokens.

Download SKILL.mdSave it as .claude/skills/debug/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
debug
description
Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.

debug

<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->

Purpose

A diagnosed failure, repair and regression evidence.

Before investigating or acting:

  1. Read the task context contract.
  2. Read the method.

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

Principles

  • Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
  • If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
  • The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
  • Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.

© suboss87, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (references) in skills/debug of suboss87/FDEOps.

  • SKILL.md
  • .fde-generated.json
  • agents/openai.yaml
  • references/build.md
  • references/debug.md
  • references/eval-pack.md
  • references/integrate.md
  • references/qa.md
  • references/review.md
  • references/ship.md
  • references/task-context.md
  • references/verification.md

Open the folder on GitHubat commit 64d1d8a

Compare with similar skills

Debug 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.

Debug compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Debug this skillsuboss87/FDEOps954—~349Automated safety check: PassMIT
Debugging CI FailuresPostHog/posthog40k—~5.7kAutomated safety check: PassCustom licence
Investigating CI FailuresPostHog/posthog40k—~2.9kAutomated safety check: PassCustom licence
RustPython Test Failure InvestigationRustPython/RustPython22k—~467Automated safety check: PassMIT
Debugasgeirtj/system_prompts_leaks69k—~439Automated safety check: PassCC0-1.0
Root Cause Investigationgarrytan/gstack136k—~12kAutomated safety check: NotesMIT

Similar skills

  • Debugging CI Failures

    PostHog/posthog

    Official

    Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?").

    40k GitHub stars~5.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Official

    Investigates a specific CI failure to a verdict: whose fault, which commit, who wrote it, and whether it's fixed.

    40k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed
  • Investigates a failing RustPython test by comparing it with CPython, then either fixes it or gathers the details for an incompatibility report.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed
  • Debug

    asgeirtj/system_prompts_leaks

    Enable debug logging for this session and help diagnose issues

    69k GitHub stars~439 tokensUpdated yesterday
    Auto-check passed
  • Debugs in four phases (investigate, analyze, hypothesize, implement) under one rule: no fix is made until the root cause is found.

    136k GitHub stars~12k tokensUpdated today
    DevelopmentAuto-check: notes
  • Runtime Debug

    vercel/next.js

    Official

    Debug and verification workflow for runtime-bundle and module-resolution regressions.

    143k GitHub starsUsed in 1 repo~618 tokens
    DevelopmentAuto-check passed

More from suboss87/FDEOps

All 34 skills in this repo
  • Fde

    suboss87/FDEOps

    Keeps the engagement record for client work. An agent skill from suboss87/FDEOps.

    954 GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Audit

    suboss87/FDEOps

    Audit an inherited engagement or implementation against its evidence.

    954 GitHub stars~341 tokensUpdated today
    Auto-check passed
  • Board Memo

    suboss87/FDEOps

    Draft a board or executive summary of an engagement using outcomes, risks and investment decisions.

    954 GitHub stars~343 tokensUpdated today
    Auto-check passed
  • Brief

    suboss87/FDEOps

    Clarify a new customer brief, desired outcome, constraints and evidence gaps.

    954 GitHub stars~339 tokensUpdated today
    Auto-check passed
  • Business Case

    suboss87/FDEOps

    Develop a business case for an initiative using costs, benefits, risks and evidence.

    954 GitHub stars~343 tokensUpdated today
    Auto-check passed
  • Connect

    suboss87/FDEOps

    Configure or diagnose access to a requested source using available host tools.

    954 GitHub stars~354 tokensUpdated today
    Auto-check passed

Questions about Debug

What does Debug do?

Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Debug is an agent skill from suboss87/FDEOps. Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced.

When should I use Debug?

Debug fits situations like: diagnosis and repair; follow incident authority for live mitigation.

How do I install Debug in Claude Code?

Run `npx skills add suboss87/FDEOps --skill debug -a claude-code`. Or copy the skill folder (skills/debug in suboss87/FDEOps) into .claude/skills/debug in your project. Claude Code loads it when a task matches its description.

How do I install Debug in Codex?

Run `npx skills add suboss87/FDEOps --skill debug -a codex`. Or copy the skill folder (skills/debug in suboss87/FDEOps) into .agents/skills/debug in your project. Codex loads it when a task matches its description.

Can I use Debug 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 suboss87/FDEOps --skill debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug, .gemini/skills/debug, .github/skills/debug and .opencode/skills/debug in your project.

What does Debug need to run?

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

Does Debug 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 Debug 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 Debug use?

Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Debug use?

About 349 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to Debug?

Skills that share tags, products or a category with Debug: Debugging CI Failures (PostHog/posthog, 40k stars), Investigating CI Failures (PostHog/posthog, 40k stars), RustPython Test Failure Investigation (RustPython/RustPython, 22k stars) and Debug (asgeirtj/system_prompts_leaks, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Debug?

suboss87 (a GitHub user) maintains it in suboss87/FDEOps, which has 954 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 8, 2026.

Source: suboss87/FDEOps on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.