القائمة
Use when a local Pi agent needs administrator privileges, a password-protected command, or approval for global or ambiguous deletion
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Standalone Speedrift-native planning and Workgraph compilation. PlanForge V2 uses a model-mediated planner persona, validated schema, critic pass, and Speedrift module/model assignment to produce an executable Workgraph with tests, evals, drift gates, and fix loops. Use directly when you need discovery, decomposition, or an end-to-end Speedrift execution graph.
Use when agents need Google Workspace access across Drive, Docs, Sheets, Calendar, Slides, Tasks, People, or related GWS services; choose the correct gws-account profile before using gws CLI or domain-specific gws-* skills. Do not use Python gspread/googleapiclient or custom OAuth. Use msgvault for email search/reading.
gws CLI shared reference. Use before any gws-* skill to choose the correct gws-account profile, avoid raw gws config drift, and apply shared Drive flags, auth checks, output formatting, and security rules.
Workgraph-first drift-control autopilot (driftdriver + coredrift + optional specdrift/datadrift/depsdrift/uxdrift/therapydrift/yagnidrift/redrift) with optional Amplifier runtime integration. Use for start/resume, dependency-aware execution, and keeping code/spec/intent synced without hard blocks.
Use when managing projects, programs, initiatives, dependencies, schedules, Workboard/PAIA Program tasks, Linear/GitHub/Google/Folio work, cross-system planning, weekly operating reviews, stale work rescue, operational task decomposition, or research-backed planning for Braydon's work. Covers a model-mediated program panel, research/evidence discovery, model-authored records, HTML inspection packets, change plans, approval gates, and execution ledgers.
Use when writing, revising, speaking, or thinking in a named human or agent voice; using golden voice packets, voice packs, voice guides, tone guides, or prompt packs; creating or updating voice packets; or learning voice preferences from user-edited model drafts.
| name | pi-privileged-execution |
| description | Use when a local Pi agent needs administrator privileges, a password-protected command, or approval for global or ambiguous deletion |
Use this skill when a local Pi session needs administrator privileges or must perform deletion that may affect the whole machine.
Use the privileged_exec tool for every command that requires sudo. Pass the exact shell command and working directory. Do not pre-expand, hide, rewrite, or split the command to avoid the approval boundary.
The Pi extension will show the command and ask the user for approval. If the sudo credential cache is unavailable, it will show a masked password field inside Pi. Never ask the user to paste a password into a model message or command.
Never request, echo, store, or place the password in a command, prompt, file, environment variable, tool argument, model message, notification, or returned result. The extension owns password entry and authentication.
Do not retry after denial, cancellation, failed authentication, unavailable TUI, or command failure. Report the failure and wait for the user.
Clearly local literal rm commands may use ordinary bash. Global or ambiguous deletion requires explicit approval. Treat root paths, home-directory references, wildcards, variables, shell wrappers, and equivalent deletion commands such as find ... -delete as approval-required.
If ordinary bash blocks a command containing sudo, repeat the exact request through privileged_exec. Do not work around the extension with another shell, environment variable, temporary file, or encoded password.
Expose this skill to Pi's global skill directory:
ln -sfn "/Users/braydon/projects/experiments/braydon-workspace-skills/skills/pi-privileged-execution" "$HOME/.agents/skills/pi-privileged-execution"
Then append this exact path to the existing extensions array in ~/.pi/agent/settings.json without replacing existing extensions:
/Users/braydon/projects/experiments/braydon-workspace-skills/skills/pi-privileged-execution/extension/index.ts
Restart Pi after changing the settings. The Markdown skill is guidance; the companion extension is the enforcement boundary.
User: Install the local service dependency.
Agent: I will request privileged_exec with the exact install command. Pi will show you the command and ask for approval before it runs.