Skip to content
Agentmart
Submit a tool

ae-explore

Explore a solution direction.

Skill by AndreaCatalucci

IndexedMIT★ 1
Write a review

Chalk Labs

Need help deploying ae-explore?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/andreacatalucci-ae-explore

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Explore a solution direction. Use when a solution exists and how it should work is still open.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/ae-explore

What's inside

Skill name
ae-explore
Description
Explore a solution direction. Use when a solution exists and how it should work is still open.
License
MIT
Instructions
34 lines in SKILL.md · view on GitHub

Before installing

  • Instructions call the network

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Explore

Read the request and relevant project context.

Compare different approaches where the choice matters. Treat each as a hypothesis.

When inspection cannot settle a consequential hypothesis, build the smallest runnable experiment that can. Name the question, decisive observation, and stopping condition first. Use the project's tools, representative data, and isolated or stubbed writes. Add only the interface and checks needed to answer the question. Record the result and decision. Keep requested runnable experiments with a run command; remove disposable scratch work outside that deliverable. Production implementation uses `ae-work` and its verification criteria.

When a hypothesis is cheap to check, check it: curl a public API to see its real response shape, auth, and rate limits; fetch a site's terms or pricing page to check licensing; read the relevant docs; run a quick snippet to confirm a claim.

Ask only decisions that materially affect the next experiment or implementation and require the user's judgment. Batch independent questions sparingly, give recommended answers with concrete alternatives, and wait for required decisions. Resolve routine reversible choices from the available evidence.

A question that depends on an unanswered one belongs to a later round. Sharpen fuzzy or conflicting terms into the project's own words. Stress-test a relationship with a concrete scenario when the boundary is the real issue.

Track:

- concepts and prototypes explored;
- hypotheses;
- learnings;
- emerging principles;
- decisions;
- remaining uncertainty;
- leading concept;
- next experiments.

Challenge contradictions and unnecessary scope directly. Conclude when a leading concept is named and remaining uncertainty is marked. Unasked branches become remaining uncertainty.

Keep one bounded decision inline. For multi-round exploration or a requested artifact, maintain a Concept Notebook under `docs/concepts/` covering the relevant tracks. Point to evidence rather than restating it.

The deliverable is the decision and its evidence, plus any requested runnable experiment. Unobserved results remain open.

Before finishing, run the `unslop` skill.

From AndreaCatalucci/andrea-engineering, MIT.

Signals

Stars
1
Forks
0
Open issues
0
Last commit (this folder)
Sep 6, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from AndreaCatalucci

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get ae-explore running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying ae-explore?

CallGet help
Cite this page

ae-explore skill. Agent Mart. https://agentmart.dev/skills/andreacatalucci-ae-explore (last updated 2026-10-24)