Agent skill · writing content · yonatangross
help
OrchestKit skill directory by category. Use when looking for the right skill or workflow.
Why this skill is useful
Codifies a structured approach to discovering skills and workflows, reducing guesswork for users.
What it needs
About 5k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
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 help when you want categorized browsing or rationale for why a skill applies. Quick Start Argument Resolution --- STEP 0: Dynamic Skill Discovery ALWAYS run this first to get accurate, up-to-date skill data: If BOTH probes return zero files, say so plainly ("could not locate the OrchestKit skills directory, checked ${CLAUDEPLUGINROOT}/skills and src/skills") 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. For each matched file, read the frontmatter to get name, description, version, complexity, argument-hint and tags: Every number rendered later is derived from this scan, never typed as a literal: Build the skill list dynamically. Never hardcode counts or skill names. --- STEP 1: Category Selection If CATEGORY argument provided, skip to STEP 2 with that category. Otherwise, present categories interactively: --- STEP 2: Render Category For the selected category, render the skill table from the data gathered in STEP 0. Category Definitions Categories are defined by tag predicates, never by a list of skill names, so a newly shipped skill lands in the right bucket without editing this file. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/help