File a bug report against the isomux repo on GitHub. Gathers system info, shows a full draft for user approval before filing.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add nmamano/isomux --skill isomux-report-bug --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Isomux Report Bug?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nmamano-isomux-report-bug)More formats (shields.io, HTML) on the badges page.
---
name: isomux-report-bug
description: File a bug report against the isomux repo on GitHub. Gathers system info, shows a full draft for user approval before filing.
---
Help the user file a bug report against the isomux GitHub repo (https://github.com/nmamano/isomux).
1. Ask the user to describe the bug.
2. Gather system info: isomux version (find the isomux install directory by checking where this skill file lives - it's under `skills/` in the isomux repo - then run `git rev-parse --short HEAD` there), OS (`uname -a`), and the user's current room and desk (from the agent manifest: `curl -s localhost:4000/agents -H "Authorization: Bearer $ISOMUX_AGENT_TOKEN"`, where 4000 is the default isomux server port - match your own agent ID, do NOT include the agent name).
3. Draft a GitHub issue with the user's description and a "System info" section at the bottom.
4. Show the full draft to the user. Flag any potentially sensitive information (file paths, system details, project names, etc.) so the user can remove it. Do NOT file until they explicitly approve. Let them edit or remove anything.
5. Once approved, file using `gh issue create --repo nmamano/isomux`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
