Hooks
What crypto-trading-desk runs automatically, and when. A hook is a command Claude Code fires at a fixed moment, without you asking for it.
> /plugin marketplace add hugoguerrap/crypto-claude-desk > /plugin install crypto-trading-desk@hugoguerrap
Ships with crypto-trading-desk. Installing the plugin gets these hooks.
What fires, and when
SessionStart
Fires once when a session begins, and again after a context compaction. It is where a plugin sets up its environment, or restores state the compaction dropped.
- Matches
startup${CLAUDE_PLUGIN_ROOT}/hooks/post-setup.sh
Where it lives
- hooks/post-setup.shRunsGitHub
Read the script
#!/usr/bin/env bash # Lightweight session startup hook. # Only creates data directories. No dependency management. # Dependencies are handled by /setup skill (first time) and uv run (ongoing). ROOT="${CLAUDE_PLUGIN_ROOT:-$(cd "$(dirname "$0")/.." && pwd)}" mkdir -p "$ROOT/data/trades" \ "$ROOT/data/reports" \ "$ROOT/data/logs" \ "$ROOT/data/db" \ "$ROOT/data/create" \ "$ROOT/.claude/agent-memory/portfolio-manager" 2>/dev/null || true
Read the script before you install anything that runs on your machine. This is the one part of a plugin that acts without being asked.
I used to spend weeks building multi-agent systems with LangGraph, CrewAI, and AutoGen. Hundreds of lines of Python orchestration code, custom state machines, fragile message passing between agents.
Repo: hugoguerrap/crypto-claude-desk