GreptimeDB Fuzz CI Failure Investigation
GreptimeTeam/greptimedb
Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.
Classify failing Foundry fuzz, property, invariant, and differential tests.
MITAuto-check passed
Install Foundry Failure Triage
$ npx skills add aviggiano/security --skill foundry-failure-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aviggiano/security foundry-failure-triage --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/aviggiano/security.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/foundry-failure-triage .claude/skills/foundry-failure-triage && 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 "foundry-failure-triage" agent skill from https://github.com/aviggiano/security/tree/main/skills/foundry-failure-triage into .claude/skills/foundry-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foundry-failure-triage", 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/aviggiano/security/tree/main/skills/foundry-failure-triageType 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 aviggiano/security --skill foundry-failure-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aviggiano/security foundry-failure-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviggiano/security.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/foundry-failure-triage .agents/skills/foundry-failure-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "foundry-failure-triage" agent skill from https://github.com/aviggiano/security/tree/main/skills/foundry-failure-triage into .agents/skills/foundry-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foundry-failure-triage", 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 aviggiano/security --skill foundry-failure-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aviggiano/security foundry-failure-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviggiano/security.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/foundry-failure-triage .cursor/skills/foundry-failure-triage && 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 "foundry-failure-triage" agent skill from https://github.com/aviggiano/security/tree/main/skills/foundry-failure-triage into .cursor/skills/foundry-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foundry-failure-triage", 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/aviggiano/security.git --path skills/foundry-failure-triage--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 aviggiano/security --skill foundry-failure-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aviggiano/security foundry-failure-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviggiano/security.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/foundry-failure-triage .gemini/skills/foundry-failure-triage && 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 "foundry-failure-triage" agent skill from https://github.com/aviggiano/security/tree/main/skills/foundry-failure-triage into .gemini/skills/foundry-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foundry-failure-triage", 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 aviggiano/security foundry-failure-triageInstalls 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 aviggiano/security --skill foundry-failure-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aviggiano/security.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/foundry-failure-triage .github/skills/foundry-failure-triage && 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 "foundry-failure-triage" agent skill from https://github.com/aviggiano/security/tree/main/skills/foundry-failure-triage into .github/skills/foundry-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foundry-failure-triage", 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 aviggiano/security --skill foundry-failure-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aviggiano/security foundry-failure-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aviggiano/security.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/foundry-failure-triage .opencode/skills/foundry-failure-triage && 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 "foundry-failure-triage" agent skill from https://github.com/aviggiano/security/tree/main/skills/foundry-failure-triage into .opencode/skills/foundry-failure-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "foundry-failure-triage", 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
foundry-failure-triage- GitHub stars
- 144
- Token cost
- ~637 tokens
- SKILL.md length
- 305 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Classify failing Foundry fuzz, property, invariant, and differential tests.
- Works in 6 steps: Read AGENTS.md and any testing-plan docs. → Run the requested Foundry command and… → Reproduce each failing test with the… → …
- Codex needs to run forge tests
- SKILL.md covers Workflow, Categories, Strictness and Subagent Prompt Shape, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Foundry Failure Triage is an agent skill from aviggiano/security. Classify failing Foundry fuzz, property, invariant, and differential tests. Use when Codex needs to run forge tests, reproduce counterexamples, spawn fresh investigations, separate harness defects from reference bugs and production bugs, and report strict-equality failures without masking them.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
The repository describes itself as: Security Reviews and Audit Checklists. The licence is MIT.
When your agent uses it
- Codex needs to run forge tests
- Reproduce counterexamples
- Spawn fresh investigations
- Separate harness defects from reference bugs and production bugs
Example prompts
- “/foundry-failure-triage”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read AGENTS.md and any testing-plan docs.
- Run the requested Foundry command and capture the failing test list.
- Reproduce each failing test with the narrowest command and useful verbosity.
- For independent failures, use fresh context or subagents when available.
- Classify each failure before fixing anything.
- Report a table before making changes unless the user has already authorized specific fixes.
What it can do on your machine
Read from SKILL.md and the folder at commit e18ce7d. 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
Foundry Failure Triage loads about 637 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 305 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
The full file from aviggiano/security at commit e18ce7d, republished under its MIT licence (© aviggiano). 305 words, ~637 tokens.
Download SKILL.mdSave it as
.claude/skills/foundry-failure-triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- foundry-failure-triage
- description
- Classify failing Foundry fuzz, property, invariant, and differential tests. Use when Codex needs to run forge tests, reproduce counterexamples, spawn fresh investigations, separate harness defects from reference bugs and production bugs, and report strict-equality failures without masking them.
Foundry Failure Triage
Workflow
- Read
AGENTS.mdand any testing-plan docs. - Run the requested Foundry command and capture the failing test list.
- Reproduce each failing test with the narrowest command and useful verbosity.
- For independent failures, use fresh context or subagents when available.
- Classify each failure before fixing anything.
- Report a table before making changes unless the user has already authorized specific fixes.
Categories
harness defect: invalid setup, impossible bounds, asymmetric production/reference state, wrong ABI shape, stale interface, or test expectation not actually implied by public behavior.reference bug: the independent model is incomplete or diverges from the public spec/interface.production bug: production diverges from the public spec/interface or from a valid independent reference.spec mismatch: the test encodes a desired/spec behavior that production does not satisfy and should remain failing for developer attention.unknown: insufficient evidence; preserve the failing test.
Do not assume production is correct. Do not assume the reference is correct. Do not assume the test is correct.
Strictness
Treat one-unit and one-wei differences as real findings unless the spec defines tolerance. Never relax equality only because a failure is small.
Only fix tests when confidence is high that the test would otherwise create a false positive. If confidence is low or medium, keep the failing test and explain the ambiguity.
Subagent Prompt Shape
Give each fresh investigation:
- failing test name and file
- exact forge command or counterexample
- relevant public interface/spec paths or URLs
- classification categories
- instruction not to edit files unless asked
Ask for root cause, classification, confidence, and recommendation. Merge results into one table and resolve conflicts by doing a fresh local check.
Report Table
Use columns like:
| Failing test | Category | Root cause | Recommendation |
|---|
When the user needs developer-facing output, include exact file/test names, enough evidence to reproduce, and whether the test should remain failing.
© aviggiano, 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 1 other file in skills/foundry-failure-triage of aviggiano/security.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit e18ce7d
Compare with similar skills
Foundry Failure Triage 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 |
|---|---|---|---|---|---|---|
| Foundry Failure Triage this skillaviggiano/security | 144 | — | ~637 | Automated safety check: Pass | MIT | |
| GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb | 6.7k | — | ~4.4k | Automated safety check: Pass | Apache-2.0 | |
| Nemoclaw Maintainer Classify CI FailureNVIDIA/NemoClaw | 23k | — | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Fuzzmillionco/react-doctor | 15k | — | ~839 | Automated safety check: Pass | Custom licence | |
| cargo-fuzz Rust Fuzzingtrailofbits/skills | 7.5k | — | ~2.9k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| CSS At Propertythedaviddias/Front-End-Checklist | 74k | — | ~602 | Automated safety check: Pass | MIT |
Similar skills
- Official
Nemoclaw Maintainer Classify CI Failure
NVIDIA/NemoClaw
Classify one failed NemoClaw GitHub Actions job using bounded, redacted logs and optional retained artifacts.
Fuzz
millionco/react-doctor
Fuzz React Doctor rules for crashes, slowness, false positives, and mutation-sensitive diagnostics with @react-doctor/fuzz.
- Official
cargo-fuzz Rust Fuzzing
trailofbits/skills
Sets up cargo-fuzz for a Cargo-based Rust project: nightly toolchain, fuzz targets, structured inputs, sanitizers, coverage and reproducing crashes.
CSS At Property
thedaviddias/Front-End-Checklist
A skill your agent uses when implementing animated gradients, complex CSS transitions that involve custom property values, or building a typed design token system where custom property misuse should…
Pester Failure Analysis
PowerShell/PowerShell
Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.
More from aviggiano/security
All 10 skills in this repoFoundry Deploy Fixtures
aviggiano/security
Create or refactor Foundry deployment fixtures for Solidity tests.
Foundry Fuzz Mirrors
aviggiano/security
Create Foundry fuzz tests from deterministic unit tests. An agent skill from aviggiano/security.
Foundry Spec Properties
aviggiano/security
Turn whitepapers, protocol specs, and public documentation into Foundry property tests.
Foundry Test Campaign
aviggiano/security
Master skill for running an end-to-end multi-pass Foundry testing campaign for Solidity projects.
Stateful Invariant Testing
aviggiano/security
Build metric-driven Chimera/create-chimera-app stateful invariant testing campaigns for Solidity projects.
Foundry Differential Tests
aviggiano/security
Create Foundry differential tests comparing production Solidity contracts against an independent reference model.
Questions about Foundry Failure Triage
What does Foundry Failure Triage do?
Classify failing Foundry fuzz, property, invariant, and differential tests. Foundry Failure Triage is an agent skill from aviggiano/security. Classify failing Foundry fuzz, property, invariant, and differential tests.
When should I use Foundry Failure Triage?
Foundry Failure Triage fits situations like: Codex needs to run forge tests; reproduce counterexamples; spawn fresh investigations; separate harness defects from reference bugs and production bugs.
How do I install Foundry Failure Triage in Claude Code?
Run `npx skills add aviggiano/security --skill foundry-failure-triage -a claude-code`. Or copy the skill folder (skills/foundry-failure-triage in aviggiano/security) into .claude/skills/foundry-failure-triage in your project. Claude Code loads it when a task matches its description.
How do I install Foundry Failure Triage in Codex?
Run `npx skills add aviggiano/security --skill foundry-failure-triage -a codex`. Or copy the skill folder (skills/foundry-failure-triage in aviggiano/security) into .agents/skills/foundry-failure-triage in your project. Codex loads it when a task matches its description.
Can I use Foundry Failure Triage 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 aviggiano/security --skill foundry-failure-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/foundry-failure-triage, .gemini/skills/foundry-failure-triage, .github/skills/foundry-failure-triage and .opencode/skills/foundry-failure-triage in your project.
What does Foundry Failure Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Foundry Failure Triage is instructions for the agent only.
Does Foundry Failure Triage 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 Foundry Failure Triage 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 Foundry Failure Triage use?
Foundry Failure Triage 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 Foundry Failure Triage use?
About 637 tokens (SKILL.md is roughly 2.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 Foundry Failure Triage?
Skills that share tags, products or a category with Foundry Failure Triage: GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars), Nemoclaw Maintainer Classify CI Failure (NVIDIA/NemoClaw, 23k stars), Fuzz (millionco/react-doctor, 15k stars) and cargo-fuzz Rust Fuzzing (trailofbits/skills, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Foundry Failure Triage?
aviggiano (a GitHub user) maintains it in aviggiano/security, which has 144 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 15, 2026.
Source: aviggiano/security on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.