lisa-wiki-add-role
Turn a role definition into two generated artifacts: a documentation page in the wiki and a runnable,
brain-pointed subagent on both runtimes. Running the subagent (invocation, scheduling, Telegram /
agent-team routing, private notebooks) is out of scope — this skill only creates it.
Workflow
- Resolve the role from a
config.staff[] entry (or interview to add one): id, role,
expertise, owns (categories / connectors / skills), sensitivity.
- Doc page: generate
wiki/staff/<id>.md describing the role, its owned domain, and who it
reports to. This page is wiki content and is itself ingestible (the roles connector).
- Subagents (dual-runtime), rendered from the role-agent templates:
- Claude:
.claude/agents/<id>.md.
- Codex:
.codex/agents/<id>.toml (keys name, description, developer_instructions; optional
model, model_reasoning_effort, sandbox_mode).
- Brain-pointed, not baked: the subagent's instructions say "your domain is
wiki/<owned>/;
/query it first, contribute via /ingest; stay in your lane." It points at the live wiki so it
never goes stale. Only its one-line description is synthesized from the wiki at generation time.
- Serialize the description before rendering: derive
roleDescriptionSerialized with
JSON.stringify(roleDescription) or an exact equivalent that emits one JSON string literal on one
physical line. Substitute that serialized literal, including its surrounding quotes, directly for
{{roleDescriptionSerialized}} in both templates. Do not add another layer of quotes. This keeps
colon-space sequences, quotes, backslashes, and runtime newlines exact in both YAML and TOML.
Rules
- v1 instructs lane-keeping but does not enforce per-role write isolation (deferred).
- Setup seeds the starter roster by delegating here per
config.staff[] entry.
Related
lisa-wiki-setup (seeds the roster), lisa-wiki-add-ingest, lisa-wiki-onboard-me.
1---2name: lisa-wiki-add-role-33description: Scaffold a domain-expert…4---56# lisa-wiki-add-role78Turn a role definition into two generated artifacts: a documentation page in the wiki and a runnable,9brain-pointed subagent on both runtimes. **Running the subagent (invocation, scheduling, Telegram /10agent-team routing, private notebooks) is out of scope** — this skill only creates it.1112## Workflow131. **Resolve the role** from a `config.staff[]` entry (or interview to add one): `id`, `role`,14 `expertise`, `owns` (categories / connectors / skills), `sensitivity`.152. **Doc page:** generate `wiki/staff/<id>.md` describing the role, its owned domain, and who it16 reports to. This page is wiki content and is itself ingestible (the `roles` connector).173. **Subagents (dual-runtime), rendered from the role-agent templates:**18 - Claude: `.claude/agents/<id>.md`.19 - Codex: `.codex/agents/<id>.toml` (keys `name`, `description`, `developer_instructions`; optional20 `model`, `model_reasoning_effort`, `sandbox_mode`).214. **Brain-pointed, not baked:** the subagent's instructions say *"your domain is `wiki/<owned>/`;22 `/query` it first, contribute via `/ingest`; stay in your lane."* It points at the live wiki so it23 never goes stale. Only its one-line `description` is synthesized from the wiki at generation time.245. **Serialize the description before rendering:** derive `roleDescriptionSerialized` with25 `JSON.stringify(roleDescription)` or an exact equivalent that emits one JSON string literal on one26 physical line. Substitute that serialized literal, including its surrounding quotes, directly for27 `{{roleDescriptionSerialized}}` in both templates. Do not add another layer of quotes. This keeps28 colon-space sequences, quotes, backslashes, and runtime newlines exact in both YAML and TOML.2930## Rules31- v1 instructs lane-keeping but does not *enforce* per-role write isolation (deferred).32- Setup seeds the starter roster by delegating here per `config.staff[]` entry.3334## Related35`lisa-wiki-setup` (seeds the roster), `lisa-wiki-add-ingest`, `lisa-wiki-onboard-me`.