New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Squid Triage Issue

by iusztinpaul in iusztinpaul/squid

Bug intake — localise the suspected code, capture a deterministic reproducer, and emit a groomed bug task with a regression-test acceptance criterion, ready for /squid-implement-task or the full…

Apache-2.0Auto-check passedTesting & QA

Install Squid Triage Issue

skills CLI
$ npx skills add iusztinpaul/squid --skill squid-triage-issue -a claude-code

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

GitHub CLI
$ gh skill install iusztinpaul/squid squid-triage-issue --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/iusztinpaul/squid.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/squid-triage-issue .claude/skills/squid-triage-issue && 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
squid-triage-issue
GitHub stars
203
Token cost
~2k tokens
SKILL.md length
645 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
Apache-2.0

At a glance

Bug intake — localise the suspected code, capture a deterministic reproducer, and emit a groomed bug task with a regression-test acceptance criterion, ready for /squid-implement-task or the full…

  • Works in 6 steps: Resolve the report → Localise → Build the reproducer → …
  • Tasks that involve Issue triage
  • SKILL.md covers When NOT to use, Step 1 — Resolve the report, Step 2 — Localise and Step 3 — Build the reproducer, plus 3 more sections
  • Calls gh

What it does

Squid Triage Issue is an agent skill from iusztinpaul/squid. Bug intake — localise the suspected code, capture a deterministic reproducer, and emit a groomed bug task with a regression-test acceptance criterion, ready for /squid-implement-task or the full pipeline.

Its SKILL.md is about 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 Testing & QA, covering Issue triage. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Issue triage

Example prompts

  • “/squid-triage-issue”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Resolve the report
  2. Localise
  3. Build the reproducer
  4. Write the groomed bug task
  5. File the task
  6. Hand-off recommendation

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Squid Triage Issue loads about 2k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 645 words of instructions outside code blocks.

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

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 iusztinpaul/squid at commit f5bf6b3, republished under its Apache-2.0 licence (© iusztinpaul). 645 words, ~2,023 tokens.

Download SKILL.mdSave it as .claude/skills/squid-triage-issue/SKILL.md (or your agent's skills folder).
name
squid-triage-issue
description
Bug intake — localise the suspected code, capture a deterministic reproducer, and emit a groomed bug task with a regression-test acceptance criterion, ready for /squid-implement-task or the full pipeline.
disable-model-invocation
true
argument-hint
<bug-description | path/to/report.md |

Triage — turn a bug report into a groomed, fixable task

/squid-implement-task and /squid-implement-night both assume the spec is already shaped right. Bug reports rarely are: they read "X is broken" and need a reproducer, expected-vs-actual, code localisation, and a regression-test acceptance criterion before SWE / Tester can do anything useful with them. This skill produces that groomed bug task, then hands off.

You are the triage orchestrator — you may delegate exploration to sub-agents (Explore, general-purpose), but you do NOT write production code, do NOT write the regression test, and do NOT start the fix. Your output is the spec.

$ARGUMENTS is one of:

  • A free-form bug description (paste-in customer report, stack trace, "X is broken when Y").
  • A path to a markdown report (docs/bugs/foo.md).
  • A tracker reference (NNN-slug in file mode, #N in gh mode).

If empty, ask the user for one before proceeding.

Read AGENTS.md first to confirm the active tracker mode (file or gh).

When NOT to use

  • A feature request — use /squid-plan (PA grooming) directly.
  • A refactor with no observable user impact — use /squid-refactor.
  • A trivial typo or one-line bug you can fix right now in chat — just fix it.
  • An incident still in progress — stabilise first, triage after.

Step 1 — Resolve the report

Identify what to triage from $ARGUMENTS:

  1. File path → cat the report.
  2. Tracker reference (NNN-slug file mode, #N gh mode) → load the existing record (tasks/NNN-*.md or gh issue view N --json number,title,body,labels).
  3. Free-form text → use as-is.
  4. Empty → ask: "What bug should I triage? (Paste the report, give me a path, or a tracker reference.)"

Echo the resolved report back to the user in one paragraph as confirmation. Don't block — proceed.

Step 2 — Localise

Spawn ONE Explore agent (or general-purpose if the report is vague enough that exploration needs interview-style breadth). Prompt sketch (adapt as needed):

Agent(
  subagent_type="Explore",
  prompt="""Bug report: {one-paragraph summary}.

  Find: (1) the module(s) most likely responsible — rank top-3 with file:line and a one-sentence reason; (2) existing tests covering this behaviour, by file:line; (3) recent commits touching the implicated files (`git log --since='4 weeks ago' -- <file>`) — recent changes correlate with regressions; (4) related closed PRs / issues (`gh search issues "<keyword>" --state closed`).

  Be specific. Report back as four bulleted lists. Do NOT propose fixes."""
)

Read the top-3 candidate file(s) yourself (cheap) before moving on — you want firsthand familiarity, not just the agent's summary. If localisation surfaces other bugs, file each as its own triage task — one bug per task.

Show full SKILL.md (306 more words)Show less

Step 3 — Build the reproducer

A reproducer is the load-bearing artefact. Without one, the Tester can't verify a fix and the SWE is guessing.

Try, in this order:

  1. Re-derive from the report — if the user already pasted exact steps, formalise them as a numbered list with concrete inputs.
  2. Ask the user — if the report is vague ("the page is slow sometimes"), use AskUserQuestion. Two questions max:
    • What exact input / state triggers it?
    • What's the smallest path to observing it (URL, command, test invocation)?
  3. Synthesise from code — if the user can't repro and the code makes the failure mode obvious, draft the reproducer as a failing test case (described in prose; you don't write it).

The reproducer must be deterministic. If it's only intermittent, mark it explicitly as flaky-repro and capture the conditions correlating with reproduction (load, state, time-of-day) — the AC then becomes "instrument so we can capture it next time," not "fix the bug." Be explicit about the difference.

Step 4 — Write the groomed bug task

Use this exact template. Frontmatter follows squid-scaffold/specs/tracker-workflow.md, so /squid-implement-task and /squid-implement-night accept it without re-grooming.

markdown
# Bug: {one-line title — observable user-visible symptom}

**Severity:** {S1 outage / S2 broken feature / S3 degraded / S4 cosmetic}
**Affected component(s):** {file paths or module names}
**First observed:** {date or commit ref, if knowable}

## Summary

One paragraph. What the user sees. Don't speculate on the cause here.

## Reproducer (deterministic)

1. {exact command / URL / inputs}
2. {next step}
3. ...

Expected: {what should happen}
Actual: {what does happen — include exact error message, status code, or output}

> If the bug is non-deterministic, replace this section with a `Flaky-repro` block listing the correlating conditions.

## Suspected localisation

- `path/to/file.py:42` — {one-sentence reason}
- `path/to/other.py:117` — {one-sentence reason}

> Hypotheses, not conclusions. The SWE will confirm or refute during fix.

## Out of scope

- {Things that look related but aren't part of this bug — explicit so the SWE doesn't expand scope.}

## Acceptance criteria

- [ ] **Regression test** added at `tests/.../test_<slug>.py` that fails on `main` and passes on the fix branch. Test name describes the symptom, not the implementation.
- [ ] Reproducer steps from above produce the expected behaviour after the fix.
- [ ] No unrelated behaviour changes (full unit + integration suite green).
- [ ] If `Severity ≤ S2`, a one-line note added to the project changelog / release notes.

## Notes for the SWE

- {Optional: hints from your localisation — e.g. "the bug appears only when feature flag X is on; check the branching in module Y".}
- {Optional: explicitly forbidden fix shapes — e.g. "do not add a try/except that swallows the underlying exception; surface it properly".}

Severity heuristic (don't over-think — the user can correct):

  • S1 — production outage / data loss / security exposure.
  • S2 — a documented feature is broken; users hit it on the golden path.
  • S3 — a documented feature is degraded; workarounds exist.
  • S4 — cosmetic / docs / typo.

Step 5 — File the task

Where it lands depends on tracker mode (read from AGENTS.md).

File mode

Allocate NNN per squid-scaffold/specs/tracker-workflow.md. Write to:

tasks/NNN-bug-<slug>.md

Open the file with YAML frontmatter (status: pending, feature: bug-<slug>), then the groomed body from Step 4.

gh mode
gh issue create \
  --title "Bug: {one-line title}" \
  --label "bug,triaged" \
  --body "$(cat <<'EOF'
{the entire groomed-bug body, minus the # H1}
EOF
)"

Capture the issue number for Step 6.

Step 6 — Hand-off recommendation

Surface a single decision block to the user:

markdown
## Triage complete — {bug title}

**Filed:** {tracker path or issue URL}
**Severity:** {S1–S4}
**Suspected files:** {top 1–3}

### Recommended next step

{Pick ONE based on severity + scope:}

- **Severity S1 / S2, narrow scope (≤2 files), reproducer is deterministic** → `/squid-implement-task {ref}` — supervise the fix in real time. Fastest path; you watch the diff.
- **Severity S3 / S4, OR scope spans multiple files / tasks, OR a regression test will need its own design conversation** → `/squid-plan {ref}` then `/squid-implement-night` — full pipeline. The PA decomposes into tasks; you only gate the plan and the merge.
- **Severity S1 production-down** → fix live yourself; this groomed task becomes the postmortem record, not the entry point.

### Open questions for the human

- {if any — list them. Otherwise omit this section.}

Hand control back. Do NOT auto-invoke /squid-implement-task or /squid-implement-night — the user approves the groomed task first; this skill stops at filing.

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

Files

Just SKILL.md in skills/squid-triage-issue of iusztinpaul/squid.

Open the folder on GitHubat commit f5bf6b3

Compare with similar skills

Squid Triage Issue 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.

Squid Triage Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Squid Triage Issue this skilliusztinpaul/squid203—~2kAutomated safety check: PassApache-2.0
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0
Issue Triagepnp/powershell906—~1.8kAutomated safety check: PassMIT
Triage Issuedruxt/druxt.js114—~767Automated safety check: PassMIT
Development Workflowruby-git/ruby-git1.8k—~6.1kAutomated safety check: PassMIT
Maggyalinaqi/maggy707—~1.5kAutomated safety check: PassMIT

Similar skills

  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated today
    Testing & QAAuto-check passed

  • Issue Triage

    pnp/powershell

    Take a PnP PowerShell GitHub issue, find the cmdlet that owns it, trace the code path, and decide whether the cause is in this repo or in PnP Framework, PnP Core SDK or the service.

    906 GitHub stars~1.8k tokensUpdated today
    Testing & QAAuto-check passed

  • Triage Issue

    druxt/druxt.js

    Sorts a druxt.js issue by type and package, and reproduces it against the example Drupal backend or with a failing unit test before writing up the findings.

    114 GitHub stars~767 tokensUpdated today
    Testing & QAAuto-check passed

  • Development Workflow

    ruby-git/ruby-git

    Follows a strict Test-Driven Development (TDD) workflow with four phases: triage, prepare, execute, and finalize.

    1.8k GitHub stars~6.1k tokensUpdated 8 days ago
    Testing & QAAuto-check passed

  • Maggy

    alinaqi/maggy

    Maggy is a local AI engineering command center. An agent skill from alinaqi/maggy.

    707 GitHub stars~1.5k tokensUpdated 16 days ago
    Testing & QAAuto-check passed

  • Bug Triage Prioritizer

    zanecole10/software-tailor-skills

    Triage bug reports by severity, recommend fix order, generate client communication templates, determine whether to charge for fixes, and provide Claude Code prompts to resolve issues quickly.

    106 GitHub stars~1.2k tokensUpdated 11 mo ago
    Testing & QAAuto-check passed

More from iusztinpaul/squid

All 13 skills in this repo

  • Squid Implement Night

    iusztinpaul/squid

    Run the full agent-team pipeline end-to-end for one feature whose Tasks Plan is already approved by /squid-plan, handing the human a validated, ready-to-squash-merge PR.

    203 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Squid Implement Task

    iusztinpaul/squid

    Implement one task — or a whole list / an approved Tasks Plan — via the inner SWE↔Tester loop, committing each task on PASS.

    203 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Squid Review

    iusztinpaul/squid

    Push the committed feature branch, create or update its PR, then run Product Architect acceptance and PR-Reviewer on it.

    203 GitHub stars~873 tokensUpdated 1 mo ago
    Auto-check passed

  • Squid Review CI

    iusztinpaul/squid

    Drive CI green on a pushed, review-clean feature PR — On-Call diagnoses failures and hands fix tasks to the SWE.

    203 GitHub stars~607 tokensUpdated 1 mo ago
    Auto-check passed

  • Squid Testing Python

    iusztinpaul/squid

    Write and evaluate effective Python tests using pytest. An agent skill from iusztinpaul/squid.

    203 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

  • Squid Architecture Review

    iusztinpaul/squid

    Periodic architectural sweep — reads existing ADRs, maps modules/dependencies/layering, and reports up to 10 prioritised findings shaped as refactor proposals /squid-refactor can consume directly.

    203 GitHub stars~2.6k tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Squid Triage Issue

What does Squid Triage Issue do?

Bug intake — localise the suspected code, capture a deterministic reproducer, and emit a groomed bug task with a regression-test acceptance criterion, ready for /squid-implement-task or the full…. Squid Triage Issue is an agent skill from iusztinpaul/squid. Bug intake — localise the suspected code, capture a deterministic reproducer, and emit a groomed bug task with a regression-test acceptance criterion, ready for /squid-implement-task or the full pipeline.

When should I use Squid Triage Issue?

Squid Triage Issue fits situations like: tasks that involve Issue triage.

How do I install Squid Triage Issue in Claude Code?

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

How do I install Squid Triage Issue in Codex?

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

Can I use Squid Triage Issue 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 iusztinpaul/squid --skill squid-triage-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/squid-triage-issue, .gemini/skills/squid-triage-issue, .github/skills/squid-triage-issue and .opencode/skills/squid-triage-issue in your project.

What does Squid Triage Issue need to run?

Going by SKILL.md and its folder, Squid Triage Issue needs the command-line tools its instructions call (gh).

Does Squid Triage Issue access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Squid Triage Issue 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 Squid Triage Issue use?

Squid Triage Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Squid Triage Issue use?

About 2k tokens (SKILL.md is roughly 8.1k 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 Squid Triage Issue?

Skills that share tags, products or a category with Squid Triage Issue: Triage Issues (ClickHouse/clickhouse-java, 1.6k stars), Issue Triage (pnp/powershell, 906 stars), Triage Issue (druxt/druxt.js, 114 stars) and Development Workflow (ruby-git/ruby-git, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Squid Triage Issue?

iusztinpaul (a GitHub user) maintains it in iusztinpaul/squid, which has 203 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on September 3, 2026.

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