How do I install the Lisa Wiki Add Role skill?

Run npx skillmds@latest add codyswanngt/lisa-wiki-add-role in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lisa Wiki Add Role safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lisa Wiki Add Role?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lisa Wiki Add Role free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lisa Wiki Add Role?

codyswanngt (@codyswanngt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lisa Wiki Add Role by codyswanngt — Agent Skill

Name: Lisa Wiki Add Role
Author: codyswanngt

Lisa Wiki Add Role

Scaffold a domain-expert "digital staff" role over the wiki — a dual-runtime subagent (Claude + Codex) plus a staff doc page — from a config.staff[] entry. Use when a project wants a role-scoped expert (e.g. Legal, Finance, Sales) whose knowledge is a slice of the wiki. The plugin only SETS UP the subagent; whether it is ever invoked, scheduled, or routed is out of scope.

codyswanngt Updated Sep 17, 2026

File contents

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.

lisa-wiki-setup (seeds the roster), lisa-wiki-add-ingest, lisa-wiki-onboard-me.

---name: lisa-wiki-add-roledescription: Scaffold a domain-expert "digital staff" role over the wiki — a dual-runtime subagent (Claude + Codex) plus a staff doc page — from a config.staff[] entry. Use when a project wants a role-scoped expert (e.g. Legal, Finance, Sales) whose knowledge is a slice of the wiki. The plugin only SETS UP the subagent; whether it is ever invoked, scheduled, or routed is out of scope.---# lisa-wiki-add-roleTurn 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.## Workflow1. **Resolve the role** from a `config.staff[]` entry (or interview to add one): `id`, `role`, `expertise`, `owns` (categories / connectors / skills), `sensitivity`.2. **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).3. **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`).4. **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.5. **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`.

Frequently asked questions