bob-workspace-bootstrap
Writes canonical YAML schema source files to based on what the vault already contains (templates + frontmatter census). The BOB Workspace plugin's settings UI then takes those YAML files and regenerates fileClasses, JSON Schemas, and DATAMODEL sections via its built-in `regenerateSchemaOutputs` pipeline. This skill is the upstream half — the plugin owns the downstream half.
Inputs
- vault_path — Absolute path to the user's vault root
- templates_path — Path to existing templates folder; auto-detected if omitted
- vault_path — Absolute path to the user's vault root (minimum route must have run first)
- base_route — Which route's proposal to render (minimum | extend); defaults to minimum
- entities — Explicit list of entity slugs to generate Bases for; if omitted, generates for all YAML source files lacking a matching .base
How you ask
- Bootstrap the minimum BOB Workspace schemas for this existing vault.
- Dry-run the schema proposal without writing any YAML.
- Extend the current setup only for uncovered entity types.
- Diagnose which vault entities are missing from the current workspace UI.
Outputs
- added-yaml-source (yaml)
- bases (base)
- diagnostic-report (markdown)
- merge-report (markdown)
- proposal-report (markdown)
- updated-yaml-source (yaml)
- yaml-source (yaml)
- {vault}/
Levelbeginner
Inputconversation
Outputdocument
Setup[none]
Roles[]