Idea Darwin
sickn33/agentic-awesome-skills
Darwinian idea evolution engine — toss rough ideas onto an evolution island, let them compete, crossbreed, and mutate through structured rounds to surface your strongest concepts.
Explore an idea against the actual codebase without changing files.
MITAuto-check passed
Install Explore
$ npx skills add aiblueprinthq/ai-blueprint --skill explore -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aiblueprinthq/ai-blueprint explore --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/explore .claude/skills/explore && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "explore" agent skill from https://github.com/aiblueprinthq/ai-blueprint/tree/main/.agents/skills/explore into .claude/skills/explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explore", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aiblueprinthq/ai-blueprint/tree/main/.agents/skills/exploreType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aiblueprinthq/ai-blueprint --skill explore -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aiblueprinthq/ai-blueprint explore --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/explore .agents/skills/explore && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "explore" agent skill from https://github.com/aiblueprinthq/ai-blueprint/tree/main/.agents/skills/explore into .agents/skills/explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explore", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aiblueprinthq/ai-blueprint --skill explore -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aiblueprinthq/ai-blueprint explore --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/explore .cursor/skills/explore && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "explore" agent skill from https://github.com/aiblueprinthq/ai-blueprint/tree/main/.agents/skills/explore into .cursor/skills/explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explore", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aiblueprinthq/ai-blueprint.git --path .agents/skills/explore--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aiblueprinthq/ai-blueprint --skill explore -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aiblueprinthq/ai-blueprint explore --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/explore .gemini/skills/explore && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "explore" agent skill from https://github.com/aiblueprinthq/ai-blueprint/tree/main/.agents/skills/explore into .gemini/skills/explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explore", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aiblueprinthq/ai-blueprint exploreInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aiblueprinthq/ai-blueprint --skill explore -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/explore .github/skills/explore && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "explore" agent skill from https://github.com/aiblueprinthq/ai-blueprint/tree/main/.agents/skills/explore into .github/skills/explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explore", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aiblueprinthq/ai-blueprint --skill explore -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aiblueprinthq/ai-blueprint explore --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aiblueprinthq/ai-blueprint.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/explore .opencode/skills/explore && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "explore" agent skill from https://github.com/aiblueprinthq/ai-blueprint/tree/main/.agents/skills/explore into .opencode/skills/explore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "explore", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
explore- GitHub stars
- 461
- Token cost
- ~1.1k tokens
- SKILL.md length
- 600 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- MIT
At a glance
Explore an idea against the actual codebase without changing files.
- Considering an idea
- SKILL.md covers Start from the question, Discuss the options, Keep the boundaries clear and Neighbors and handoff
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Weighing options without writing a spec
What it does
Explore is an agent skill from aiblueprinthq/ai-blueprint. Explore an idea against the actual codebase without changing files. Investigate whether a change would help, compare alternatives and tradeoffs, and discuss uncertainty before deciding whether to plan anything. Use for /explore, considering an idea, or weighing options without writing a spec.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: A file-backed, spec-driven AI coding workflow framework for building real software while staying in control. The licence is MIT.
When your agent uses it
- Considering an idea
- Weighing options without writing a spec
Example prompts
- “/explore”
What it can do on your machine
Read from SKILL.md and the folder at commit 1a0b660. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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.
Context cost
Explore loads about 1.1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 600 words of instructions outside code blocks.
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
Auto-check passed
The automated check found no risky patterns in SKILL.md.
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 aiblueprinthq/ai-blueprint at commit 1a0b660, republished under its MIT licence (© aiblueprinthq). 600 words, ~1,100 tokens.
Download SKILL.mdSave it as
.claude/skills/explore/SKILL.md (or your agent's skills folder).- name
- explore
- description
- Explore an idea against the actual codebase without changing files. Investigate whether a change would help, compare alternatives and tradeoffs, and discuss uncertainty before deciding whether to plan anything. Use for /explore, considering an idea, or weighing options without writing a spec.
explore - investigate an idea before deciding to build
Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.
Explore is a read-only conversation grounded in the actual project. It can help with questions such as whether caching would help a dashboard, whether teams belong in the product, or which upload approach fits existing code.
No plans or active feature are required. Do not require /overview, invent a
plan, or treat missing Blueprint context as a blocker to discussing the idea.
This command never writes activity state, including blueprint/.state/run.json.
Start from the question
Use the supplied topic or relevant conversation context. With neither, ask what the user wants to investigate. For a vague idea, state a tentative interpretation and ask a focused question only when its answer changes the investigation.
Reuse context already loaded in the session. Read relevant project instructions, code, tests as text, manifests, and existing plans when they help answer the question. Follow the actual implementation far enough to support your claims; point to concrete files or symbols. Avoid scanning unrelated parts of the repo. Read-only Git inspection can establish what exists or is already in progress.
Authoritative documentation lookup is appropriate when technical uncertainty needs it. Distinguish documented facts from what this project actually uses. Missing code or evidence is an uncertainty to explain, not permission to execute an experiment or to invent current behavior.
Discuss the options
Keep the conversation proportional to the question. Compare plausible options against the user's needs and existing project constraints. Include doing nothing when the current behavior may already be sufficient. Do not invent scale, security requirements, or new abstractions to justify a change.
Explain the strongest case against your recommendation and how confident you are. Separate observed facts, assumptions, and unanswered questions. Say what evidence could change the recommendation without gathering it through execution. An unresolved question or a recommendation to leave the project alone is a valid outcome.
Use a small diagram in the response when it makes a relationship or tradeoff clearer. Do not create diagram files. There is no mandatory output template, report, question count, or next-step checklist. Follow the user's responses and let the discussion continue as long as useful.
Show full SKILL.md (215 more words)Show less
Keep the boundaries clear
- Never create, edit, or delete files, including specs, plans, notes, generated output, and activity state. Do not save the conversation into the project.
- Never install dependencies, execute product code, run tests or builds, start servers, perform browser interactions, or call state-changing tools. Read source and existing evidence instead of testing a hypothesis by execution.
- Never create or switch branches, commit, merge, push, publish, or deploy.
- Never turn a request to discuss an idea into approval to plan or implement it. If the user asks for changes, explain the appropriate handoff and keep this Explore invocation read-only. Do not invoke another command automatically.
Neighbors and handoff
/briefexplains an existing build-plan item, its scope, dependencies, and size. Explore can discuss an unplanned idea or question a planned approach./discoverydevelops broader product direction and reviewed planning drafts. Explore does not draft either planning file./debugreproduces and isolates an actual failure. Explore discusses options without executing code to diagnose or verify them./featurewrites a buildable spec;/fixspecifies a confirmed small change. Suggest the appropriate command only when the user is ready to proceed.
Do not force a handoff at the end of every response. Keep discussing the idea when that is what the user wants, and leave the project unchanged.
© aiblueprinthq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/explore of aiblueprinthq/ai-blueprint.
Open the folder on GitHubat commit 1a0b660
Compare with similar skills
Explore next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Explore this skillaiblueprinthq/ai-blueprint | 461 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Idea Darwinsickn33/agentic-awesome-skills | 47k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Idea Refinementaddyosmani/agent-skills | 103k | 6 repos | ~2k | Automated safety check: Pass | MIT | |
| Make Changesremix-run/remix | 33k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Code ChangesJanDeDobbeleer/oh-my-posh | 24k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Orch Change Featureaffaan-m/ECC | 275k | 1 repos | ~420 | Automated safety check: Pass | MIT |
Similar skills
Idea Refinement
addyosmani/agent-skills
Guides a conversation that takes a vague idea through divergent and convergent thinking and ends in a markdown one-pager covering scope and assumptions.
Make Changes
remix-run/remix
Create or update Remix repo change files under packages//.changes.
Code Changes
JanDeDobbeleer/oh-my-posh
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea.
Orch Change Feature
affaan-m/ECC
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit.
Change Management
sickn33/agentic-awesome-skills
Implement change management processes. An agent skill from sickn33/agentic-awesome-skills.
More from aiblueprinthq/ai-blueprint
All 20 skills in this repoAdopt
aiblueprinthq/ai-blueprint
Adopt Blueprint into an existing brownfield codebase by surveying shipped behavior and generating plans, standards, commands, adapter choices, and visibility setup.
CI
aiblueprinthq/ai-blueprint
Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI, with an optional local pre-push hook.
Doctor
aiblueprinthq/ai-blueprint
Run a Blueprint health and context check covering setup, adapters, commands, visibility, plans, overview freshness, configuration, dashboard state, and workflow drift.
Feature
aiblueprinthq/ai-blueprint
Turn the next, named, or numbered build-plan feature into a buildable current-feature.md spec with small steps and done-when criteria.
Onboard
aiblueprinthq/ai-blueprint
Onboard a fresh or early scaffold after Blueprint is overlaid by tuning commands, standards, adapters, visibility, and context loading.
Overview
aiblueprinthq/ai-blueprint
Validate and normalize project-plan.md and build-plan.md, then generate the durable project-overview.md used by agents.
Questions about Explore
What does Explore do?
Explore an idea against the actual codebase without changing files. Explore is an agent skill from aiblueprinthq/ai-blueprint. Explore an idea against the actual codebase without changing files.
When should I use Explore?
Explore fits situations like: considering an idea; weighing options without writing a spec.
How do I install Explore in Claude Code?
Run `npx skills add aiblueprinthq/ai-blueprint --skill explore -a claude-code`. Or copy the skill folder (.agents/skills/explore in aiblueprinthq/ai-blueprint) into .claude/skills/explore in your project. Claude Code loads it when a task matches its description.
How do I install Explore in Codex?
Run `npx skills add aiblueprinthq/ai-blueprint --skill explore -a codex`. Or copy the skill folder (.agents/skills/explore in aiblueprinthq/ai-blueprint) into .agents/skills/explore in your project. Codex loads it when a task matches its description.
Can I use Explore in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aiblueprinthq/ai-blueprint --skill explore -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/explore, .gemini/skills/explore, .github/skills/explore and .opencode/skills/explore in your project.
What does Explore need to run?
SKILL.md names no scripts, command-line tools or credentials: Explore is instructions for the agent only.
Does Explore access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Explore safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Explore use?
Explore is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Explore use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Explore?
Skills that share tags, products or a category with Explore: Idea Darwin (sickn33/agentic-awesome-skills, 47k stars), Idea Refinement (addyosmani/agent-skills, 103k stars), Make Changes (remix-run/remix, 33k stars) and Code Changes (JanDeDobbeleer/oh-my-posh, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Explore?
aiblueprinthq (a GitHub organization) maintains it in aiblueprinthq/ai-blueprint, which has 461 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 5, 2026.
Source: aiblueprinthq/ai-blueprint on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.