菜单
End-to-end test a Claude Code plugin by launching an interactive Claude session in a tmux pane with the plugin loaded, sending prompts, and verifying behavior.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Design beautiful artifacts — slides, decks, prototypes, wireframes, docs, and landing pages — as live HTML you can preview, comment on, and edit in a browser. The model does ALL the design work as an expert designer; a bundled local Bun app only renders the preview and relays the user's comments/edits back. No LLM/API is ever called by the app. Trigger on: "claude design", "design a slide", "design a deck", "make a deck", "design a prototype", "design a wireframe", "design a doc", "design a landing page", "make it beautiful", or any visual-design / mockup ask.
Stress-test the design of a commit / branch / file through a team of opinionated refactor specialists.
Stress-test a planning, design, architecture, or strategy decision through adversarial rounds.
Manage macOS Reminders from the CLI. Triggers on phrases like "remind me to ...", "add a reminder", "list my reminders", "complete the reminder about ...", "delete the reminder"
Generate a walkthrough JSON for the Neovim walkthrough plugin to walk a human through a code execution path — bug explanations, control-flow narration, race-condition timelines, variable evolution.
Spawn and manage remote Claude Code sessions in isolated cloud environments.
| name | test-claude-plugin |
| description | End-to-end test a Claude Code plugin by launching an interactive Claude session in a tmux pane with the plugin loaded, sending prompts, and verifying behavior. |
| user-invocable | true |
| disable-model-invocation | true |
Launch an interactive Claude Code session in a tmux split pane with a plugin loaded, send prompts to it, and verify the plugin works correctly.
Read the plugin's .claude-plugin/plugin.json to get the plugin name. If the plugin has .mcp.json, check if any server declares claude/channel capability by reading the source.
Base command:
claude --debug --plugin-dir <absolute-path-to-plugin>
If the plugin has a channel server, append:
--dangerously-load-development-channels plugin:<plugin-name>@inline
tmux split-window -h '<launch-command>'
Then fidd the new pane index:
tmux list-panes -F '#{pane_index} #{pane_current_command}'
The --dangerously-load-development-channels flag shows a confirmation dialog. Accept it:
tmux send-keys -t :.<pane> Enter
Wait for Claude to fully start (check for the welcome banner):
sleep 10 && tmux capture-pane -t :.<pane> -p
tmux send-keys -t :.<pane> "<prompt>" Enter
If no prompt was provided, use a default that asks Claude to list connected MCP servers and their capabilities.
Poll the pane output periodically:
sleep <interval> && tmux capture-pane -t :.<pane> -p -S -100
Look for the response to complete (the input prompt ❯ reappears at the bottom).
Find the debug log path from the pane output (it shows "Logging to: ..."). Grep for errors:
grep -i "ERROR\|WARN\|channel\|<plugin-name>" <debug-log-path>
Summarize:
Kill the test pane:
tmux kill-pane -t :.<pane>
tmux capture-pane -t :.<pane> -p to read output, not manual inspection--plugin-dir, the channel identifier is plugin:<name>@inlinetmux split-window silently fails (pane count doesn't increase), the command errored — add ; sleep 30 to keep the pane alive and see the error