Skill
ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate,…
@yonatangrossView SkillDevelopment
Skill
/ork-explore
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or
Install
$ npx -y skills add yonatangross/orchestkit --skill ork-explore --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/ork-explore
Context preview
The summary Claude sees to decide when to auto-load this skill.
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or
SKILL.md
ork-explore.SKILL.mdname: ork-explore
description: Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or fix the code.
Ork Explore
Stay read-only. Start with the task boundary, repository instructions, entry points, and the smallest searches that can prove the execution path. Cite files and symbols for every material claim; distinguish confirmed behavior from inference.
When the path runs through a third-party library or framework, read its current documentation with the context7 MCP server: call `resolve-library-id` to get the library ID, then `query-docs`. Those are the only two tools it exposes. A recalled API detail you could not confirm belongs in the unknowns list, not in the map.
Explore in one context by default. Fan out only for three or more independent questions such as structure, data flow, tests, and deployment. Use a flat fan-out, make each assignment bounded and read-only, and ask for concise evidence rather than proposed fixes. Prefer `ork_explorer` when installed; otherwise use Codex's built-in `explorer`.
Return a compact map: entry points, important components and dependencies, tests/observability, risks or unknowns, and the next smallest investigation. Do not change files or turn the map into an implementation plan unless asked.
Read more
name: ork-explore description: Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or fix the code.
Ork Explore
Stay read-only. Start with the task boundary, repository instructions, entry points, and the smallest searches that can prove the execution path. Cite files and symbols for every material claim; distinguish confirmed behavior from inference.
When the path runs through a third-party library or framework, read its current documentation with the context7 MCP server: call `resolve-library-id` to get the library ID, then `query-docs`. Those are the only two tools it exposes. A recalled API detail you could not confirm belongs in the unknowns list, not in the map.
Explore in one context by default. Fan out only for three or more independent questions such as structure, data flow, tests, and deployment. Use a flat fan-out, make each assignment bounded and read-only, and ask for concise evidence rather than proposed fixes. Prefer `ork_explorer` when installed; otherwise use Codex's built-in `explorer`.
Return a compact map: entry points, important components and dependencies, tests/observability, risks or unknowns, and the next smallest investigation. Do not change files or turn the map into an implementation plan unless asked.
Ships withorchestkit
The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.
Get the whole plugin
Stats
264
Stars
28
Forks
Active
Maintenance
TypeScript
Language
MIT
License
1d ago
Last commit
8mo ago
Created
Repo: yonatangross/orchestkit
Other skills on orchestkit.
@yonatangrossView SkillSkill
ork-brainstorm
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think…
@yonatangrossView SkillSkill
ork-implement
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed…
@yonatangrossView SkillSkill
ork-review-pr
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review…
@yonatangrossView SkillSkill
ork-verify
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove,…
@yonatangrossView SkillSkill
accessibility
Accessibility patterns for WCAG 2.2 compliance, keyboard focus management, React Aria component patterns, cognitive inclusion, native HTML-first philosophy,…
@yonatangrossView Skill