メニュー
Use when a Searchpo task involves GitHub repository understanding, DeepWiki MCP, repo architecture questions, dependency exploration, or source-code context as supporting context after AnySearch-first evidence planning has started.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | searchpo-deepwiki-research |
| description | Use when a Searchpo task involves GitHub repository understanding, DeepWiki MCP, repo architecture questions, dependency exploration, or source-code context as supporting context after AnySearch-first evidence planning has started. |
| version | 1.0.0 |
| triggers | ["DeepWiki","deepwiki","MCP repo research","repo architecture","GitHub repository understanding","source-code context","代码库理解"] |
| tools | ["mcp__deepwiki.read_wiki_structure","mcp__deepwiki.read_wiki_contents","mcp__deepwiki.ask_question","shell","filesystem"] |
| mutating | false |
Use this skill for repo-focused context collection. DeepWiki is a supporting repository-intelligence surface, not a replacement for Searchpo canonical evidence or AnySearch supplemental research.
.mcp.json and declares deepwiki as https://mcp.deepwiki.com/mcp.mcp__deepwiki.read_wiki_structure, mcp__deepwiki.read_wiki_contents, and mcp__deepwiki.ask_question when those tools are available.mcp__deepwiki__read_wiki_structure, mcp__deepwiki__read_wiki_contents, and mcp__deepwiki__ask_question.generate_wiki unless the user explicitly asks to generate a wiki.owner/repo.searchpo-research-agent has started the AnySearch-first evidence path: canonical URL detail, GitHub API/README evidence, and AnySearch search/extract planning. If not, return to searchpo-research-agent first.python3 scripts/agent_capabilities.py --profile repo --format text to verify MCP/key availability without printing secrets.read_wiki_structure to find topic areas.read_wiki_contents when full repo documentation is useful and concise enough.ask_question for targeted questions such as architecture, CLI entrypoint, render path, API boundary, or safety model.fact_bank.json, topic_brief.json, and cross_check_review.json..env values.Convert prompts, vague tasks, product requirements, coding requests, research plans, monitors, reminders, and agent workflows into repeatable, verifiable loops. Use when the user asks to "loopify" a requirement, turn a prompt into an agent loop, design unattended or recurring work, define /loop or routine instructions, create guardrails for autonomous agents, convert one-shot tasks into monitored workflows, or make future prompts more reliable through goal/scope/verification/escalation/stop conditions.
Frontend design cognitive system grounded in Michael Polanyi's tacit knowledge theory. Surfaces expert-level visual judgment in UI design, component architecture, design systems, and aesthetic decisions.
Domain knowledge for designing a search harness for coding agents — search API landscape, ground-API pipeline/strategy, CLI + skills architecture, and roadmap. Use when discussing search agent infrastructure, choosing search APIs for agents, designing search pipelines, or reviewing the search-harness project direction.
Remotion video composition best practices for searchpo. Use when editing src/ components, configuring rendering, optimizing video output, or adding animations/effects to the Remotion pipeline.
Use when Searchpo agents need to inspect available .env keys, provider/API capabilities, DeepWiki MCP availability, credential routing, side-effect boundaries, or decide which agent should use which external service without exposing secrets.
Run the full Searchpo provider/live flow from input selection through evidence, FactBank, DeepSeek/Gemini, Remotion render, audit, delivery package, and Douyin gate verification. Use when the user asks to run the complete flow, full flow, /searchpo-full-flow, end-to-end publishable render, or live publish.