← ClaudeAtlas

source-researchlisted

Build traceable evidence packets. Use when current research or source verification is needed.
kirilenkofedir-max/reverse-engineer-orchestra · ★ 2 · AI & Automation · score 70
Install: claude install-skill kirilenkofedir-max/reverse-engineer-orchestra
# Source Research ## Inputs Require or infer: - A bounded research question and intended decision. - Geography, language, time horizon, and material risk. - Minimum evidence needed and stopping rule. - Paths for source records, claim records, and the report. State any non-blocking assumptions before searching. ## Workflow 1. Restate the question and define acceptance criteria. 2. Search the current year first, then the previous year, then older origin/history material. 3. Prefer primary research, regulators, official documentation, professional bodies, first-party releases, and direct product evidence. 4. Use secondary reporting to discover or contextualize primary sources, not to replace them. 5. Open the supporting page; do not cite a search snippet as evidence. 6. Record one source using `knowledge/source_registry/source.schema.json`. 7. Atomize material conclusions and record them using `knowledge/claims/claim.schema.json`. 8. Link sources as `supports`, `qualifies`, `contradicts`, or `background`. 9. Seek at least one credible alternative or counterexample for a material decision. 10. Stop when the evidence threshold is met, sources repeat without adding information, or a named limitation blocks stronger inference. 11. Hand the packet to an independent reviewer. ## Allowed tools Use web search/open, official documentation, public repositories, public APIs, browser inspection, and local read-only analysis. Use private connectors only when the user explicitly place