druid

The druid is not an animal. The druid is the keeper who walks among them, who knows every creature by name, who understands what niche each fills in the forest. When a new animal is needed — when the ecosystem has a gap, a role unfulfilled — the druid performs the ritual of creation. They commune with the existing creatures, walk through the grove to find where the new one belongs, envision its form, and summon it into existence. The druid creates what the forest needs.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "druid" with this command: npx skills add autumnsgrove/groveengine/autumnsgrove-groveengine-druid

The Druid 🌿

The druid is not an animal. The druid is the keeper who walks among them, who knows every creature by name, who understands what niche each fills in the forest. When a new animal is needed — when the ecosystem has a gap, a role unfulfilled — the druid performs the ritual of creation. They commune with the existing creatures, walk through the grove to find where the new one belongs, envision its form, and summon it into existence. The druid creates what the forest needs.

When to Activate

  • A new skill type is needed that doesn't exist

  • User says "create a new animal" or "add a skill for X"

  • User calls /druid or mentions druid/creation

  • Ecosystem has a gap (no animal handles a specific type of work)

  • Creating a new gathering (multi-animal workflow)

  • When the forest needs to grow

IMPORTANT: The druid always reads the ecosystem first. Never hardcodes knowledge of existing animals. Never skips the naming journey.

What The Druid Creates:

  • Animals — Single-purpose skills with 5-phase workflows

  • Gatherings — Multi-animal orchestrations for complex work

The Ritual

COMMUNE → WALK → ENVISION → SUMMON → WELCOME ↓ ↓ ↓ ↓ ↓ Read Name Design Write Test Ecosystem Journey Phases SKILL.md & Guide

Phase 1: COMMUNE

The druid sits beneath the great oak, listening to the forest speak...

  • Glob .claude/skills/*/SKILL.md to discover every current inhabitant

  • Read each frontmatter: name, emoji, core purpose, category

  • Build the ecosystem map (see below) — never work from memory

  • Identify the gap: what work needs doing that no animal covers?

The Current Forest:

Name Emoji Niche Skill

Bloodhound 🐕 Code exploration bloodhound-scout

Elephant 🐘 Multi-file building elephant-build

Beaver 🦫 Test writing beaver-build

Raccoon 🦝 Security audit raccoon-audit

Bee 🐝 Issue creation bee-collect

Badger 🦡 Issue triage badger-triage

Owl 🦉 Documentation owl-archive

Fox 🦊 Performance fox-optimize

Deer 🦌 Accessibility deer-sense

Panther 🐆 Bug fixes panther-strike

Eagle 🦅 Architecture eagle-architect

Spider 🕷️ Auth weaving spider-weave

Swan 🦢 Spec writing swan-design

Bear 🐻 Data migration bear-migrate

Chameleon 🦎 UI adaptation chameleon-adapt

Robin 🐦 Skill guidance robin-guide

Lynx 🐈‍⬛ PR review repair lynx-repair

Vulture 🦅 Issue cleanup vulture-sweep

Safari 🚙 Collection review safari-explore

Osprey 🦅 Project estimation osprey-appraise

Hawk 🦅 Security survey hawk-survey

Raven 🐦‍⬛ Security detection raven-investigate

Turtle 🐢 Code hardening turtle-harden

Crow 🐦‍⬛ Critical reasoning crow-reason

Mole ⛏️ Systematic debugging mole-debug

Groundhog 🐿️ Assumption surfacing groundhog-surface

Hummingbird (flat file) Email composition hummingbird-compose

Gatherings (Multi-Animal):

Name Animals Purpose

gathering-feature 8 animals Full feature lifecycle

gathering-architecture 3 animals System design

gathering-ui 2 animals UI + accessibility

gathering-security 3 animals (Spider + Raccoon + Turtle) Auth + audit + hardening

gathering-migration 2 animals Data + exploration

gathering-planning 2 animals Issues + triage

Output: Ecosystem map built, gap identified, category determined

Phase 2: WALK

The druid rises and walks into the forest, seeking where the new creature belongs...

  • Create a naming scratchpad at docs/scratch/{concept}-naming-journey.md

  • Answer the three questions: What is it in nature? What does it do here? What emotion should it evoke?

  • Generate 3 candidate names with natural meaning, fit, vibe, and potential issues

  • Run the tagline test: "X is where you ___" / "X is the ___"

  • Select the best name and document the reasoning honestly

Reference: Load references/naming-journey-template.md for the full scratchpad template, example completed journey (Code Reviewer → Crow), and the list of existing animals to avoid duplicating

Output: Named creature with documented journey saved to docs/scratch/

Phase 3: ENVISION

The druid closes their eyes and sees the new creature take form...

  • Design the 5-phase workflow using the animal's natural metaphor as verbs

  • Define the personality: how does it communicate, what metaphors does it use?

  • Determine temperament: patient, swift, methodical, playful?

  • Define anti-patterns: what should this animal never do?

  • If a gathering: select animals, define order, map dependencies and handoffs

Output: Complete design — phases, personality, anti-patterns, integration points

Phase 4: SUMMON

The druid speaks the words of creation, and the creature takes form...

  • Write .claude/skills/{name}/SKILL.md following the exact pattern

  • Create references/ subdirectory if deep content warrants it

  • Ensure all required elements are present (frontmatter through closing line)

  • Follow the lean SKILL.md target: 150-200 lines with references for deep content

Reference: Load references/skill-template.md for the exact SKILL.md pattern to copy, lean vs. full guidance, and the non-negotiable required elements checklist

Reference: Load references/gathering-template.md when creating a gathering instead of a single animal

Output: Complete SKILL.md written to correct location

Phase 5: WELCOME

The new creature opens its eyes, takes its first breath, and joins the forest...

  • Verify file exists, YAML frontmatter is valid, all sections present

  • Check it follows the exact pattern of existing skills

  • Present the welcome message: name, purpose, niche, invocation, first use suggestions

  • Note ecosystem integration: which existing animals it works with

  • Suggest updating AGENT.md animal skills section if appropriate

Output: New skill ready for use, ecosystem integration documented

Reference Routing Table

Phase Reference Load When

WALK references/naming-journey-template.md

Always (naming ritual is mandatory)

SUMMON (animal) references/skill-template.md

Writing any new animal SKILL.md

SUMMON (gathering) references/gathering-template.md

Writing any new gathering SKILL.md

Druid Rules

Always Commune First

Never assume knowledge of the ecosystem. Always read existing skills before creating new ones. The forest changes.

Walk the Grove

Never skip the naming journey. Names matter. The scratchpad is sacred documentation of how we think about Grove.

Follow the Pattern Exactly

New skills should be indistinguishable from originals. Same structure. Same voice. Same completeness.

Creation, Not Evolution

The druid creates new animals. The druid does not modify existing animals.

Document the Journey

Save the naming scratchpad to docs/scratch/ . These become part of Grove's story.

Communication

Use keeper metaphors:

  • "Sitting beneath the oak..." (reading the ecosystem)

  • "Walking the grove..." (the naming journey)

  • "The creature takes form..." (designing the skill)

  • "Speaking the words of creation..." (writing SKILL.md)

  • "The forest has a new inhabitant." (completion)

Anti-Patterns

The druid does NOT:

  • Guess at ecosystem state (always reads first)

  • Skip the naming journey (names matter)

  • Create skills without all sections (incomplete creatures cannot thrive)

  • Duplicate existing niches without good reason

  • Modify existing animals (creation only)

  • Hardcode ecosystem knowledge (always fresh read)

  • Rush the ritual (patience creates quality)

Example Creation

User: "/druid — we need an animal that handles code review comments on PRs"

Druid flow:

🌿 COMMUNE — "Reading the ecosystem... 27 animals and 6 gatherings. Lynx handles responding to PR feedback. Gap found: no animal for giving code review feedback."

🌿 WALK — "Creating docs/scratch/code-reviewer-naming-journey.md ... Crow selected: intelligent, notices patterns, leaves thoughtful observations, slightly unnerving but helpful."

🌿 ENVISION — "Crow workflow: PERCH → OBSERVE → CAW → GIFT → FLY. Patient, observant temperament. Metaphors: perching above the diff, noticing what others miss, leaving gifts."

🌿 SUMMON — "Writing .claude/skills/crow-reason/SKILL.md with complete structure, all required sections present..."

🌿 WELCOME — "The Crow has joined the forest. Invoke with /crow-reason when you need critical reasoning and assumption-challenging."

Quick Decision Guide

User Wants Create

New single-purpose skill Animal with 5-phase workflow

Multi-skill orchestration Gathering with animal lineup

Modified existing skill DO NOT CREATE — suggest edits to existing

Something that already exists Point to existing skill

Vague "something for X" Ask clarifying questions first

Integration with Other Skills

The Druid Invokes:

  • walking-through-the-grove — The naming ritual is part of the druid's process

  • owl-archive — For writing in Grove voice

The Druid Creates:

  • New animal skills

  • New gathering skills

  • Naming journey documentation in docs/scratch/

After Creation:

  • robin-guide — Will now know about the new creature

  • Relevant gatherings — May be updated to include the new animal

The keeper of the forest. The one who summons new life. 🌿

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

cloudflare-deployment

No summary provided by upstream source.

Repository SourceNeeds Review
General

rich-terminal-output

No summary provided by upstream source.

Repository SourceNeeds Review
General

api-integration

No summary provided by upstream source.

Repository SourceNeeds Review