Dogfood Exploratory QA
vercel-labs/agent-browser
Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.
Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue.
Install Filing Bug Reports
$ npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install matlab/simulink-agentic-toolkit filing-bug-reports --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/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills-catalog/model-based-design-core/filing-bug-reports .claude/skills/filing-bug-reports && 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 "filing-bug-reports" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/filing-bug-reports into .claude/skills/filing-bug-reports/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filing-bug-reports", 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/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/filing-bug-reportsType 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 matlab/simulink-agentic-toolkit --skill filing-bug-reports -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install matlab/simulink-agentic-toolkit filing-bug-reports --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills-catalog/model-based-design-core/filing-bug-reports .agents/skills/filing-bug-reports && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "filing-bug-reports" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/filing-bug-reports into .agents/skills/filing-bug-reports/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filing-bug-reports", 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 matlab/simulink-agentic-toolkit --skill filing-bug-reports -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install matlab/simulink-agentic-toolkit filing-bug-reports --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills-catalog/model-based-design-core/filing-bug-reports .cursor/skills/filing-bug-reports && 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 "filing-bug-reports" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/filing-bug-reports into .cursor/skills/filing-bug-reports/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filing-bug-reports", 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/matlab/simulink-agentic-toolkit.git --path skills-catalog/model-based-design-core/filing-bug-reports--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 matlab/simulink-agentic-toolkit --skill filing-bug-reports -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install matlab/simulink-agentic-toolkit filing-bug-reports --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills-catalog/model-based-design-core/filing-bug-reports .gemini/skills/filing-bug-reports && 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 "filing-bug-reports" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/filing-bug-reports into .gemini/skills/filing-bug-reports/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filing-bug-reports", 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 matlab/simulink-agentic-toolkit filing-bug-reportsInstalls 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 matlab/simulink-agentic-toolkit --skill filing-bug-reports -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills-catalog/model-based-design-core/filing-bug-reports .github/skills/filing-bug-reports && 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 "filing-bug-reports" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/filing-bug-reports into .github/skills/filing-bug-reports/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filing-bug-reports", 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 matlab/simulink-agentic-toolkit --skill filing-bug-reports -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install matlab/simulink-agentic-toolkit filing-bug-reports --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/matlab/simulink-agentic-toolkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills-catalog/model-based-design-core/filing-bug-reports .opencode/skills/filing-bug-reports && 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 "filing-bug-reports" agent skill from https://github.com/matlab/simulink-agentic-toolkit/tree/main/skills-catalog/model-based-design-core/filing-bug-reports into .opencode/skills/filing-bug-reports/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "filing-bug-reports", 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
filing-bug-reports- GitHub stars
- 1.2k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 1,024 words
- Files
- 3 (incl. assets)
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue.
- Works in 7 steps: Reconstruct from conversation context.… → Gather environment details… → Reproduce the bug. Re-run the failing… → …
- The user says file a bug
- SKILL.md covers When to Use, When NOT to Use, Output Conventions and Workflow, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Filing Bug Reports is an agent skill from matlab/simulink-agentic-toolkit. Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue. Use when the user says 'file a bug', 'write a bug report', 'report this issue', or asks to document a defect for handoff.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including assets (for example `assets/bug-report-template.md` and `manifest.yaml`).
It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: The Simulink Agentic Toolkit gives your AI agent both the tools and the expertise to work effectively with Simulink and Model-Based Design.
When your agent uses it
- The user says file a bug
- Write a bug report
- Report this issue
- Asks to document a defect for handoff
Example prompts
- “file a bug”
- “write a bug report”
- “report this issue”
- “/filing-bug-reports”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Reconstruct from conversation context. You were present when the bug occurred — use your conversation history to extract
- Gather environment details programmatically. Don't ask the user for things you can look up
- Reproduce the bug. Re-run the failing operation to confirm it's reproducible and capture exact output. If it passes on retry, note it as…
- Shrink to a minimal reproduction. Remove every step, file, and variable that isn't needed to trigger the bug. The goal is the smallest…
- Ask the user ONLY for what you cannot determine
- Write the report using the template in assets/bug-report-template.md. Fill every required section. Mark optional sections N/A if not…
- Review before saving. Verify
What it can do on your machine
Read from SKILL.md and the folder at commit c58e6ae. 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
Filing Bug Reports loads about 1.9k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 1,024 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 1,024 words (~1,910 tokens).
“Generate a self-contained bug report as a Markdown file that gives a receiving developer everything needed to reproduce the issue — without prescribing root cause or solution.”
- name
- filing-bug-reports
- license
- https://www.mathworks.com/content/dam/mathworks/license/pmrl/license.md
- metadata.author
- MathWorks
- metadata.version
- 1.3
Files
SKILL.md and 2 other files (assets) in skills-catalog/model-based-design-core/filing-bug-reports of matlab/simulink-agentic-toolkit.
- SKILL.md
- assets/bug-report-template.md
- manifest.yaml
Open the folder on GitHubat commit c58e6ae
Compare with similar skills
Filing Bug Reports 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 |
|---|---|---|---|---|---|---|
| Filing Bug Reports this skillmatlab/simulink-agentic-toolkit | 1.2k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Dogfood Exploratory QAvercel-labs/agent-browser | 44k | 8 repos | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Codex Plugin QAcode-yeongyu/oh-my-openagent | 70k | 1 repos | ~1.9k | Automated safety check: Pass | Custom licence | |
| DeerFlow Smoke Testbytedance/deer-flow | 83k | — | ~2.5k | Automated safety check: Notes | MIT | |
| CodexBar Live QAsteipete/CodexBar | 22k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Diagnose Playwright Failure as Product Bugappsmithorg/appsmith | 41k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
DeerFlow Smoke Test
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
CodexBar Live QA
steipete/CodexBar
Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.
Diagnose Playwright Failure as Product Bug
appsmithorg/appsmith
Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
More from matlab/simulink-agentic-toolkit
All 43 skills in this repoResolve Design Errors
matlab/simulink-agentic-toolkit
A skill your agent uses when asked to run Design Error Detection (quick defect scan), find design errors in a Simulink model, perform root cause analysis on DED findings, fix division-by-zero…
Simscape Write Ssc
matlab/simulink-agentic-toolkit
A skill your agent uses when writing or editing Simscape Language (.ssc) source files — components, domains, or functions.
Simulink Optimizing Embedded Code
matlab/simulink-agentic-toolkit
Optimizes Simulink models for Embedded Coder generated code.
Checking Model Compliance
matlab/simulink-agentic-toolkit
A skill your agent uses when the user asks to check Simulink model compliance against a standard (MISRA, MAB, JMAAB, ISO, DO, IEC, EN, CERT C/CWE, AUTOSAR, Simulink Code Inspector (SLCI)), wants to…
Fix Sldv Incompatibility
matlab/simulink-agentic-toolkit
A skill your agent uses when a Simulink model is incompatible with Simulink Design Verifier (sldvcompat returns false, or an SLDV analysis errors out on an unsupported construct) and needs to be…
Simulink Collect Metrics
matlab/simulink-agentic-toolkit
Collect and assess quality metrics for Simulink models using the metric.Engine API.
Related
Categories
Questions about Filing Bug Reports
What does Filing Bug Reports do?
Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue. Filing Bug Reports is an agent skill from matlab/simulink-agentic-toolkit. Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue.
When should I use Filing Bug Reports?
Filing Bug Reports fits situations like: the user says file a bug; write a bug report; report this issue; asks to document a defect for handoff.
How do I install Filing Bug Reports in Claude Code?
Run `npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -a claude-code`. Or copy the skill folder (skills-catalog/model-based-design-core/filing-bug-reports in matlab/simulink-agentic-toolkit) into .claude/skills/filing-bug-reports in your project. Claude Code loads it when a task matches its description.
How do I install Filing Bug Reports in Codex?
Run `npx skills add matlab/simulink-agentic-toolkit --skill filing-bug-reports -a codex`. Or copy the skill folder (skills-catalog/model-based-design-core/filing-bug-reports in matlab/simulink-agentic-toolkit) into .agents/skills/filing-bug-reports in your project. Codex loads it when a task matches its description.
Can I use Filing Bug Reports 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 matlab/simulink-agentic-toolkit --skill filing-bug-reports -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/filing-bug-reports, .gemini/skills/filing-bug-reports, .github/skills/filing-bug-reports and .opencode/skills/filing-bug-reports in your project.
What does Filing Bug Reports need to run?
SKILL.md names no scripts, command-line tools or credentials: Filing Bug Reports is instructions for the agent only.
Does Filing Bug Reports 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 Filing Bug Reports 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 Filing Bug Reports use?
Filing Bug Reports 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 Filing Bug Reports use?
About 1.9k tokens (SKILL.md is roughly 7.6k 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 Filing Bug Reports?
Skills that share tags, products or a category with Filing Bug Reports: Dogfood Exploratory QA (vercel-labs/agent-browser, 44k stars), Codex Plugin QA (code-yeongyu/oh-my-openagent, 70k stars), DeerFlow Smoke Test (bytedance/deer-flow, 83k stars) and CodexBar Live QA (steipete/CodexBar, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Filing Bug Reports?
matlab (a GitHub organization) maintains it in matlab/simulink-agentic-toolkit, which has 1,199 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 7, 2026.
Source: matlab/simulink-agentic-toolkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.