Install
$ agentstack add skill-ai-driven-dev-framework-11-explore ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Explore
Surveys the current project across three axes so the user sees what is there and can dig into any of them. It maps the project, it never prescribes a next step.
Axes
- Tooling: the AIDD capabilities installed, the skills, agents, commands, rules, hooks, MCP servers, and plugins. What the user can run.
- Context: the context layer, the memory bank, the specs and plans, and the AI context files. What the AI knows about the project.
- Codebase: the project itself, the stack and the high-level structure. What the project is.
Actions
| # | Action | Role | Input | | --- | -------- | ---------------------------------------------------------------- | ----------------- | | 01 | survey | Scan the three axes and present a compact map | project root | | 02 | drill | Descend one axis or all, level by level, match an intent if any | a scope or a goal |
Detect the project's AI tools first, from the signals in references/ai-mapping.md. Then route by what the user asked: no scope given runs survey for a compact map, a named axis or "all" runs drill straight away. Always propose the axes when the request is open, never assume one. Run each action's ## Test before the next.
Transversal rules
- Map, never prescribe. Explore shows what is there across the axes and descends into it on request. It never tells the user the next step, that is the onboard skill's job, at any depth.
- Detect the tools before either action. A surface a tool does not have is skipped, never an error.
- Propose, then accept. Offer the axes or all when the request is open, run the user's pick directly when they name one.
- Descend one level per confirmation. Wait for the user at every level, stop at a leaf or when they are done.
- List only what is actually installed or present, never invent an item.
- Never hardcode a tool. Per-tool scan paths and formats live in
references/ai-mapping.md. - Point, do not run. Return an item's invocation path and stop.
References
references/ai-mapping.md: the per-tool signals, scan paths, and formats for the Tooling and Context axes.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ai-driven-dev
- Source: ai-driven-dev/framework
- License: MIT
- Homepage: https://www.ai-driven-dev.fr/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.