ClawHub

Jarvis Bug Triage 01

v1.0.0

Triage production bugs fast with repro isolation and risk-first fixes. Use when handling development work that needs repeatable steps, quality gates, and pra...

⭐ 0· 660·0 current·0 all-time
by@xammarie
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (bug triage, repro isolation, risk-first fixes) matches the SKILL.md playbook. There are no requested binaries, environment variables, or install steps that don't belong to a triage workflow.
ℹ
Instruction Scope
The instructions are high-level and constrained to producing a reproducible workflow, checkpoints, evidence, risks, and action items. The playbook does not instruct the agent to read system files, access credentials, or transmit data externally, but it is intentionally open-ended (asks for 'available artifacts' and to 'record evidence'), so the agent may request user-provided logs or snippets — users should avoid sharing secrets.
✓
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes disk write and supply-chain risk.
✓
Credentials
No environment variables, credentials, or config paths are required. The skill does not request unrelated secrets or system access.
✓
Persistence & Privilege
Defaults are used (not always: true). The skill does not request permanent presence or elevated privileges and does not modify other skills or system-wide settings.
Assessment
This skill is an instruction-only triage playbook and is internally coherent. It poses low technical installation risk, but be cautious about the data you provide when using it: do not paste credentials, API keys, unredacted PI, or full production secrets into prompts or logs. If the skill outputs shell commands or remediation steps, review and test them in a safe environment before running them in production. If you prefer tighter control, only invoke the skill interactively (don’t enable any automated/autonomous execution) and scrub logs or artifacts before sharing.

Like a lobster shell, security has layers — review code before you run it.

latestvk97egy4m459fgc3zbpzwjy5vz181atyy

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments