cmux-diagnostics
Run end-user cmux diagnostics. Use when cmux hooks, notifications, session restore, settings, browser automation, socket access, CLI control, or agent resume behavior is not working, or when the user asks for a cmux health check, doctor report, or support-safe debug summary.
What this skill does
# cmux Diagnostics Use this skill to collect and interpret support-safe cmux diagnostics for end users. Default to read-only checks. Do not dump hook config files, session stores, prompt logs, tokens, or environment secrets. ## Quick Report Run the bundled read-only diagnostic script first: ```bash # From a cmux checkout skills/cmux-diagnostics/scripts/cmux-diagnostics # From an installed skill ~/.agents/skills/cmux-diagnostics/scripts/cmux-diagnostics # From a Codex-only skills.sh install ~/.codex/skills/cmux-diagnostics/scripts/cmux-diagnostics ``` Use `--include-context` only when workspace names, cwd paths, and current cmux identifiers are relevant to the user-reported issue: ```bash skills/cmux-diagnostics/scripts/cmux-diagnostics --include-context ``` ## What to Check 1. CLI and socket health: ```bash command -v cmux cmux ping cmux capabilities --json ``` If socket commands fail, check whether the agent is running inside a cmux terminal and whether socket automation is enabled. 2. Settings health: ```bash ~/.agents/skills/cmux-settings/scripts/cmux-settings validate ~/.agents/skills/cmux-settings/scripts/cmux-settings get terminal.autoResumeAgentSessions ``` If the user installed with `skills.sh`, use `~/.codex/skills/cmux-settings/scripts/cmux-settings` instead. If `terminal.autoResumeAgentSessions` is false, cmux restores panes but will not automatically resume saved agent sessions. 3. Hook installation: ```bash cmux hooks setup --agent codex cmux hooks setup --agent opencode cmux hooks setup ``` Only run install or uninstall commands after the user agrees. `cmux hooks setup` installs supported agents found on PATH and skips missing agents. 4. Session restore evidence: ```bash ls -lh ~/.cmuxterm/*-hook-sessions.json 2>/dev/null ``` Missing session stores usually means the agent has not run inside cmux since hooks were installed, hooks are disabled, or the agent integration does not support resume capture. 5. Notification path: ```bash cmux notify "cmux diagnostic test" ``` Use this only when the user is ready for a visible test notification. ## Interpretation - `cmux` not found: the CLI is not installed or not on PATH for this shell. - `cmux ping` fails: app is not reachable through the current socket path, the app is closed, or automation access is disabled. - No `CMUX_WORKSPACE_ID` or `CMUX_SURFACE_ID`: the command is probably running outside a cmux terminal. Some hooks intentionally no-op outside cmux. - Hook config exists but no session store: run one supported agent inside cmux after installing hooks, then re-check. - Session store exists but restore does not launch agents: check `terminal.autoResumeAgentSessions` and whether the saved executable still exists on PATH. - Settings validation fails: fix the config first. Invalid config can make later symptoms misleading. ## Rules - Stay read-only until the user asks to fix something. - Never print raw hook files, session JSON, prompt logs, shell history, tokens, or API keys. - Summarize file presence, size, modified time, and marker presence instead of contents. - Prefer narrow fixes such as `cmux hooks setup --agent codex` over reinstalling every integration. - After a fix, rerun the diagnostic script and report the changed lines.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.