Install

Botanical's product Shiitake extensions: goal, loop and Almanac on the generic extension surface

For a published npm release:

npm install @fungi.computer/shiitake-extensions

pnpm, Yarn and Bun work the same way.

Entrypoints

@fungi.computer/shiitake-extensions/almanac
@fungi.computer/shiitake-extensions/almanac/host
@fungi.computer/shiitake-extensions/question
@fungi.computer/shiitake-extensions/question/client
@fungi.computer/shiitake-extensions/question/host
@fungi.computer/shiitake-extensions/goal
@fungi.computer/shiitake-extensions/goal/host
@fungi.computer/shiitake-extensions/loop
@fungi.computer/shiitake-extensions/loop/host
@fungi.computer/shiitake-extensions/roster
@fungi.computer/shiitake-extensions/roster/conversation-agents
@fungi.computer/shiitake-extensions/plan
@fungi.computer/shiitake-extensions/plan/host
@fungi.computer/shiitake-extensions/skills/source
@fungi.computer/shiitake-extensions/skills
@fungi.computer/shiitake-extensions/home
@fungi.computer/shiitake-extensions/home/host
@fungi.computer/shiitake-extensions/goal/client
@fungi.computer/shiitake-extensions/loop/client
@fungi.computer/shiitake-extensions/plan/client
@fungi.computer/shiitake-extensions/subagents
@fungi.computer/shiitake-extensions/subagents/host
@fungi.computer/shiitake-extensions/subagents/client

What comes with it

Installing @fungi.computer/shiitake-extensions also installs @fungi.computer/almanac, @fungi.computer/cairn, @fungi.computer/knapsack, @fungi.computer/mycelium, @fungi.computer/shiitake, @fungi.computer/watchdog, @fungi.computer/whistle, effect, zod, @fungi.computer/gills.

Set up

This is a package for host and client maintainers. Use its exported subpaths from the configured workspace, not an invented npm install. From the repository root:

pnpm turbo:run run build --filter=@fungi.computer/shiitake-extensions

A host passes botanicalAgentExtensions as its Shiitake extensions option. It still supplies the SQLite owner, runtime wake, model and instruction sources and any tools sandbox. The roster does not supply provider credentials or resource permissions.

A Local host uses botanicalExtensionsWithSkills(source) instead. The read-only SkillSource owns discovery and file access. skillsExtension({source}) uses the prompt, run_tools and commands grants: metadata enters the prompt, while skill.load({name, file?}) returns the body or a supporting file through the existing execute tool. It is a forage operation, not a top-level tool. The human /skills command lists each discovered skill beside its SKILL.md path, plus the reasons other entries were not loaded; choosing one shows its description. Commands run inside a synchronous core transaction, so /skills reads the latest discovery, taken at activation and before each model request. Empty catalogs say that no skills are installed; invalid entries report a redacted cause. Tool discovery summaries stay within Forage’s metadata bounds and mark shortened listings; the prompt still lists every admitted skill. The Hub uses the shared roster without Skills and adds its own scoped Home extension.