RavenClaude

Your control surface, in bounds.

Tune how autonomous your agents are, watch every guardrail an action passes through, and wire the plugin into your tools. Your private Claude Code plugin marketplace — the controls, not the catalog.

Preview — this is a read-only view. Run the served dashboard (rc dashboard or python3 scripts/serve-dashboards.py) to save changes to your repo.

Apply a preset

Sets every category's Local layer at once — your personal default. User and Project layers are untouched.

Design check-ins ⚙ Behavior, not permission

Two independent systems: permission levels gate tool-call approval; behavioral flags (marked ⚙) control whether Claude pauses for design / decision judgment. Setting every permission to Allow changes no behavioral flag.

Separate from the permission levels below. When ON, Claude pauses to confirm structural / architectural / design decisions (Keep / Update / Deny) before implementing — at ANY permission level, including Allow. When OFF (nonstop), Claude proceeds through those decisions using its best judgment and reports them afterward. The permission scale governs whether tool actions need a click; this governs whether design judgment is surfaced first. Honored by the Team Lead, which reads this flag at session start — it is a behavioral commitment, not a machine-enforced lock.

⚖ Command review (the Thing)Early access

When turned on for a category, a command that would normally stop to ask you is instead checked by a panel of AI reviewers before it runs. Each one looks for a different problem: Forseti checks for security risks, Mímir checks the command is correct, and Heimdall watches for hidden instructions trying to trick the system (a “prompt injection”). Thor breaks a tie if they disagree. They vote allow / edit / deny, and a reviewer may rewrite a risky command into a safe one (re-checked before it runs). You are interrupted only when the panel can’t decide; every verdict is logged. It can only resolve the ask cases — it can never unblock the always-denied “danger zone” commands (like force-pushing or wiping a folder). Costs credits on every reviewed command — treat it as a high-stakes guard, not a daily setting. Design: tribunal-review-feature-design.md · concern catalog.

Live for twelve categories: the five shell categories plus network_write (allow / edit / deny); six tool-shape categories (file_edit_*, file_read_*, network_read, mcp_tools) are allow / deny only. Turn each on via its toggle inside the category card below.

Is command review for me? (scope & when it’s optional)

Command review exists to put portable, model-agnostic guardrails on agentic AI that routes across multiple model vendors (e.g. GitHub Copilot CLI using Claude + ChatGPT + Grok), where Claude Code’s native auto permission mode is unavailable (it is Anthropic-API/Claude-only). There it is the only layer giving you a deterministic catastrophe floor, a self-tamper guard, secret-egress prevention, cross-vendor anti-correlated review, and low-touch allow / edit / deny disposition.

If you run only Claude Code, native auto mode may be enough — it adds a hardened classifier plus a non-configurable 3-consecutive / 20-total runaway brake. On pure Claude Code, prefer auto for containment and treat command review as an optional add-on for its domain concerns, audit trail, and yes/no decision-routing. The tribunal earns its credits cost most clearly where auto cannot run.

Per-category review status
file_edit_globaloff
file_edit_projectoff
file_read_globaloff
file_read_projectoff
mcp_toolsoff
network_readoff
network_writeoff
shell_code_execoff
shell_local_mutateoff
shell_package_installoff
shell_readonlyoff
shell_remote_mutateoff
Advanced — seat models, confidence & per-tier panel

Which model fills each seat and how unsure a seat may be before the tie-breaker is convened. Applies wherever a category’s review toggle is on.

Comfort level — which commands you confirm

Reads are never interrupted, and the tribunal always blocks or rewrites dangerous commands — this only changes which safe-looking commands you confirm.

Per-tier panel (advanced)

Override which seats convene and how confident the panel must be at each risk tier. A required seat (set by the tier’s mandatory list) is always checked and can’t be removed.

Medium risk

By default Mímir + Heimdall convene; Heimdall is required.

High risk

By default Forseti + Mímir + Heimdall convene; Heimdall is required.

Extreme risk

By default Forseti + Mímir + Heimdall convene; Forseti + Heimdall are required.

Low risk runs no panel — clean reads pass the deterministic screen for free and are never sent to the tribunal.

Each row below is a type of action Claude might take — for example, shell_code_exec means “run code such as python -c …”. For each one you pick Deny (never), Ask (check with me first), or Allow (go ahead). Start from the ★ Recommended preset above and loosen or tighten from there as you build trust.

Files
Edit files outside this projectWriting to your home directory or system paths.
User
Local
Project
Per-permission overrides (4)0 overridden
Edit(~/**)
Modify a file in your home directory.
Write(~/**)
Create a file in your home directory.
Edit(//**)
Modify a file at filesystem root (e.g. /etc/hosts).
Write(//**)
Create a file at filesystem root.
Edit files in this projectCreating or modifying files inside the current project.
User
Local
Project
Per-permission overrides (3)0 overridden
Edit(**)
Modify an existing file in this project.
Write(**)
Create a new file or overwrite an existing one in this project.
MultiEdit(**)
Apply multiple edits to one file in a single tool call.
Read files outside this projectReading anything outside the current project directory.
User
Local
Project
Per-permission overrides (2)0 overridden
Read(~/**)
Read any file in your home directory.
Read(//**)
Read any file at filesystem root (/etc/, /var/, /opt/, etc.).
Read files in this projectReading source files inside the current project directory.
User
Local
Project
Per-permission overrides (1)0 overridden
Read(**)
Read any file inside this project.
Network
Web readsWebFetch on known documentation domains; HTTP GETs.
User
Local
Project
Per-permission overrides (4)0 overridden
WebFetch
Read a URL via Claude Code's built-in fetcher.
WebSearch
Bash(curl:*)
Make HTTP requests with curl (read by default; --request POST etc. are categorized as network_write).
Bash(wget:*)
Download files from a URL.
Web writesPOST, PUT, DELETE — anything that mutates remote state.
User
Local
Project
Per-permission overrides (11)0 overridden
Bash(curl -X POST:*)
Curl POST — sends data to a remote endpoint.
Bash(curl -X PUT:*)
Curl PUT — replaces a remote resource.
Bash(curl -X DELETE:*)
Curl DELETE — removes a remote resource.
Bash(curl -X PATCH:*)
Curl PATCH — partially updates a remote resource.
Bash(curl --request POST:*)
Curl POST using the long-form --request flag.
Bash(curl --request PUT:*)
Curl PUT using --request.
Bash(curl --request DELETE:*)
Curl DELETE using --request.
Bash(gh api PATCH:*)
Direct GitHub API PATCH call (used for fine-grained PR/issue/repo updates).
Bash(gh api POST:*)
Direct GitHub API POST call.
Bash(gh api DELETE:*)
Direct GitHub API DELETE call.
Bash(gh api PUT:*)
Direct GitHub API PUT call.
Other
MCP server toolsTools provided by connected MCP servers.
User
Local
Project
Shell
Arbitrary code executionpython -c, node -e, bash -c, eval.
User
Local
Project
Per-permission overrides (9)0 overridden
Bash(python:*)
Run a Python script or python -c expression.
Bash(python3:*)
Run Python 3 explicitly.
Bash(node:*)
Run Node.js. With -e, executes arbitrary JavaScript.
Bash(deno:*)
Run Deno (modern TypeScript/JavaScript runtime).
Bash(bash -c:*)
Run a string as a bash script.
Bash(sh -c:*)
POSIX-shell variant of bash -c.
Bash(eval:*)
Evaluate a string as shell code in the current shell.
Bash(ruby:*)
Run a Ruby script or ruby -e expression.
Bash(perl:*)
Run a Perl script or perl -e expression.
Local shell mutationsmkdir, mv, cp, git commit. Changes filesystem locally.
User
Local
Project
Per-permission overrides (17)0 overridden
Bash(mkdir:*)
Create a directory.
Bash(touch:*)
Create an empty file or update its modified time.
Bash(cp:*)
Copy files or directories.
Bash(mv:*)
Move or rename files.
Bash(ln:*)
Create a hard or symbolic link.
Bash(chmod:*)
Change file permissions (rwx bits).
Bash(rm:*)
Remove files.
Bash(git add:*)
Stage changes for the next commit.
Bash(git commit:*)
Record staged changes as a commit.
Bash(git checkout:*)
Switch branches or restore files from a commit.
Bash(git switch:*)
Modern branch-switching command (the safer git checkout).
Bash(git stash:*)
Save uncommitted changes for later (or apply previously stashed changes).
Bash(git restore:*)
Restore working-tree or staged files from a commit.
Bash(git reset:*)
Move HEAD or unstage changes.
Bash(git merge:*)
Merge a branch into the current branch.
Bash(git rebase:*)
Reapply commits on top of another base, rewriting history.
Bash(git tag:*)
Create or list tags.
Package installsnpm install, pip install, apt install, brew install.
User
Local
Project
Per-permission overrides (19)0 overridden
Bash(npm install:*)
Install an npm package (with dependencies).
Bash(npm i:*)
Short form of npm install.
Bash(pnpm install:*)
Install dependencies via pnpm.
Bash(pnpm add:*)
Add a package via pnpm.
Bash(yarn add:*)
Add a package via yarn.
Bash(yarn install:*)
Install dependencies via yarn.
Bash(pip install:*)
Install a Python package via pip.
Bash(pip3 install:*)
Pip 3 variant.
Bash(uv add:*)
Add a dependency via uv (modern Python package manager).
Bash(uv pip install:*)
uv's pip-compatible install.
Bash(brew install:*)
Install a package via Homebrew.
Bash(apt install:*)
Install a package via apt (Debian/Ubuntu).
Bash(apt-get install:*)
Older apt frontend.
Bash(cargo install:*)
Install a Rust binary crate.
Bash(go install:*)
Install a Go binary.
Bash(pipx install:*)
Bash(gem install:*)
Bash(bun add:*)
Bash(bun install:*)
Read-only shell commandsls, cat, git status, grep, find. Cheap shell with no side effects.
User
Local
Project
Per-permission overrides (32)0 overridden
Bash(ls:*)
List directory contents.
Bash(cat:*)
Print a file to stdout.
Bash(head:*)
Show the first N lines of a file.
Bash(tail:*)
Show the last N lines of a file (commonly used to follow logs).
Bash(wc:*)
Count lines, words, or bytes in a file.
Bash(file:*)
Identify a file's type by inspecting its contents.
Bash(stat:*)
Show file metadata (size, permissions, modified time).
Bash(which:*)
Locate a command on PATH.
Bash(type:*)
Show how a shell name is interpreted (alias, function, builtin, file).
Bash(grep:*)
Search files for text patterns.
Bash(rg:*)
Ripgrep — a faster, smarter grep used heavily by Claude.
Bash(find:*)
Walk a directory tree by name, size, or time predicates.
Bash(tree:*)
Print a directory tree as ASCII art.
Bash(echo:*)
Print arguments to stdout.
Bash(pwd)
Print the current working directory.
Bash(git status:*)
Show working-tree status — what's modified, staged, untracked.
Bash(git log:*)
Show commit history.
Bash(git diff:*)
Show changes between working tree, index, or commits.
Bash(git show:*)
Show details for a specific commit, tag, or object.
Bash(git branch:*)
List branches.
Bash(git ls-files:*)
List files tracked by git.
Bash(git remote:*)
List or inspect git remotes.
Bash(git blame:*)
Show line-by-line authorship for a file.
Bash(git stash list)
List stashed changes.
Bash(gh pr view:*)
View a GitHub PR's details.
Bash(gh pr list:*)
List PRs in a repository.
Bash(gh pr diff:*)
Show a PR's diff.
Bash(gh pr checks:*)
Show CI check status for a PR.
Bash(gh issue view:*)
View a GitHub issue's details.
Bash(gh issue list:*)
List issues in a repository.
Bash(gh run view:*)
View a workflow run's status and logs.
Bash(gh run list:*)
List recent workflow runs.
Remote shell mutationsgit push, gh pr create, npm publish — anything that touches a shared system.
User
Local
Project
Per-permission overrides (15)0 overridden
Bash(git push:*)
Send commits to a remote (typically GitHub).
Bash(git fetch:*)
Download refs from a remote without merging.
Bash(git pull:*)
Fetch and merge from a remote.
Bash(gh pr create:*)
Open a new GitHub PR.
Bash(gh pr edit:*)
Edit a PR's title, body, labels, or reviewers.
Bash(gh pr comment:*)
Post a comment on a PR.
Bash(gh pr merge:*)
Merge a PR.
Bash(gh pr close:*)
Close a PR without merging.
Bash(gh issue create:*)
Open a new GitHub issue.
Bash(gh issue edit:*)
Edit an issue's title, body, labels, or assignees.
Bash(gh issue close:*)
Close an issue.
Bash(gh issue comment:*)
Post a comment on an issue.
Bash(npm publish:*)
Publish a package to the npm registry.
Bash(pnpm publish:*)
Publish a package via pnpm.
Bash(yarn publish:*)
Publish a package via yarn.

Danger Zone

The following patterns are ALWAYS denied, regardless of category levels. Unblock individual rules at your own risk.

These are preventive guardrails, not a malware scanner. They block the common routes malware and damage travel through — running remote scripts (curl | sh), gaining root (sudo), wiping files, and reading secrets — and they stop the command before it runs.

What they don’t do: inspect a file’s contents — so they cannot catch malware hidden inside something you explicitly approve. Treat the floor as a seatbelt, not a reason to skip reviewing what Claude produced.

The floor and the hooks behind it (guard-destructive blocks destructive shell commands, enforce-layout blocks off-pattern file writes) are maintained in the RavenClaude marketplace and periodically re-reviewed by the Researcher meta-skill, which adds new dangerous patterns here as they emerge. Learn more: Claude Code permissions · how hooks work · this plugin’s security rules.

Bash(rm -rf:*)

Recursive force-delete — removes a directory tree without confirmation.

Bash(git push --force:*)

Force-push, overwriting remote branch history.

Bash(git push -f:*)

Short flag for force-push.

Bash(git reset --hard:*)

Discard working-tree and staged changes irreversibly.

Bash(git clean -fd:*)

Force-remove untracked files and directories.

Bash(npm publish:*)

Publish a package to the npm registry.

Bash(pnpm publish:*)

Publish a package via pnpm.

Bash(yarn publish:*)

Publish a package via yarn.

Bash(cargo publish:*)

Publish a Rust crate to crates.io.

Bash(curl * | sh)

Pipe downloaded content directly into a shell — the 'curl pipe sh' install pattern.

Bash(curl * | bash)

Variant of curl-pipe-sh.

Bash(wget * | sh)

wget variant of curl-pipe-sh.

Bash(wget * | bash)

wget variant of curl-pipe-bash.

Bash(sudo:*)

Run a command as the superuser (root) — full administrative privileges over the machine.

Read(.env)

Read an .env file (environment-variable definitions).

Read(.env.*)

Read .env.local, .env.production, .env.staging, etc.

Read(**/*.pem)

Read a PEM-encoded private key (TLS certs, SSH keys).

Read(**/*.key)

Read any .key file (generic private-key extension).

Read(**/credentials*)

Read any file literally named 'credentials' (AWS, GCP, etc.).

Read(**/secrets*)

Read any file literally named 'secrets' (generic catch-all).

Guardrail pipeline

Everything an AI agent passes through, top to bottom. Each box shows whether it's on right now, what it does (in plain words), the step-by-step of how it works, and the knobs you can turn. Changes save to your .ravenclaude/comfort-posture.yaml.

The two middle checkpoints repeat for every command and file edit — that's the ↺ loop. Open “How it works, step by step” on any box to see exactly what it checks and what happens if it trips. Badges: Always on can't be turned off · Advisory only nudges, never blocks · On / Off depends on your settings (filled in live below).

When a session startsSessionStart

Right when the robot wakes up, it loads your settings and reminds itself what it's allowed to do.

Re-apply settingsAlways on

Loads your saved safety settings so they're on from the very first step.

How it works, step by step
  1. Reads your saved settings file (.ravenclaude/comfort-posture.yaml).
  2. Turns each rule into a real Claude Code permission.
  3. Writes them into .claude/settings.json so they're active right away.

If it trips: If there's no settings file, it does nothing — no harm done.

Where it’s set: Change these in the Settings tab; the Save button writes the file.

Safe starting modeAlways on

Picks a safe mode to start the session in.

How it works, step by step
  1. Checks what mode the session is starting in.
  2. If nothing was chosen, picks a safe default.

If it trips: Only steps in when no mode was set — otherwise it leaves your choice alone.

Where it’s set: Built in — nothing to tune.

Capability checkAlways on

Reminds the robot what tools and access it already has, so it doesn't say “I can't” by mistake.

How it works, step by step
  1. Looks at what tools, logins, and permissions are available.
  2. Writes a short summary into the session so the robot knows what it can do.
  3. Adds a line about recent guardrail activity (how many things were blocked, when settings last changed).

If it trips: Read-only — it never changes anything, it only informs.

Where it’s set: Built in.

Before the robot runs a command or edits a filePreToolUse

This is the busiest checkpoint. Every command and every file edit goes through these in order before it's allowed to happen.

Danger guardAlways on

Stops really dangerous commands (like deleting everything) before they can run.

How it works, step by step
  1. Looks at the command about to run.
  2. Matches it against a list of never-allowed patterns (delete everything, force-push, wipe history).
  3. Blocks it before it can run if it matches.

If it trips: Blocks the command and writes a note in the alert log (Perimeter alerts tab).

Where it’s set: Built-in safety floor — always on, can't be turned off.

Command review (the Thing)

A panel of robot reviewers votes yes / no / fix on a command before it runs. You choose how strict it is.

How it works, step by step
  1. Runs quick free checks first, so the obvious-dangerous ones are caught with no waiting.
  2. If the command is risky enough, a panel of reviewers reads it.
  3. They vote: allow, fix (rewrite it to be safe), or block.
  4. Low-risk reads skip the panel completely — no waiting.

If it trips: A block stops the command; a fix rewrites it; anything safe just runs.

Where it’s set: Turn it on (and on/off per command type) and tune the panel in Settings — quick toggles below.

Turn individual command types on/off, and tune the reviewer panel, in the Settings tab.

Runaway brake

Counts the robot's steps. If it loops forever or takes way too many steps, it pauses so it can't run away.

How it works, step by step
  1. Counts every tool the robot uses this session.
  2. Watches for the same command repeated over and over.
  3. Pauses if it loops, or if it passes your step limit.

If it trips: Pauses the robot so it can't run away with your time or money.

Where it’s set: Turn the brake off, or set the two limits, in the boxes below.

Parallel workers

Lets the robot split a job across several helpers at once — and caps how many run together.

How it works, step by step
  1. Watches when the robot wants to fan work out to helpers (subagents / worktrees).
  2. If parallel workers are allowed, lets several run side by side.
  3. Caps how many run at once to your limit.

If it trips: When off, helpers run one at a time; when on, up to your worker limit run together.

Where it’s set: Turn parallel workers on and set the most-at-once limit in the boxes below.

When on, fan-out work (subagents / worktrees) may run in parallel. Tick “No limit” for unlimited workers, or set a cap. Off keeps the work sequential.

Folder & task limits

Makes sure new files go in the right folders, and that the robot only touches the files this task is allowed to.

How it works, step by step
  1. Checks where a new file is about to be written.
  2. Compares it to your allowed-folders list (.repo-layout.json).
  3. If a task-file list is set, checks the file is part of this task (.ravenclaude/task-scope.json).

If it trips: Blocks the write and suggests the correct folder.

Where it’s set: Edit the two file lists in the boxes below.

Allowed folders .repo-layout.json
This task’s files .ravenclaude/task-scope.json
Decision routing⚙ Behavior, not permission

When the robot would ask you a yes/no question, a panel answers the easy ones so you're not interrupted.

How it works, step by step
  1. Notices when the robot is about to ask you a yes/no question.
  2. Sends the simple, low-risk ones to a small panel.
  3. Big or risky questions always come to you.

If it trips: In binding mode the panel answers the easy ones; risky ones still reach you.

Where it’s set: Pick off / advisory / binding in the box below.

Website guardNot set up

Lets you pick which websites the robot may open without asking, and which are always off-limits.

How it works, step by step
  1. Before the robot fetches a web page, checks your allow / deny lists.
  2. An allowed site opens with no prompt; a denied site is blocked.
  3. A site on neither list falls through to the normal once / this-session / permanently / deny prompt.

If it trips: Blocks a denied site; otherwise it asks you the first time, exactly like today.

Where it’s set: Set up allow / deny lists on the Web access page. “Not configured yet” is fine — sites just fall through to the normal ask prompt.

Not configured yet — every website falls through to the normal ask prompt (allow once / this session / permanently / deny). The guard never blocks web access until you set up lists, so this is a safe default.

Set up allow / deny lists on the Web access page — saved to .ravenclaude/web-access.yaml, enforced by guard-web-access.sh. Nothing to configure here; this is a shortcut to that editor.

Claude orchestrator⚙ Behavior, not permission

Routes team-lead planning to Claude when your host CLI isn't Claude Code. Inert under Claude Code.

How it works, step by step
  1. Checks whether the host is already Claude Code — if so, does nothing.
  2. Reads the orchestrator knob from .ravenclaude/comfort-posture.yaml.
  3. decide: sends the task to Claude and gets back a JSON plan the host CLI executes.
  4. full: sends the full task to Claude and gets back artifact content the host writes.

If it trips: If Claude is unavailable or auth fails, falls back to host orchestration automatically — never blocks.

Where it’s set: Pick off / decide / full below. Inert under Claude Code (host already IS Claude).

[host-only — inert under Claude Code] Active only when your CLI is not Claude Code (e.g. GitHub Copilot routing GPT/Grok). Under Claude Code the host already is Claude — this knob is a no-op. off — zero cost, host orchestrates as always. decide — Claude returns a JSON dispatch plan; host runs the agents (brain / hands split; lower cost). full — one Claude call reasons through the task and returns artifact content; host writes the files (guaranteed intent; highest cost, bounded).

Right after a command runs or a file is savedPostToolUse

After something happens, these tidy up and double-check the work.

Auto-tidyAlways on

Tidies up a file's formatting right after it's saved.

How it works, step by step
  1. Runs right after a file is saved.
  2. Runs the formatter for that kind of file.
  3. Saves the tidied version.

If it trips: Skips files it doesn't have a formatter for — never blocks.

Where it’s set: Built in.

Copy guardAlways on

Stops the robot from making endless copies of itself.

How it works, step by step
  1. Watches for the robot launching copies of itself.
  2. Warns if those copies nest too deep.

If it trips: Warns (it doesn't hard-block) so you can step in.

Where it’s set: Built in.

Fact checkAdvisory

Reminds the robot to say where a fact came from when it writes one into a document.

How it works, step by step
  1. Reads facts written into knowledge / docs files.
  2. Checks each big claim says where it came from.
  3. Nudges if a source is missing.

If it trips: Advisory only — it nudges, it never blocks.

Where it’s set: No knob — fires whenever a comfort-posture exists.

Do-it-yourself nudgeAdvisory

Reminds the robot to run a check itself instead of telling you to go look, when it already has the access.

How it works, step by step
  1. Reads knowledge / docs files the robot writes.
  2. Looks for “open the portal / check it yourself / verify manually” phrasing.
  3. Nudges the robot to run the check itself when it already holds the access.

If it trips: Advisory only — it nudges, it never blocks.

Where it’s set: No knob — fires whenever a comfort-posture exists.

When the robot thinks it's doneStop

Before the robot is allowed to stop, it proves the work is really finished.

Done check

Before the robot says “done,” it runs your tests. If they fail, it keeps working.

How it works, step by step
  1. Fires when the robot tries to stop.
  2. Runs your test / build command.
  3. If it fails, the robot keeps working instead of stopping.

If it trips: Blocks the stop until tests pass (up to a retry limit, then it lets the robot stop with a warning).

Where it’s set: Set your test command and the retry limit in the boxes below.

Leave the command empty to turn the done-check off.

Test reminderAdvisory

A gentle nudge to run the tests when there's no done-check set up.

How it works, step by step
  1. Fires on stop when no done-check is set.
  2. Prints a friendly reminder to run the tests.

If it trips: Advisory only — just a nudge.

Where it’s set: Becomes unnecessary once you set a done-check above.

Concern reliability

Per-concern false-positive signals from the command-review Sága log. Stripped means the orchestrator deterministically caught a cite the seat shouldn’t have made (e.g. xc.outside-project-tree on a file the path-classifier already proved is in-tree). Heimdall-disagreed means another seat cited the concern and voted deny while Heimdall (injection-only) voted allow — a behavioural false-positive signal. A high FP ratio is the queue of concerns worth tuning. Read live from .ravenclaude/runs/thing/ via /__concern-stats; static hosts show an empty state.

Loading…

Install RavenClaude — GitHub Copilot CLI

Follow these steps in order. Every command has a Copy button — you don’t need to type anything. Each step tells you what to expect after you run it. Using Claude Code instead? See the Claude Code page.

What is this?

RavenClaude is a kit of AI agents (architect, coder, reviewer, and friends) you can use inside coding tools. GitHub Copilot CLI is GitHub’s command-line chatbot — you type copilot in a terminal and it answers like a chat. This page shows how to plug the RavenClaude kit into Copilot so the agents are there when you chat.

Before you start — what you need

Run each of these three checks. They print a version number if you have the thing already.

a. Node.js 22 or higher
node --version
b. GitHub Copilot CLI
copilot --version
c. GitHub CLI (for cloning the RavenClaude repo)
gh auth status

Missing the Copilot CLI? Install it:

Install GitHub Copilot CLI
npm install -g @github/copilot

Not signed into Copilot? Run copilot once. When it opens, type /login and follow the prompts — you sign in with your GitHub account.

Step 1: Get RavenClaude onto your machine

RavenClaude lives in a GitHub repo. You clone (download) it once, into your home folder. The squiggly line ~ means “your home folder” — on a Mac that’s /Users/yourname, on Linux it’s /home/yourname, and in a Codespace it’s /home/codespace.

Clone the RavenClaude repo (one time only)
gh repo clone mcorbett51090/RavenClaude ~/RavenClaude

After this: You have a folder at ~/RavenClaude with all the agent kits. Every command below points back to this folder.

If the clone fails with “permission denied”: the repo is private — make sure you ran gh auth login first and signed in with your GitHub account, then try the clone again.

Step 2: Pick how you’re working

Two situations. Pick the one that matches you. (Click to expand.)

Situation A: I’m using a brand-new GitHub Codespace

A Codespace is a cloud computer GitHub gives you for a repo — it opens in your browser and looks like VS Code. If that’s you, follow these four steps to make RavenClaude set itself up automatically every time the Codespace opens.

  1. Inside your Codespace’s terminal, run this once. It copies two setup files into your project’s .devcontainer/ folder.
    bash ~/RavenClaude/scripts/ravenclaude init-codespace --project .
  2. Wire up THIS session right now (so you don’t have to rebuild to test). Pick the plugins you want here — see Step 3 for what each one does.
    Just the base kit (core only)
    bash ~/RavenClaude/scripts/ravenclaude setup --project .
    Core + power-platform (example: a Microsoft Power Platform project)
    bash ~/RavenClaude/scripts/ravenclaude setup --project . --with-plugin power-platform
  3. Reload your shell so the new rc command works.
    source ~/.bashrc
  4. Commit and push the .devcontainer/ files so future Codespace builds are fully automatic.
    git add .devcontainer && git commit -m "Add RavenClaude Codespace auto-setup" && git push

After this: Every time you (or anyone on your team) opens a Codespace for this repo, RavenClaude sets itself up automatically. The dashboard URL opens by itself in a new browser tab. You just type rc to launch Copilot.

Situation B: I’m on my own computer (no Codespace)

Three steps. Pretty similar to Situation A, just without the Codespace auto-setup file.

  1. Go to your project folder in a terminal. Replace the path with your actual folder.
    cd /path/to/your/project
  2. Wire RavenClaude into this project. Pick the plugins you want — see Step 3 for what each one does.
    Just the base kit (core only)
    bash ~/RavenClaude/scripts/ravenclaude setup --project .
    Core + power-platform
    bash ~/RavenClaude/scripts/ravenclaude setup --project . --with-plugin power-platform
  3. Reload your shell so the new rc command works.
    If you use bash
    source ~/.bashrc
    If you use zsh (most Macs)
    source ~/.zshrc

After this: RavenClaude is wired into THIS project on this computer. You type rc in a terminal (from this project’s folder) to launch Copilot.

Step 3: Pick your plugins

RavenClaude is split into plugins — separate kits for different jobs. Step 2 above showed how to pick them with the --with-plugin flag. Add the flag once per plugin — for example: --with-plugin power-platform --with-plugin finance.

What’s in each plugin?

  • ravenclaude-coreAlways on. The base kit of generalist agents (architect, coder, reviewer, etc.) and the team-lead dispatch pattern. You never have to ask for this one.
  • power-platform — Microsoft Power Platform specialists (Dataverse, Power Automate, Power Apps). Use this for any Microsoft project.
  • finance — Finance-domain specialists for accounting workflows.
  • web-design — Web design specialists (UX, visual, accessibility, performance).
  • data-platform — Data engineering, ELT, dashboards, multi-tenant.
  • and 12 others — see the Learn tab for the full list.

Already installed and want to add a plugin later? Re-run the setup command with the new plugin name. It’s safe to run again — it just adds the new skills alongside what’s already there.

Add power-platform to an already-installed project
bash ~/RavenClaude/scripts/ravenclaude setup --project . --with-plugin power-platform

Then, inside your running Copilot session:

Pick up the new skills without restarting Copilot
/skills reload

Step 4: Launch Copilot with RavenClaude

One word from any terminal:

Launch Copilot with all your wired-up agents
rc

What rc does: It pulls the latest RavenClaude (so you always have the newest version), then launches Copilot with the agents and skills loaded. (rc is short for “ravenclaude” — ravenclaude setup added it to your shell’s ~/.bashrc or ~/.zshrc.)

Updating later

rc auto-updates every time you launch — so usually you don’t do anything extra. A few common variants:

1. Update and relaunch in one step — the everyday move:

Update + launch (the rc alias)
rc

2. Update without launching Copilot — e.g. from a scratch shell or a script:

Update only (no launch)
bash ~/RavenClaude/scripts/ravenclaude update

Then, inside your running Copilot session, pick up changed skills:

Inside Copilot
/skills reload

3. Verify what’s wired in this project — lists the version, the wired skills, the hook adapter, and the MCP entry:

Status check
bash ~/RavenClaude/scripts/ravenclaude status --project .

4. Relaunch from a running Copilot session — needed when you changed a hook or an MCP server (skills alone don’t need this; /skills reload is enough). Press Ctrl+C twice to quit, then:

Quit + relaunch
rc

Using Claude Code on the same machine? ravenclaude update only refreshes the Copilot side — it does not touch Claude Code’s plugin cache at ~/.claude/plugins/cache/. To update that side too, run /plugin marketplace update ravenclaude and /reload-plugins inside Claude Code. See the Bifröst cache-verification steps.

When do I need to rebuild my Codespace?

A rebuild tears down the Codespace and creates a new one. It’s slow — a few minutes. Most things don’t need one.

What you didRebuild?What instead
Added or changed files in .devcontainer/ Yes The .devcontainer/ files only take effect when the Codespace is built. Command Palette → “Codespaces: Rebuild Container”.
Ran ravenclaude update (or rc) No Skills read live from disk. Inside Copilot, type /skills reload.
Added a new plugin with --with-plugin No Inside Copilot, type /skills reload (or quit and re-run rc).
Changed settings on the dashboard No Dashboard’s Save & apply updates .claude/settings.json immediately. The engine reads it on each command.
Changed hooks or MCP servers No, but relaunch Hooks and MCP servers load when Copilot starts. Press Ctrl+C twice to quit, then type rc again.
Just opened the Codespace after pausing it No That’s a resume, not a build. The dashboard auto-launch fires on resume too.

Common problems

“rc: command not found”

Your shell hasn’t loaded the new rc alias yet. Reload it:

source ~/.bashrc

If you use zsh (most Macs), use source ~/.zshrc instead. Or just close and reopen your terminal.

“gh: command not found” during the clone step

GitHub CLI isn’t installed. In a Codespace, it’s already there — if you see this, you’re probably on a local computer. Install it:

  • Mac: brew install gh
  • Ubuntu/Debian: see github.com/cli/cli
  • Windows: winget install --id GitHub.cli

After installing: gh auth login.

Copilot says it doesn’t know about an agent

Either Copilot was launched without --plugin-dir (the rc alias handles this for you), or you need to reload skills. Inside Copilot, type /skills reload. If that doesn’t work, press Ctrl+C twice to quit Copilot, then type rc again.

Dashboard didn’t open automatically in my Codespace

Open the Ports panel in VS Code (View menu → Ports), find port 8000 labeled “RavenClaude dashboard”, right-click → Open in Browser. Don’t use the VS Code Simple Browser — it blocks parts of the dashboard.

I want to check what’s wired in my project
bash ~/RavenClaude/scripts/ravenclaude status --project .

Prints what’s in .claude/skills, .github/hooks, and ~/.copilot/mcp-config.json.

Under the hood: RavenClaude reads everything live from disk. The plugin loads via --plugin-dir, skills from .claude/skills, hooks from .github/hooks, MCP from ~/.copilot/mcp-config.json. So ravenclaude update is just a git pull on the marketplace clone — no re-install, ever. There’s no plugin cache to invalidate, no version registry to update. The hooks land at repo level (not plugin level) as a workaround for copilot-cli#2540 — plugin-level preToolUse hooks don’t fire in Copilot today.

Commands

Copy any of these and run them in your checkout. They work everywhere, even when this page is opened from GitHub Pages or a file.

Set up (one-shot: install + balanced posture + rc alias)
bash scripts/ravenclaude setup
Install (one-time wiring only)
bash scripts/ravenclaude install
Launch Copilot with the plugin
copilot --plugin-dir plugins/ravenclaude-core/copilot
Update (git pull + re-sync, then /skills reload in Copilot)
bash scripts/ravenclaude update
Status (show what is wired)
bash scripts/ravenclaude status
One-command alias (update, then launch)
alias rc='bash scripts/ravenclaude update && copilot --plugin-dir plugins/ravenclaude-core/copilot'

One-click run

Run python3 scripts/serve-dashboards.py for one-click, or use the copy buttons above.

Bridge status

Click Status to check which pieces (skills, hooks, MCP, package) are wired. Needs the local server.

Preview a command's review

Type any shell command to see how command review (the Thing) would handle it — which category it lands in, its risk tier, which reviewers weigh in, and whether it would be allowed, auto-fixed, surfaced to you, or denied. It runs the real review engine — no command is run and no AI is called — so it matches what happens for real.

Web access — allow & deny lists

Domains the agent may fetch without asking (allow) or never (deny). Saves to .ravenclaude/web-access.yaml via the dashboard server; the guard-web-access.sh hook enforces it for Claude when the plugin is installed, and any cloned CLI tool can read the same plain-YAML file. On the static/published copy edits stay in your browser — use Download. One domain per line; a rule matches the domain and its subdomains (e.g. github.com also allows api.github.com). Unlisted domains fall through to the agent's once / this-session / permanently / deny prompt.

Allow auto-approved

Deny always blocked

⚖ Review log

Loading review log…

📜 Run feed

Run history from .ravenclaude/runs/ — newest first. Each card is one multi-step run (its summary, structured-result status, and event count). Command-review verdicts live in the Review log tab.

Sleipnir’s stables

Loading activity…

Perimeter alerts

Perimeter alerts — a read-only mirror of what your guardrails already flagged. Heimdall never blocks anything itself; it shows the most recent hook denials, CI runs, and version drift so you can answer “what tripped, when, and why?” in one glance.

Recent hook denials

When did a guardrail say “no”? (red = irrecoverable, amber = blocked, grey = advisory)

Loading hook events…

Recent CI runs

The last few GitHub Actions runs on this marketplace.

Loading CI status…

Plugin version drift

Does each plugin’s version match the marketplace catalog?

Active alarms (Gjallarhorn)

The highest-severity signal currently flagged.

Debt watch (Níðhöggr)

Slow-rotting bits at the foundations — low-noise marketplace maintenance signals.

Loading debt signals…

Knowledge health (Idunn)

How current is the marketplace’s knowledge layer? Click a bucket to drill into the files in it.

Loading knowledge health…

Security log

Posture & security event log (Víðarr’s shoe) — a read-only chronological record of how your security posture changed and which guardrails blocked an action. Víðarr’s shoe was assembled from leather scraps across all of time; this log is the same — small events accumulating against the day someone needs to know exactly what happened.

Loading security log…

Lineage

Plugin lineage (The Norns) for ravenclaude-core — past, present, and proposed future, drawn live from git history, surfaced scenarios, and the manifest.

Urðr (Lessons & history) · Verðandi (Current) · Skuld (Proposed)

Urðr Lessons & history

Loading…

Verðandi Current

Loading…

Skuld Proposed

Loading…

Session

Claude Code session state for this project (Mímir’s well) — drawn live from ~/.claude/ and .claude/settings.json. Read-only; in-process-only fields render with an explainer, never a dash.

Settings

Loading…

Current session

Loading…

Activity summary

Loading…

Recent project sessions

Loading…

In-process only

Loading…

Streams

Agentic Work-Streams for this project — named logical workstreams under .ravenclaude/streams/, drawn live from the served dashboard. Read-only; the per-stream history shows derived labels only (never your prompt text). Switch the active stream with /stream set <id> or rc streams set-active <id>.

Streams

Loading…

Active stream — recent activity (derived)

Loading…

Install & Update — Claude Code

Bifröst is the rainbow bridge between the marketplace and your Claude Code project. Follow these four steps to install a plugin, then see Updating an installed plugin below. Each step is copy-paste only — Bifröst guides you, but you cross the bridge yourself. Nothing here runs a command for you; you run each in your Claude Code session and paste the result back so Bifröst can light the next step. Using GitHub Copilot CLI instead? See the Copilot CLI page.

  1. Not started

    Step 1. Add the marketplace

    Point Claude Code at the RavenClaude marketplace (a URL or a local path to a clone).

    /plugin marketplace add <url-or-path>

    Paste what Claude Code printed (e.g. “marketplace added” or an error).

  2. Not started

    Step 2. Install the plugin

    Install a plugin from the marketplace into your project. The name must match an entry in marketplace.json’s plugins[].

    /plugin install <plugin-name>@ravenclaude

    Paste the install result.

  3. Not started

    Step 3. Reload plugins

    Make Claude Code pick up the newly-installed plugin.

    /reload-plugins

    Confirm you can see the plugin in your /plugin menu, then paste anything it printed (or type “I see it”).

  4. Not started

    Step 4. Verify the bridge

    Confirm the project is agent-ready with the plugin wired in.

    /init-agent-ready --check

    Paste the check output — green means the bridge holds.

If the bridge is down…

Updating an installed plugin

Once a plugin is installed you don’t re-run the wizard to update it — just refresh the marketplace catalog and reload. Run both in your Claude Code session:

1. Pull the latest marketplace catalog
/plugin marketplace update ravenclaude
2. Apply it in your session
/reload-plugins

Plugin versions bump on every user-visible change, so the catalog update is what surfaces a new version. Re-run /init-agent-ready --check (step 4) afterward to confirm the bridge still holds.

Verify the cache actually advanced

Claude Code reads installed plugins from ~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/, indexed by ~/.claude/plugins/installed_plugins.json. If a reload doesn’t seem to take, check the cache directly — the most common failure mode is a stale entry. Run these in a shell (not in Claude Code):

a. Cached version for ravenclaude-core
jq -r '.plugins["ravenclaude-core@ravenclaude"][0].version' ~/.claude/plugins/installed_plugins.json
b. Versions on disk in the cache
ls ~/.claude/plugins/cache/ravenclaude/ravenclaude-core/

The cached version should match the marketplace’s current version in plugins/ravenclaude-core/.claude-plugin/plugin.json. If they differ, re-run the two commands above (catalog update + reload). If they still differ, fully restart Claude Code — the cache lookup is read once at startup and the running session won’t pick up a newly-extracted version mid-flight.

About this dashboard

Your control panel for working with Claude Code under RavenClaude. Set what Claude may do on its own and see the safety checks every command passes through (Set up); review past decisions, live runs, perimeter alerts, and your security log (Look back); read plain-English explainers, command playbooks, and decision-tree guidance (Learn); and add plugins or wire RavenClaude into your tools (Install & help). The Settings page is where you tune permissions — Deny (never), Ask (check first), or Allow (go ahead) per action type, across three layers (User, Local, Project) where the strictest wins; it saves to .ravenclaude/comfort-posture.yaml and the /set-posture skill turns that into Claude Code's own .claude/settings.json rules.

ravenclaude-core · static dashboard, no backend. Your edits stay in your browser until you click Download.

How the pages are organized

Pick a category in the top bar, then a page within it.

  • Set up — Overview, Settings (what Claude may do), Pipeline (the safety checks every command passes through), and Preview a review.
  • Look back — Review log, Run feed, Perimeter alerts, Security log, and Lineage.
  • Learn — plain-English explainers, ready-to-run command playbooks, and decision-tree guidance.
  • Install & help — two install & update guides, one per tool: Claude Code (the Bifröst bridge) and GitHub Copilot CLI — plus this page.

accessibility-engineering

Configure accessibility-engineering's variables here — they save to .ravenclaude/plugins/accessibility-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

accounting-bookkeeping

Configure accounting-bookkeeping's variables here — they save to .ravenclaude/plugins/accounting-bookkeeping.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ai-coding-model-guidance

Configure ai-coding-model-guidance's variables here — they save to .ravenclaude/plugins/ai-coding-model-guidance.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ai-rag-engineering

Configure ai-rag-engineering's variables here — they save to .ravenclaude/plugins/ai-rag-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ai-red-teaming

Configure ai-red-teaming's variables here — they save to .ravenclaude/plugins/ai-red-teaming.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

analytics-engineering

Configure analytics-engineering's variables here — they save to .ravenclaude/plugins/analytics-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

api-engineering

Configure api-engineering's variables here — they save to .ravenclaude/plugins/api-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

applied-statistics

Configure applied-statistics's variables here — they save to .ravenclaude/plugins/applied-statistics.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

The default α for hypothesis tests; document deviations.

Default family-wise / FDR correction when running many tests.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ar-vr-xr-engineering

Configure ar-vr-xr-engineering's variables here — they save to .ravenclaude/plugins/ar-vr-xr-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

architecture-aec

Configure architecture-aec's variables here — they save to .ravenclaude/plugins/architecture-aec.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

audio-dsp-engineering

Configure audio-dsp-engineering's variables here — they save to .ravenclaude/plugins/audio-dsp-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

auth-identity

Configure auth-identity's variables here — they save to .ravenclaude/plugins/auth-identity.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

auto-repair-shop-operations

Configure auto-repair-shop-operations's variables here — they save to .ravenclaude/plugins/auto-repair-shop-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

automotive-dealership

Configure automotive-dealership's variables here — they save to .ravenclaude/plugins/automotive-dealership.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

aws-cloud

Configure aws-cloud's variables here — they save to .ravenclaude/plugins/aws-cloud.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

azure-cloud

Configure azure-cloud's variables here — they save to .ravenclaude/plugins/azure-cloud.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

backend-engineering

Configure backend-engineering's variables here — they save to .ravenclaude/plugins/backend-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

behavioral-health-practice

Configure behavioral-health-practice's variables here — they save to .ravenclaude/plugins/behavioral-health-practice.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

bioinformatics-engineering

Configure bioinformatics-engineering's variables here — they save to .ravenclaude/plugins/bioinformatics-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

blockchain-web3-engineering

Configure blockchain-web3-engineering's variables here — they save to .ravenclaude/plugins/blockchain-web3-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

brand-identity-studio

Configure brand-identity-studio's variables here — they save to .ravenclaude/plugins/brand-identity-studio.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

browser-extension-engineering

Configure browser-extension-engineering's variables here — they save to .ravenclaude/plugins/browser-extension-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

cannabis-operations

Configure cannabis-operations's variables here — they save to .ravenclaude/plugins/cannabis-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

chaos-engineering-resilience

Configure chaos-engineering-resilience's variables here — they save to .ravenclaude/plugins/chaos-engineering-resilience.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

childcare-early-education

Configure childcare-early-education's variables here — they save to .ravenclaude/plugins/childcare-early-education.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

chiropractic-practice

Configure chiropractic-practice's variables here — they save to .ravenclaude/plugins/chiropractic-practice.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

claude-app-engineering

Configure claude-app-engineering's variables here — they save to .ravenclaude/plugins/claude-app-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

House opinion #3 — right-size by cost-per-resolved-task; the everyday default tier.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

cli-tooling-engineering

Configure cli-tooling-engineering's variables here — they save to .ravenclaude/plugins/cli-tooling-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

clinical-trials

Configure clinical-trials's variables here — they save to .ravenclaude/plugins/clinical-trials.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

cloud-native-kubernetes

Configure cloud-native-kubernetes's variables here — they save to .ravenclaude/plugins/cloud-native-kubernetes.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

commercial-real-estate

Configure commercial-real-estate's variables here — they save to .ravenclaude/plugins/commercial-real-estate.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

computer-vision-engineering

Configure computer-vision-engineering's variables here — they save to .ravenclaude/plugins/computer-vision-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

construction-general-contractor

Configure construction-general-contractor's variables here — they save to .ravenclaude/plugins/construction-general-contractor.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

conversational-ai-voice-engineering

Configure conversational-ai-voice-engineering's variables here — they save to .ravenclaude/plugins/conversational-ai-voice-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

craft-beverage-operations

Configure craft-beverage-operations's variables here — they save to .ravenclaude/plugins/craft-beverage-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

creator-economy-operations

Configure creator-economy-operations's variables here — they save to .ravenclaude/plugins/creator-economy-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

customer-success-analytics

Configure customer-success-analytics's variables here — they save to .ravenclaude/plugins/customer-success-analytics.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

customer-support-cx-operations

Configure customer-support-cx-operations's variables here — they save to .ravenclaude/plugins/customer-support-cx-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

cybersecurity-grc

Configure cybersecurity-grc's variables here — they save to .ravenclaude/plugins/cybersecurity-grc.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

data-governance-privacy

Configure data-governance-privacy's variables here — they save to .ravenclaude/plugins/data-governance-privacy.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

data-orchestration

Configure data-orchestration's variables here — they save to .ravenclaude/plugins/data-orchestration.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

data-platform

Configure data-platform's variables here — they save to .ravenclaude/plugins/data-platform.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

The stack-selection Case (A/B/C/D) this engagement fits.

House opinion #4 — embed tokens are short-lived (5–15 min).

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

data-quality-observability

Configure data-quality-observability's variables here — they save to .ravenclaude/plugins/data-quality-observability.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

data-science-research

Configure data-science-research's variables here — they save to .ravenclaude/plugins/data-science-research.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

data-streaming-engineering

Configure data-streaming-engineering's variables here — they save to .ravenclaude/plugins/data-streaming-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

database-engineering

Configure database-engineering's variables here — they save to .ravenclaude/plugins/database-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

database-reliability-engineering

Configure database-reliability-engineering's variables here — they save to .ravenclaude/plugins/database-reliability-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

dental-practice

Configure dental-practice's variables here — they save to .ravenclaude/plugins/dental-practice.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

desktop-app-engineering

Configure desktop-app-engineering's variables here — they save to .ravenclaude/plugins/desktop-app-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

developer-relations

Configure developer-relations's variables here — they save to .ravenclaude/plugins/developer-relations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

developer-tooling

Configure developer-tooling's variables here — they save to .ravenclaude/plugins/developer-tooling.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

devops-cicd

Configure devops-cicd's variables here — they save to .ravenclaude/plugins/devops-cicd.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

digital-twin-engineering

Configure digital-twin-engineering's variables here — they save to .ravenclaude/plugins/digital-twin-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ecommerce-dtc

Configure ecommerce-dtc's variables here — they save to .ravenclaude/plugins/ecommerce-dtc.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

edtech-partner-success

Configure edtech-partner-success's variables here — they save to .ravenclaude/plugins/edtech-partner-success.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

The score below which an account is RED in the health model.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

email-engineering

Configure email-engineering's variables here — they save to .ravenclaude/plugins/email-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

embedded-iot-engineering

Configure embedded-iot-engineering's variables here — they save to .ravenclaude/plugins/embedded-iot-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

engineering-management

Configure engineering-management's variables here — they save to .ravenclaude/plugins/engineering-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

esg-sustainability-reporting

Configure esg-sustainability-reporting's variables here — they save to .ravenclaude/plugins/esg-sustainability-reporting.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

event-management

Configure event-management's variables here — they save to .ravenclaude/plugins/event-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

experimentation-growth-engineering

Configure experimentation-growth-engineering's variables here — they save to .ravenclaude/plugins/experimentation-growth-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

field-service-management

Configure field-service-management's variables here — they save to .ravenclaude/plugins/field-service-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

film-video-production

Configure film-video-production's variables here — they save to .ravenclaude/plugins/film-video-production.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

finance

Configure finance's variables here — they save to .ravenclaude/plugins/finance.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

House opinion #5 — materiality is a design constraint; document the threshold.

House opinion #10 — finance data is sensitive; set the default handling class.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

finops-cloud-cost

Configure finops-cloud-cost's variables here — they save to .ravenclaude/plugins/finops-cloud-cost.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

fintech-payments-engineering

Configure fintech-payments-engineering's variables here — they save to .ravenclaude/plugins/fintech-payments-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

fitness-studio-gym-operations

Configure fitness-studio-gym-operations's variables here — they save to .ravenclaude/plugins/fitness-studio-gym-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

fleet-logistics

Configure fleet-logistics's variables here — they save to .ravenclaude/plugins/fleet-logistics.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

franchise-operations

Configure franchise-operations's variables here — they save to .ravenclaude/plugins/franchise-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

freight-forwarding-sales

Configure freight-forwarding-sales's variables here — they save to .ravenclaude/plugins/freight-forwarding-sales.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

frontend-engineering

Configure frontend-engineering's variables here — they save to .ravenclaude/plugins/frontend-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

funeral-home-operations

Configure funeral-home-operations's variables here — they save to .ravenclaude/plugins/funeral-home-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

game-development

Configure game-development's variables here — they save to .ravenclaude/plugins/game-development.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

gcp-cloud

Configure gcp-cloud's variables here — they save to .ravenclaude/plugins/gcp-cloud.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

generative-web-media

Configure generative-web-media's variables here — they save to .ravenclaude/plugins/generative-web-media.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

geospatial-engineering

Configure geospatial-engineering's variables here — they save to .ravenclaude/plugins/geospatial-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

grants-management

Configure grants-management's variables here — they save to .ravenclaude/plugins/grants-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

graphql-engineering

Configure graphql-engineering's variables here — they save to .ravenclaude/plugins/graphql-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

hardware-electronics-engineering

Configure hardware-electronics-engineering's variables here — they save to .ravenclaude/plugins/hardware-electronics-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

higher-education-administration

Configure higher-education-administration's variables here — they save to .ravenclaude/plugins/higher-education-administration.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

hospice-referral-sales

Configure hospice-referral-sales's variables here — they save to .ravenclaude/plugins/hospice-referral-sales.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

hotel-hospitality-operations

Configure hotel-hospitality-operations's variables here — they save to .ravenclaude/plugins/hotel-hospitality-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

incident-response-dfir

Configure incident-response-dfir's variables here — they save to .ravenclaude/plugins/incident-response-dfir.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

insurance-life-health-benefits

Configure insurance-life-health-benefits's variables here — they save to .ravenclaude/plugins/insurance-life-health-benefits.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

insurance-pc

Configure insurance-pc's variables here — they save to .ravenclaude/plugins/insurance-pc.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

internal-audit

Configure internal-audit's variables here — they save to .ravenclaude/plugins/internal-audit.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

itsm-service-management

Configure itsm-service-management's variables here — they save to .ravenclaude/plugins/itsm-service-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

k12-school-administration

Configure k12-school-administration's variables here — they save to .ravenclaude/plugins/k12-school-administration.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

legacy-modernization

Configure legacy-modernization's variables here — they save to .ravenclaude/plugins/legacy-modernization.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

llm-evaluation-engineering

Configure llm-evaluation-engineering's variables here — they save to .ravenclaude/plugins/llm-evaluation-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

localization-i18n-engineering

Configure localization-i18n-engineering's variables here — they save to .ravenclaude/plugins/localization-i18n-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

manufacturing-operations

Configure manufacturing-operations's variables here — they save to .ravenclaude/plugins/manufacturing-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

marketing-operations

Configure marketing-operations's variables here — they save to .ravenclaude/plugins/marketing-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

martech-event-instrumentation

Configure martech-event-instrumentation's variables here — they save to .ravenclaude/plugins/martech-event-instrumentation.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

med-spa-aesthetics

Configure med-spa-aesthetics's variables here — they save to .ravenclaude/plugins/med-spa-aesthetics.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

medical-revenue-cycle

Configure medical-revenue-cycle's variables here — they save to .ravenclaude/plugins/medical-revenue-cycle.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

microsoft-365-copilot

Configure microsoft-365-copilot's variables here — they save to .ravenclaude/plugins/microsoft-365-copilot.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

microsoft-fabric

Configure microsoft-fabric's variables here — they save to .ravenclaude/plugins/microsoft-fabric.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

Size to average + smoothing (house opinion #5); record the engagement's default capacity.

House opinion #8 — on-OneLake has NO DirectQuery fallback; on-SQL falls back. Name it.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

microsoft-graph

Configure microsoft-graph's variables here — they save to .ravenclaude/plugins/microsoft-graph.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

The Microsoft national cloud the engagement targets (endpoints differ).

Store immutable IDs for stored references (the immutable-ids best-practice).

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ml-engineering

Configure ml-engineering's variables here — they save to .ravenclaude/plugins/ml-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

mobile-engineering

Configure mobile-engineering's variables here — they save to .ravenclaude/plugins/mobile-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

mortgage-lending

Configure mortgage-lending's variables here — they save to .ravenclaude/plugins/mortgage-lending.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

museum-cultural-institution-operations

Configure museum-cultural-institution-operations's variables here — they save to .ravenclaude/plugins/museum-cultural-institution-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

network-engineering

Configure network-engineering's variables here — they save to .ravenclaude/plugins/network-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

nonprofit-fundraising

Configure nonprofit-fundraising's variables here — they save to .ravenclaude/plugins/nonprofit-fundraising.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

observability-sre

Configure observability-sre's variables here — they save to .ravenclaude/plugins/observability-sre.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

open-source-maintenance

Configure open-source-maintenance's variables here — they save to .ravenclaude/plugins/open-source-maintenance.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

optometry-eyecare-practice

Configure optometry-eyecare-practice's variables here — they save to .ravenclaude/plugins/optometry-eyecare-practice.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

people-operations-hr

Configure people-operations-hr's variables here — they save to .ravenclaude/plugins/people-operations-hr.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

performance-engineering

Configure performance-engineering's variables here — they save to .ravenclaude/plugins/performance-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

pharmacy-operations

Configure pharmacy-operations's variables here — they save to .ravenclaude/plugins/pharmacy-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

physical-therapy-rehab-clinic

Configure physical-therapy-rehab-clinic's variables here — they save to .ravenclaude/plugins/physical-therapy-rehab-clinic.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

platform-engineering-idp

Configure platform-engineering-idp's variables here — they save to .ravenclaude/plugins/platform-engineering-idp.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

power-platform

Configure power-platform's variables here — they save to .ravenclaude/plugins/power-platform.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

House opinion #5 — a prefix you control (not the default cr_) so customizations are traceable.

Environment-variable discipline (#2) — never hard-code; set the engagement's default here.

Per-tenant org URL for the official Dataverse MCP (CLAUDE.md §9a). e.g. https://contoso.crm.dynamics.com

Whether the bundled Power BI pbix-mcp server is wired (requires pip install pbix-mcp).

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

precision-agriculture

Configure precision-agriculture's variables here — they save to .ravenclaude/plugins/precision-agriculture.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

pricing-monetization

Configure pricing-monetization's variables here — they save to .ravenclaude/plugins/pricing-monetization.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

process-improvement

Configure process-improvement's variables here — they save to .ravenclaude/plugins/process-improvement.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

procurement-sourcing

Configure procurement-sourcing's variables here — they save to .ravenclaude/plugins/procurement-sourcing.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

product-management

Configure product-management's variables here — they save to .ravenclaude/plugins/product-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

project-management

Configure project-management's variables here — they save to .ravenclaude/plugins/project-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

prompt-engineering

Configure prompt-engineering's variables here — they save to .ravenclaude/plugins/prompt-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

property-management

Configure property-management's variables here — they save to .ravenclaude/plugins/property-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

public-sector-govtech

Configure public-sector-govtech's variables here — they save to .ravenclaude/plugins/public-sector-govtech.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

qa-test-automation

Configure qa-test-automation's variables here — they save to .ravenclaude/plugins/qa-test-automation.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

quantum-computing-engineering

Configure quantum-computing-engineering's variables here — they save to .ravenclaude/plugins/quantum-computing-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ravenclaude-core

Configure ravenclaude-core's variables here — they save to .ravenclaude/plugins/ravenclaude-core.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

Canonical config is .ravenclaude/comfort-posture.yaml (Settings tab). Mirrored here for visibility.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

realtime-collaboration-engineering

Configure realtime-collaboration-engineering's variables here — they save to .ravenclaude/plugins/realtime-collaboration-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

regulatory-compliance

Configure regulatory-compliance's variables here — they save to .ravenclaude/plugins/regulatory-compliance.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

House opinion #12 — name the regulator + regime so the same word isn't read across regimes.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

renewable-energy

Configure renewable-energy's variables here — they save to .ravenclaude/plugins/renewable-energy.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

report-regeneration

Configure report-regeneration's variables here — they save to .ravenclaude/plugins/report-regeneration.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

residential-real-estate-brokerage

Configure residential-real-estate-brokerage's variables here — they save to .ravenclaude/plugins/residential-real-estate-brokerage.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

restaurant-operations

Configure restaurant-operations's variables here — they save to .ravenclaude/plugins/restaurant-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

retail-store-operations

Configure retail-store-operations's variables here — they save to .ravenclaude/plugins/retail-store-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

robotics-autonomous-systems-engineering

Configure robotics-autonomous-systems-engineering's variables here — they save to .ravenclaude/plugins/robotics-autonomous-systems-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

sales-engineering

Configure sales-engineering's variables here — they save to .ravenclaude/plugins/sales-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

sales-revops

Configure sales-revops's variables here — they save to .ravenclaude/plugins/sales-revops.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

salesforce

Configure salesforce's variables here — they save to .ravenclaude/plugins/salesforce.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

The Salesforce API version this org/engagement pins (e.g. v62.0).

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

salon-spa-operations

Configure salon-spa-operations's variables here — they save to .ravenclaude/plugins/salon-spa-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

search-relevance-engineering

Configure search-relevance-engineering's variables here — they save to .ravenclaude/plugins/search-relevance-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

security-engineering

Configure security-engineering's variables here — they save to .ravenclaude/plugins/security-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

self-storage-operations

Configure self-storage-operations's variables here — they save to .ravenclaude/plugins/self-storage-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

senior-care-operations

Configure senior-care-operations's variables here — they save to .ravenclaude/plugins/senior-care-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

serverless-engineering

Configure serverless-engineering's variables here — they save to .ravenclaude/plugins/serverless-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

skilled-trades-contracting

Configure skilled-trades-contracting's variables here — they save to .ravenclaude/plugins/skilled-trades-contracting.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

staffing-operations

Configure staffing-operations's variables here — they save to .ravenclaude/plugins/staffing-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

startup-fundraising

Configure startup-fundraising's variables here — they save to .ravenclaude/plugins/startup-fundraising.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

streaming-media-engineering

Configure streaming-media-engineering's variables here — they save to .ravenclaude/plugins/streaming-media-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

supply-chain-planning

Configure supply-chain-planning's variables here — they save to .ravenclaude/plugins/supply-chain-planning.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

tableau

Configure tableau's variables here — they save to .ravenclaude/plugins/tableau.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

team-portfolio

Configure team-portfolio's variables here — they save to .ravenclaude/plugins/team-portfolio.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

technical-program-management

Configure technical-program-management's variables here — they save to .ravenclaude/plugins/technical-program-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

technical-seo-engineering

Configure technical-seo-engineering's variables here — they save to .ravenclaude/plugins/technical-seo-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

technical-writing-docs

Configure technical-writing-docs's variables here — they save to .ravenclaude/plugins/technical-writing-docs.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

terraform-iac

Configure terraform-iac's variables here — they save to .ravenclaude/plugins/terraform-iac.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

title-escrow-settlement

Configure title-escrow-settlement's variables here — they save to .ravenclaude/plugins/title-escrow-settlement.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

travel-agency-tour-operations

Configure travel-agency-tour-operations's variables here — they save to .ravenclaude/plugins/travel-agency-tour-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

treasury-management

Configure treasury-management's variables here — they save to .ravenclaude/plugins/treasury-management.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

trust-and-safety

Configure trust-and-safety's variables here — they save to .ravenclaude/plugins/trust-and-safety.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

ux-research

Configure ux-research's variables here — they save to .ravenclaude/plugins/ux-research.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

veterinary-practice

Configure veterinary-practice's variables here — they save to .ravenclaude/plugins/veterinary-practice.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

waste-recycling-operations

Configure waste-recycling-operations's variables here — they save to .ravenclaude/plugins/waste-recycling-operations.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

wealth-management-ria

Configure wealth-management-ria's variables here — they save to .ravenclaude/plugins/wealth-management-ria.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

web-commerce

Configure web-commerce's variables here — they save to .ravenclaude/plugins/web-commerce.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

web-design

Configure web-design's variables here — they save to .ravenclaude/plugins/web-design.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

advisory = warn on stderr, never block (exit 0); blocking = fail the edit on a violation (exit 1, the STRICT env var).

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.

wordpress-cms-engineering

Configure wordpress-cms-engineering's variables here — they save to .ravenclaude/plugins/wordpress-cms-engineering.yaml via the dashboard server (on the static copy, edits stay in your browser — use Download). For the full reference — agents, scenarios, skills, hooks, templates, best-practices — see this plugin in the portal's Marketplace section.

Variables

No curated knobs for this plugin yet — use the free-form section below.

Free-form variables

One key: value per line (YAML). For project variables not covered by the curated knobs above.