القائمة
Query any public GitHub repo's documentation via DeepWiki. Use when needing to understand a library, framework, or dependency. Triggers on "look up docs", "how does X work", "deepwiki".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Control herdr from inside it. Manage workspaces and tabs, split panes, spawn agents, read output, and wait for state changes — all via CLI commands that talk to the running herdr instance over a local unix socket. Use when running inside herdr (HERDR_ENV=1).
Analyze pi session token usage and produce a breakdown report. Sums the usage blocks recorded in pi session logs. Use when the user wants a token report, usage breakdown, "how much have I used", cached-vs-fresh token split, per-model or per-project cost/tokens, or asks to analyze pi usage.
Use when using the agent tool or delegating to subagents. Use it for tasks that benefit from isolated context: codebase exploration, planning, focused implementation, or code review.
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
| name | deepwiki |
| description | Query any public GitHub repo's documentation via DeepWiki. Use when needing to understand a library, framework, or dependency. Triggers on "look up docs", "how does X work", "deepwiki". |
Query any public GitHub repo's docs from the terminal via DeepWiki. Assumes Node.js is installed.
| Command | Usage | Description |
|---|---|---|
toc | bunx @seflless/deepwiki toc <owner/repo> | Table of contents |
wiki | bunx @seflless/deepwiki wiki <owner/repo> | Full wiki content |
ask | bunx @seflless/deepwiki ask <owner/repo> "<question>" | AI-powered Q&A |
ask | bunx @seflless/deepwiki ask <repo1> <repo2> "<question>" | Multi-repo Q&A (max 10) |
| Flag | Purpose |
|---|---|
--json | Raw JSON output (good for piping) |
-q, --quiet | No spinners/progress |
--no-color | Disable colors |
# Understand a library's structure
bunx @seflless/deepwiki toc facebook/react
# Get full docs for reference
bunx @seflless/deepwiki wiki oven-sh/bun --json > bun-docs.json
# Ask a specific question
bunx @seflless/deepwiki ask anthropics/claude-code "How does the tool permission system work?"
# Cross-project question
bunx @seflless/deepwiki ask facebook/react vercel/next.js "How do server components work across these projects?"
--json when you need structured data to parsetoc first to understand what docs exist, then ask for specificsask is great for understanding how libraries interact