wiki-researcher
Research Codebases with Evidence
Deep codebase questions are hard to answer without tracing real implementations. This skill guides Claude, Codex, and Claude Code through structured evidence-based research.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "wiki-researcher" from https://skillstore.io/skills/sickn33-wiki-researcher.md and its manifest at https://skillstore.io/api/skills/sickn33-wiki-researcher/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "wiki-researcher". Explain how user authentication works in this repository.
Expected outcome:
Identifies route registration, request handlers, token validation, session storage, and cited confidence levels.
Using "wiki-researcher". Trace where pricing data comes from and where it is displayed.
Expected outcome:
Shows entry points, service calls, transformations, UI consumers, and open questions for untraced paths.
Using "wiki-researcher". Review the notification subsystem for technical debt.
Expected outcome:
Lists coupling, repeated patterns, risk areas, and recommended next steps with supporting file references.
Security Audit
SafeThe two static findings are false positives in Markdown prose, not executable behavior. The first is inline-code formatting for citation syntax, and the second is guidance for diagrams in architecture explanations. No prompt injection or malicious intent was found in SKILL.md.
Risk Factors
⚙️ External commands (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-wiki-researcher/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-wiki-researcher?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-wiki-researcher?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-wiki-researcher/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-wiki-researcher.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). wiki-researcher security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-wiki-researcher/audits/5BibTeX citation
@techreport{sickn33-sickn33-wiki-researcher-2026,
author = {sickn33},
title = {wiki-researcher security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-wiki-researcher/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wiki-researcher security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-wiki-researcher/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-wiki-researcher:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Map a Feature
A developer traces how one feature moves through entry points, services, data stores, and outputs.
Prepare Architecture Notes
A technical writer gathers grounded evidence before documenting how a subsystem works.
Assess Technical Debt
An engineering lead reviews coupling, anti-patterns, and risks before planning refactoring work.
Try These Prompts
Use wiki-researcher to explain how [component] works. Trace the real implementation and cite every significant claim.
Use wiki-researcher to trace how [data or request] moves from [entry point] to [destination]. Include transformations, dependencies, and open questions.
Use wiki-researcher to compare how [feature A] and [feature B] are implemented. Identify shared paths, differences, risks, and evidence.
Use wiki-researcher to produce a full five-pass analysis of [system]. Cover architecture, state, integrations, patterns, recommendations, confidence, and unanswered questions.
Best Practices
- Start with a narrow topic and expand only when the trace requires it.
- Ask for citations and confidence ratings for every important conclusion.
- Use follow-up prompts to close open questions after each research pass.
Avoid
- Do not ask for a whole repository summary without a specific system or feature.
- Do not accept diagrams that are not tied to verified implementation paths.
- Do not treat inferred architecture as fact without cited evidence.