Menu
Design and audit Pi extensions safely (avoid workspace source imports).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
ARCHIVED — project work items are tracked in GitHub Issues and GitHub Projects. Use the github-issues skill when installed, or use gh directly.
Diagnose and fix piclaw extension issues (imports, DB init errors, watcher perms), update skel, and restart safely.
Search the web via SearXNG (or DuckDuckGo fallback) and optionally fetch result pages as raw Markdown content.
Search via SearXNG (or DuckDuckGo fallback), fetch top results, and return sentence-level summaries plus optional converted page content.
Fetch a user's recent tweets (tweets, replies, retweets) using Playwright + Nitter fallbacks and produce compact JSON/Markdown summaries.
Write and review concise technical documentation using a plain-English voice guide and anti-trope filter. Use for READMEs, design notes, runbooks, API documentation, release notes, and pull-request text.
| name | extension-design |
| description | Design and audit Pi extensions safely (avoid workspace source imports). |
| distribution | public |
Use this skill when creating or reviewing extensions so imports keep working after reloads.
Do not import from the workspace source tree (for example /workspace/piclaw/runtime/src/... or /workspace/.../node_modules).
The running agent uses the installed package. Workspace paths can drift or break after reloads.
Reference the installed dist paths, for example:
import { createBatchExecTool } from "/home/agent/.bun/install/global/node_modules/piclaw/dist/tools/context-tools.js";
try/catch to avoid crashes.saveToolOutput calls.rg -n "/workspace/piclaw/runtime/src|/workspace/.*/node_modules" /workspace/.pi/extensions
cp /workspace/.pi/extensions/<name>.ts /workspace/piclaw/skel/.pi/extensions/<name>.ts