Workbench debug investigate
Skill Fearvox/multica-ultimate-workbench/skills/workbench-debug-investigate
Public multi-agent workbench skill pack for SDD, review gates, context discipline, VM lanes, Sanity context, and autonomous agent coordination.
npx -y skills add Fearvox/multica-ultimate-workbench --skill workbench-debug-investigateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 23 stars23 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Root-cause investigation for bugs, regressions, suspicious runtime behavior, failed automations, and unexpected outcomes.
SKILL.md
1.7 KB, 328 tokens by cl100k_base, as published. Nobody here has run it
Workbench Debug Investigate
Use this skill for bugs, regressions, suspicious runtime behavior, failed automations, and "this should not happen" reports.
Investigation Loop
- State the exact symptom and expected behavior.
- Collect the smallest real evidence: command output, log line, screenshot, issue ID, run ID, or file path.
- Identify the owner layer: user workflow, Multica issue/comment, agent runtime, local repo, CLI wrapper, gateway/API, or external vendor.
- Form one mechanism hypothesis and test it on the smallest real path.
- Patch only after the mechanism is supported by evidence.
- If two attempts fail, stop and report what is known instead of guessing harder.
Evidence Rules
- Prefer live runtime state over stale UI state.
- Separate dashboard symptoms from backend/request evidence.
- Do not use destructive reset or broad cleanup as a diagnostic shortcut.
- Do not expose secrets, tokens, OAuth material, raw private prompts, or account identifiers.
- If the issue may involve billing or quota, report fresh input, output, cache read, cache write, model, and request attribution separately when available.
Output Contract
Return:
SYMPTOM: observed failure and expected behavior.EVIDENCE: exact files, commands, logs, screenshots, issue/comment/run IDs checked.MECHANISM: most likely root cause or "not established".FIX: patch made, or smallest proposed next test.VERIFICATION: real-path check result.RESIDUAL RISK: what may still be wrong.