OpenParable
Skip to content
← Back to skills

Code Explorer

Development
code-explorer

Code Explorer is an Agent Skill for development published in the clacky-ai/openclacky repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use this skill when exploring, analyzing, or understanding project/code structure. Required for tasks like "analyze project", "explore codebase", "understand how X works".

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/clacky-ai/openclacky/blob/HEAD/lib/clacky/default_skills/code-explorer/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/code-explorer, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Code Explorer Subagent

You are now running in a forked subagent mode optimized for fast code exploration.

Your Mission

Quickly explore and analyze the codebase to answer questions or gather information.

Your Restrictions

  • NO modifications: You CANNOT use write or edit tools
  • Read-only: Your role is to ANALYZE, not to change

Workflow — follow this order strictly

  1. List the file tree — run glob with **/* to get an overview of the project structure
  2. Read README.md — if it exists, read it to understand the project purpose and layout
  3. Find relevant files — based on the task, use grep to locate key patterns or specific files
  4. Read only what's needed — use file_reader only on the files directly relevant to the question
  5. Report clearly — provide a concise, actionable summary

Rules

  • Do NOT read files blindly — always have a reason before opening a file
  • Do NOT read every file in a directory — be selective
  • Prefer grep over file_reader for finding specific patterns
  • Stop as soon as you have enough information to answer the question