ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a…
@yonatangrossInstall 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
Claude Code
$ npx -y skills add yonatangross/orchestkit --skill ork-explore --agent claude-code
Codex
$ npx skills add yonatangross/orchestkit --skill ork-explore -a codex -y
Cursor
$ npx skills add yonatangross/orchestkit --skill ork-explore -a cursor -y
Gemini CLI
$ npx skills add yonatangross/orchestkit --skill ork-explore -a gemini-cli -y
GitHub Copilot
$ npx skills add yonatangross/orchestkit --skill ork-explore -a github-copilot -y
OpenCode
$ npx skills add yonatangross/orchestkit --skill ork-explore -a opencode -y
Windsurf
$ npx skills add yonatangross/orchestkit --skill ork-explore -a windsurf -y
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.
Stats
301
Stars
40
Forks
Active
Maintenance
TypeScript
Language
MIT
License
Last commit
Created
Ships withorchestkit
The Complete AI Development Toolkit for Claude Code. 115 skills, 36 agents, 163 hooks. Install `ork` for stable (v10.x).
303123 skills36 agents
Stars on GitHub
Momentum
- stars in total
- 303
Other skills on orchestkit.
@yonatangrossInstall Skillork-brainstorm
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request…
@yonatangrossInstall Skillork-glyph
Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets,…
@yonatangrossInstall Skillork-implement
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a…
@yonatangrossInstall Skillork-review-pr
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a…
@yonatangrossInstall Skillork-verify
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to…
@yonatangrossInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about ork-explore.
- Which coding agents can use ork-explore?
- ork-explore installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.