help

name	help
license	MIT
compatibility	Claude Code 2.1.220+.
description	OrchestKit help directory with categorized skill listings. Use when discovering skills for a task, finding the right workflow, or browsing capabilities.
argument-hint	[category]
context	inherit
version	2.1.0
author	OrchestKit
tags	["help","documentation","skills","discovery","meta"]
user-invocable	true
allowed-tools	["AskUserQuestion","Read","Grep","Glob"]
complexity	low
persuasion-type	collaborative
effort	low
model	haiku
metadata	{"category":"document-asset-creation"}
triggers	{"keywords":["help","what skills","skills can i","available commands","which skill","show me skills","ork commands","what can","whats ork","skill for"],"examples":["what orchestkit skills can i use","show me the available ork commands","help me find the right skill for code review"],"anti-triggers":["fix","implement","doctor","setup","explore","assess"]}

OrchestKit Skill Directory

Dynamic skill discovery: enumerates the installed plugin at runtime so listings are never stale.

CC 2.1.121+ tip: if you just want to find one skill quickly, the native /skills command now has type-to-filter — open it and start typing the skill name. Use /ork:help when you want categorized browsing or rationale for why a skill applies.

Quick Start

/ork:help           # Show all categories
/ork:help build     # Show BUILD skills only
/ork:help git       # Show GIT skills only
/ork:help all       # List every user-invocable skill

Argument Resolution

CATEGORY = "$ARGUMENTS[0]"  # Optional: build, git, plan, quality, memory, config, explore, design, ops, all
# If provided, skip AskUserQuestion and show that category directly.
# $ARGUMENTS is the full string (CC 2.1.59 indexed access)

---

STEP 0: Dynamic Skill Discovery

ALWAYS run this first to get accurate, up-to-date skill data:

# ${CLAUDE_PLUGIN_ROOT} is set by the plugin runtime and points at the INSTALLED
# plugin. That is the normal case: a marketplace user has no src/ directory.
SKILLS_ROOT = "${CLAUDE_PLUGIN_ROOT}/skills"
matches = Grep(pattern="user-invocable:\\s*true", path=SKILLS_ROOT, output_mode="files_with_matches")

# Dogfooding fallback: inside the OrchestKit repo itself the skills live in the
# source tree. Retry there if the env var was unset or the probe found nothing.
if not matches:
    SKILLS_ROOT = "src/skills"
    matches = Grep(pattern="user-invocable:\\s*true", path=SKILLS_ROOT, output_mode="files_with_matches")

If BOTH probes return zero files, say so plainly ("could not locate the OrchestKit skills directory, checked and ") and stop. Do NOT substitute a remembered list of skill names. Any such list is stale by construction and a confident wrong answer is worse than no answer.