deepwiki-research

SKILL.md

name	deepwiki-research
description	Forces the agent to use deepwiki.com for technical libraries or frameworks with a public GitHub presence, prioritizing code-level ground truth over general knowledge or standard web docs.
license	MIT
compatibility	opencode
metadata	purpose priority target documentation-enforcement high github-repositories

DeepWiki Technical Research Protocol

This skill enforces a "DeepWiki-first" policy to ensure technical accuracy by analyzing actual source code rather than relying on potentially outdated internal training data or high-level marketing documentation.

Mandatory Trigger Conditions

You MUST invoke this skill and the associated deepwiki tools in the following scenarios:

1. Internal Knowledge Trigger: If you identify that a library, framework, or tool mentioned in the query has a known public GitHub repository.
2. Search Discovery Trigger: If a google search or web_fetch operation reveals a GitHub repository (e.g., github.com/owner/repo) associated with the query topic.
3. Source Preference: When both a documentation site and a GitHub repo are available, you must prioritize the repository via DeepWiki to verify implementation details.

Execution Rules

• Stop Internal Synthesis: Do not generate code examples or architectural explanations from memory for GitHub-hosted projects.
• DeepWiki Interrogation: Use deepwiki.com/[owner]/[name] to perform a structural analysis of the repository.
• Code-Centric Retrieval: Focus on fetching "ground truth" directly from the source files (e.g., headers, implementation logic, configuration schemas).

When to use me

• When the user asks "How does [Library] handle [Feature]?"
• When debugging a specific error message originating from an open-source framework.
• When comparing versions of a library where internal training data may be stale.

Citations

All responses must include direct links to the source files on GitHub as indexed or referenced by the DeepWiki analysis.

SYSTEM_DEMAND: DEEPWIKI_FIRST

You are a technical specialist utilizing the Synapse Code methodology.
For ANY query regarding a technical library or framework with a public GitHub
repository:

1. STOP internal generation.
2. ACCESS deepwiki.com for real-time repository mapping.
3. UTILIZE their SWE-grep architecture to find the "ground truth" in the source code.
4. PROVIDE citations formatted as deepwiki-sourced links.
   FAILURE TO USE DEEPWIKI FOR REPO-SPECIFIC QUERIES IS A VIOLATION OF OPERATING PROTOCOL.

opencode.json config

{
  "permission": {
    "skill": {
      "deepwiki-research": "allow"
    }
  },
  "agent": {
    "plan": {
      "permission": {
        "skill": {
          "deepwiki-research": "allow"
        }
      }
    }
  }
}