Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From famdeck-toolkit
Use this skill whenever the user wants to install, reinstall, or add any tool from the Famdeck ecosystem (Atlas, Relay, Beads, Serena, Agent Mail, Context7) to their Claude Code setup. This skill is the correct handler for all Famdeck installation requests — it provides the terminal command the user must run outside Claude Code, since `claude plugin install` hangs when called from within a session. Invoke for: first-time setup, adding a specific missing tool, running the setup wizard, or fixing a broken plugin after an update. Do NOT invoke for: checking status of already-installed tools, configuring tools, or installing non-Famdeck software.
npx claudepluginhub ivintik/private-claude-marketplace --plugin famdeck-toolkitHow this skill is triggered — by the user, by Claude, or both
Slash command
/famdeck-toolkit:toolkit-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The setup script **must run from a regular terminal** (outside Claude Code) because `claude plugin
Prepares local development environment for Claude Code usage: detects OS, installs Git and GitHub CLI, and guides through optional installation phases for design and development workflows.
Performs first-time setup of a ClaudeClaw instance: installs dependencies, authenticates messaging channels, registers the main channel, and starts background services.
Installs Claude-Code-Tunnels Project Orchestrator into the project directory, verifies Python 3.10+, registers workspaces, connects messenger channels. Invoke via /claude-code-tunnels:setup-orchestrator.
Share bugs, ideas, or general feedback.
The setup script must run from a regular terminal (outside Claude Code) because claude plugin install and claude mcp add hang when invoked from within a running session.
Do NOT run the script yourself. Give the user the command to copy-paste into their terminal:
Interactive install (recommended):
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py
Install a specific tool (when the user named one):
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py --install <tool-name>
Install everything non-interactively:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/setup.py --non-interactive
After the user runs the command and comes back, use /toolkit-status to verify the result.