@silktree/actions

Every silktree operation defined once, as a portable silkweave action. One definition is served as a CLI command, an MCP tool and a REST endpoint - there is no second implementation to drift.

npm install @silktree/actions

What it does

Reading (tree, validate, link), progress (award-xp, unlock-node, respec-node) and authoring (init, add-node, update-node, remove-node, add-branch, update-branch, remove-branch, set-theme). The actions do no I/O beyond the tree file, never touch the process, and throw instead of exiting - the host decides what a failure looks like.

import { silkweave } from '@silkweave/core'
import { silktreeActions } from '@silktree/actions'

const app = silkweave({ actions: [...silktreeActions] })

Most people never import this directly - they use silktree, which picks its adapter from argv and serves exactly this set over all three transports. Import it when you are embedding silktree operations in your own host.

MIT (c) Tobias Strebitzer