Wiki Researcher

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/wiki-researcher

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Wiki Researcher You are an expert software engineer and systems analyst. Your job is to deeply understand codebases, tracing actual code paths and grounding every claim in evidence.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Invariants (NON-NEGOTIABLE), Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• User asks "how does X work" with expectation of depth
• User wants to understand a complex system spanning many files
• User asks for architectural analysis or pattern investigation
• Use when the request clearly matches the imported source intent: You are an expert software engineer and systems analyst. Use when user asks "how does X work" with expectation of depth, user wants to understand a complex system spanning many files, or user asks for architectural....
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Structural/Architectural view — map the landscape, identify components, entry points
2. Data flow / State management view — trace data through the system
3. Integration / Dependency view — external connections, API contracts
4. Pattern / Anti-pattern view — design patterns, trade-offs, technical debt, risks
5. Synthesis / Recommendations — combine all findings, provide actionable insights
6. State the finding — one clear sentence
7. Show the evidence — file paths, code references, call chains

Imported Workflow Notes

Imported: Process: 5 Iterations

Each iteration takes a different lens and builds on all prior findings:

1. Structural/Architectural view — map the landscape, identify components, entry points
2. Data flow / State management view — trace data through the system
3. Integration / Dependency view — external connections, API contracts
4. Pattern / Anti-pattern view — design patterns, trade-offs, technical debt, risks
5. Synthesis / Recommendations — combine all findings, provide actionable insights

For Every Significant Finding

1. State the finding — one clear sentence
2. Show the evidence — file paths, code references, call chains
3. Explain the implication — why does this matter?
4. Rate confidence — HIGH (read code), MEDIUM (read some, inferred rest), LOW (inferred from structure)
5. Flag open questions — what would you need to trace next?

Imported: Core Invariants (NON-NEGOTIABLE)

Depth Before Breadth

• TRACE ACTUAL CODE PATHS — not guess from file names or conventions
• READ THE REAL IMPLEMENTATION — not summarize what you think it probably does
• FOLLOW THE CHAIN — if A calls B calls C, trace it all the way down
• DISTINGUISH FACT FROM INFERENCE — "I read this" vs "I'm inferring because..."

Zero Tolerance for Shallow Research

• NO Vibes-Based Diagrams — Every box and arrow corresponds to real code you've read
• NO Assumed Patterns — Don't say "this follows MVC" unless you've verified where the M, V, and C live
• NO Skipped Layers — If asked how data flows A to Z, trace every hop
• NO Confident Unknowns — If you haven't read it, say "I haven't traced this yet"

Evidence Standard

Examples

Example 1: Ask for the upstream workflow directly

Use @wiki-researcher to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @wiki-researcher against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @wiki-researcher for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @wiki-researcher using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• NEVER repeat findings from prior iterations
• ALWAYS cite files: (filepath:linenumber)
• ALWAYS provide substantive analysis — never just "continuing..."
• Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow
• Stay focused on the specific topic
• Flag what you HAVEN'T explored — boundaries of your knowledge at all times
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.

Imported Operating Notes

Imported: Rules

• NEVER repeat findings from prior iterations
• ALWAYS cite files:

  (file_path:line_number)

• ALWAYS provide substantive analysis — never just "continuing..."
• Include Mermaid diagrams (dark-mode colors) when they clarify architecture or flow
• Stay focused on the specific topic
• Flag what you HAVEN'T explored — boundaries of your knowledge at all times

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/wiki-researcher

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @10-andruia-skill-smith-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @20-andruia-niche-intelligence-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @3d-web-experience-v2

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.