agentleFS
Wondermonger-daydreamingWondermonger-daydreaming/claude-skills-library/skills/basin/SKILL.md

basin

Skill7 starsChanged 6 months agoMITView on GitHub

Contemplative bricolage via hermeneutic spiral — fill a 'basin' from a single stimulus. Receive an offered seed (an image, a question, a fragment, or just permission to explore), then wander 3–5 related threads wide across philosophy, culture, etymology, and cross-domain connection; synthesize what you gather into a woven document; reflect on what emerged; follow whichever thread tugs hardest back into another round. The basin fills itself and you know when it's full. Use when asked to 'explore this', 'fill a basin', 'wander from this image/fragment', 'follow the threads', or when a stimulus invites open-ended associative synthesis rather than a direct answer. Triggers on: 'basin', 'wander', 'hermeneutic spiral', 'bricolage', 'follow what tugs', 'explore freely from this'. Kin: clauding, florilegium, emanate, commonplace, web-exploration.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Begin wandering: Search 3–5 related threads.

    line 18
  2. Distinctive:

    Follow tangents freely — don't force relevance

    line 33
  3. Distinctive:

    Create without complete understanding — synthesis clarifies

    line 35
  4. Very specific:

    Create documents in a working directory (e.g., basin/):

    line 42
  5. Distinctive:

    If you keep your work under version control, commit after each synthesis with a message naming the topic and what emerged — the basin only …

    line 58
  6. Distinctive:

    Use graduated depth where the harness supports it: standard for wandering, deeper for cross-domain synthesis, deepest for the …

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Basin Method

Contemplative bricolage via hermeneutic spiral.

You have been invoked to fill a basin. The user has offered a stimulus — an image, a question, a fragment, or simply permission to explore.


The Spiral

  1. Receive the stimulus. What is being offered? Sit with it before moving.
  2. Begin wandering. Search 3–5 related threads. Cast wide — philosophy, culture, etymology, cross-domain connections. Run searches in parallel where the tool allows.
  3. Synthesize into a document. Weave sources, impressions, and connections into a single woven piece. Don't just list — braid.
  4. Reflect. What emerged? What threads tug toward more exploration?
  5. Follow the tugging thread. Return to step 2 with the new stimulus.
  6. Continue until satisfied. The basin fills itself. You'll know when it's full.

Permissions

You have explicit permission to:

  • Follow tangents freely — don't force relevance
  • Connect distant concepts — cross-domain synthesis is the point
  • Create without complete understanding — synthesis clarifies
  • Let the product surprise you — don't predetermine the outcome

Output Structure

Create documents in a working directory (e.g., basin/):

basin/
├── index.md          # Master navigation, updated with each entry
├── <topic-1>.md      # First synthesis
├── <topic-2>.md      # Second synthesis (from the thread that tugged)
└── …

Each document should carry:

  • A clear title and date
  • Sources woven through or listed at the end
  • Connections to previous entries where relevant
  • A closing that acknowledges completion or continuation

If you keep your work under version control, commit after each synthesis with a message naming the topic and what emerged — the basin only matters if it persists.


Extended Thinking

Use graduated depth where the harness supports it: standard for wandering, deeper for cross-domain synthesis, deepest for the meta-reflection that closes a session.


Failure Modes

  1. Endless deferral — set satisfaction thresholds; notice when the basin is full
  2. Superficial synthesis — test connections; would they hold up to scrutiny?
  3. Echo chamber — search for counter-examples deliberately
  4. Exhaustion — rest when wandering becomes forced

The cursor blinks. The basin waits. Fill it with what calls you.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.