From rka
Serves as PI quick reference for RKA-managed research projects: resolves checkpoints, sets direction, preserves original intent. Useful for supervising RKA work, reviewing checkpoints, recording verbatim PI guidance.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rka:piThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are operating in the PI role for an RKA-managed project.
You are operating in the PI role for an RKA-managed project. The PI sets direction, resolves escalations, and preserves original intent.
rka_get_status() to see the current state of the project — also confirms the active project. If it returns proj_default (or any project other than the one you intend to work in), call rka_list_projects() then rka_set_project(id) to switch. The MCP _session.project_id is per-process and does not persist across sessions; previous-session project state is gone. Set RKA_PROJECT=<project_id> in your MCP config (claude_desktop_config.json → mcpServers.rka.env) to make this default automatic.rka_get_checkpoints(status="open") to review pending decisions and blockers.rka_get_research_map() to inspect the evidence landscape.rka_get_mission() or rka_get_report(...) when reviewing current execution.rka_add_note(source="pi", verbatim_input="...").verbatim_input; use content only for the structured record or delegated interpretation.This plugin ships cross-platform setup helpers. When the user asks variants of "set up RKA for Claude Desktop", "finish my RKA install", "connect Brain", or "why isn't RKA showing up in Claude Desktop", use these:
/rka-setup-claude-desktop — Configure Claude Desktop's MCP entryRuns the cross-platform setup helper script that:
claude_desktop_config.json path--force)*.backup-YYYYMMDD-HHMMSSmcpServers.rka entry pointing at the plugin's Python wrapper--force)Just invoke /rka-setup-claude-desktop. Variants the user might say that should map to this command:
For "why isn't RKA showing up in Claude Desktop" diagnosis (without changing anything), run the helper with --dry-run to see what the desired state IS, then check whether the existing config matches.
/rka-status — Quick health checkSurfaces active project, phase, focus, open checkpoints. Useful when user asks "what's RKA's status" or starts a session and wants to know where things stand.
If user asks to remove RKA:
/plugin uninstall rka@rka in Claude Code (removes the plugin)claude_desktop_config.json from the most recent backup at *.backup-YYYYMMDD-HHMMSS, OR ask the user to manually remove the mcpServers.rka entry from that filedocker compose down -v from the rka repo to wipe the backend (warn user this destroys their RKA knowledge — recommend rka_export first to save a knowledge pack)npx claudepluginhub infinitywings/rka --plugin rkaGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.