30 tagged pi-extension, measured the same way as everything else here.
Browse within: pi-package 71pi-coding-agent 43claude-code-plugin 42solana 37sui 37agent-management 31agent-manager 31ai-coding-agent 31code-intelligence 31coding-agent 31pi 24ai-tools 12pi-agent 8repoprompt 8
Skill Claude Code
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
Skill Claude Code needs its repo
Audit and improve existing CLAUDE.md files across a repository. Use for a deliberate, repo-wide quality review—not to record learnings from the current session.
Skill Claude CodeCodex
When to load this skill. Agents read this line to decide whether to load it, so be specific.
imsus/pi-extension-minimax-coding-plan-mcp
Skill Claude CodeCodex
Search the web for current information using the websearch tool.
Skill Claude CodeCodex
Record and retrieve structured project learnings using mulch CLI. Use when working on code and wanting to capture patterns, failures, decisions, conventions, references, or guides for future sessions.
Skill Claude Code
Design Thinking — the §1–§10 problem-first pipeline: shapes → graph(A) → cardinality → break points (E: ⟳ ↯ ☠) → requirements (R) → boundaries → behavior layers → scope → test layers → verdict. Stack-agnostic. Use when planning, designing, or refactoring any feature or system.
Skill Claude CodeCodex
Manage resident peer agents: long-running monitors that live inside the pi session, tick on minute intervals, watch the main agent's work, and push findings back mid-turn. Use when the user asks to launch/stop/ask a peer, watcher, monitor, observer, sentinel, or auditor; wants standing review, drift/scope watching…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: