Help

What it does

When your agent uses it

• Discovering skills for a task
• Finding the right workflow
• Browsing capabilities

Example prompts

• “/help”

Requirements

• Python 3
• Compatibility (from SKILL.md): Claude Code 2.1.277+.
• Pre-approved tools (allowed-tools): AskUserQuestion, Read, Grep, Glob

Workflow steps

3 steps, taken from the step headings in SKILL.md.

1. 1Dynamic Skill Discovery
2. 2Category Selection
3. 3Render Category

What it can do on your machine

Read from SKILL.md and the folder at commit 0ef71d2. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • AskUserQuestion
  • Read
  • Grep
  • Glob

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are python and bash).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Claude Code 2.1.277+.

  From compatibility in the SKILL.md frontmatter.

Context cost

Help loads about 2.3k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 39 tokens; SKILL.md has 749 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~39

When it runs · the whole SKILL.md, loaded when a task matches

~2.3k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from yonatangross/orchestkit at commit 0ef71d2, republished under its MIT licence (© yonatangross). 749 words, ~2,282 tokens.

name

help

description

OrchestKit help directory with categorized skill listings. Use when discovering skills for a task, finding the right workflow, or browsing capabilities.

allowed-tools

AskUserQuestion, Read, Grep, Glob

compatibility

Claude Code 2.1.277+.

license

MIT

argument-hint

[category]

context

inherit

user-invocable

true

effort

low

model

haiku

metadata.category

document-asset-creation

metadata.version

2.1.0

metadata.author

OrchestKit

metadata.complexity

low

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

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)

# ${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")

Read(file_path=f"{SKILLS_ROOT}/{skill_dir}/SKILL.md", limit=25)

TOTAL = len(matches)   # user-invocable skill count

AskUserQuestion(
  questions=[{
    "question": "What type of task are you working on?",
    "header": "Category",
    # 4-option cap (CC schema): every category from STEP 2 is grouped into one of
    # 3 buckets + "Show all". STEP 2 renders the constituent categories for the
    # picked bucket. Descriptions name intents, never skills, so they cannot drift.
    "options": [
      {"label": "Build & ship", "description": "Writing code, tests, git and PRs, UI and design work"},
      {"label": "Plan & assess", "description": "Requirements, planning, quality assessment, review"},
      {"label": "Explore & operate", "description": "Codebase exploration, memory, setup, diagnostics, CI"},
      {"label": "Show all", "description": "List every user-invocable skill"}
    ],
    "multiSelect": false
  }]
)

/ork:{name}  v{version}  {complexity}
  {description}
  Example: /ork:{name} {argument-hint example}

"I need to implement user login"     → implement
"Show me the payment architecture"   → explore
"Review PR 123"                      → review-pr
"Is this code good?"                 → assess
"Plan out the billing redesign"      → visualize-plan

© yonatangross, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in src/skills/help of yonatangross/orchestkit.

• SKILL.md
• references/cc-keyboard-shortcuts.md
• rules/_sections.md
• rules/category-accuracy.md
• rules/skill-metadata-freshness.md
• test-cases.json

Open the folder on GitHubat commit 0ef71d2