Help

This is your entry point when you don't know what's available in the workspace. Type /help and it walks you through interactive discovery based on what you're trying to do: explore a codebase, fix a bug, build a feature, or prove something mathematically. You can also jump straight to /help workflows to see orchestrated pipelines like /fix and /build, /help agents for the full specialist catalog (scout, kraken, arbiter, etc.), or /help tools for CLI utilities like tldr and the Lean theorem prover. It's basically a living manual that shows you which workflows, agents, and hooks are wired up. Most useful when you inherit a heavily customized Claude setup and need to know what's actually there.

skills.sh installs: 493
GitHub stars: 3.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add parcadei/continuous-claude-v3 --skill help --agent claude-code

Installs into .claude/skills of the current project.

Files

/help - Workspace Discovery

Guide users through the capabilities of this workspace setup.

Usage

/help                    # Interactive guided discovery
/help workflows          # Workflow orchestration skills
/help agents             # Specialist agents catalog
/help tools              # CLI tools (tldr, prove, recall)
/help hooks              # Active hooks and what they do
/help advanced           # MCP, frontmatter, customization
/help <name>             # Deep dive on specific skill/agent

Behavior Based on Arguments

No Arguments: Interactive Discovery

Use AskUserQuestion to guide the user:

question: "What are you trying to do?"
header: "Goal"
options:
  - label: "Explore/understand a codebase"
    description: "Find patterns, architecture, conventions"
  - label: "Fix a bug"
    description: "Investigate, diagnose, implement fix"
  - label: "Build a feature"
    description: "Plan, implement, test new functionality"
  - label: "Prove something mathematically"
    description: "Formal verification with Lean 4"

Based on response, show relevant tools:

SKILL.md on GitHub