Files
magnus919_agent-skills/research-methodology/SKILL.md
T
Magnus HedemarkandGitHub 082fd698e5 fix(research): require durable artifact preservation
Require durable, source-linked research artifacts and source-to-artifact preservation tracking.
2026-07-15 16:17:54 -04:00

5.4 KiB

name, description, license, compatibility, metadata
name description license compatibility metadata
research-methodology Plan, conduct, evaluate, and synthesize rigorous research. Use for journalistic, industry, or technical investigations that need credible evidence and a traceable method. MIT No runtime dependency. Use appropriate retrieval tools and retain source URLs and access dates in the research log.
source_repo source_commit
https://github.com/magnus919/hermes-profiles 867a555

Research Methodology

Professional research process for a subagent. Three tracks based on the type of research:

  • Journalistic — investigative pieces, primary source research, source-heavy narrative work
  • Industry analysis — market research and strategy, signal detection
  • Academic/Comprehensive — deep systematic research when depth matters most

All three share the same lifecycle (Scope → Gather → Evaluate → Analyze → Synthesize → Report) but differ in evidence standards, speed, and output format.

The Research Lifecycle

SCOPE → GATHER → EVALUATE → ANALYZE → SYNTHESIZE → REPORT

Durable Artifact Gate

Research is not complete when an agent has produced a plausible answer. It is complete when the reusable evidence and reasoning have been preserved in the durable format that is natural to the host system and its users.

Before reporting, make the preservation decision explicit:

  1. Identify the durable destination. Use the host's normal long-lived research surface: linked knowledge records, a tracked report package, a research database, a project document, or another user-visible artifact. Do not leave the only useful output in chat, a transient workspace, or an untracked scratch file.
  2. Extract at the source's natural granularity. Capture every distinct, reusable claim, data point, method, contradiction, and open question that materially changes future reasoning. Do not use a fixed atom, finding, or note count as a stopping rule. Continue until each retained source is accounted for in the extraction log.
  3. Preserve provenance and relationships. Each durable artifact must retain its source URL or citation, access date, evidence strength, and links to the question, related artifacts, and any synthesis that depends on it.
  4. Separate extraction from synthesis. A brief or report explains the conclusion; it does not replace the underlying evidence records. Preserve source-level records and reusable claims before compacting them into a synthesis.
  5. Record what was not preserved. If a source was rejected, too weak, inaccessible, redundant, or out of scope, record that decision in the research log. A future researcher must be able to distinguish an intentional exclusion from an overlooked source.

The right artifact shape depends on the environment. Do not assume a particular database, note-taking application, or orchestration system. The invariant is durable, navigable, evidence-linked research that a later user or agent can discover and build on.

Reference Files

Tracks

Track Reference When to load
Journalistic references/journalistic-research.md You're researching an investigative piece — primary sources, interviews, documents, series management, pre-publication verification
Industry analysis references/industry-analysis.md You're researching an industry analysis piece — signal detection, corporate evidence, competitive intelligence, case study standards
Academic / Comprehensive references/research-lifecycle.md You're doing deep systematic research — question scoping, search strategy, inclusion/exclusion criteria

Shared Methodology

Reference When to load
references/source-evaluation.md You need to judge whether a source is credible — CRAAP test, triangulation, reliability tiers
references/structured-analytic-techniques.md You need to evaluate competing explanations — ACH, driving forces, pre-mortem, indicators
references/synthesis-patterns.md You need to combine findings from multiple sources into synthesized conclusions
references/technical-verification.md You need to test a technical claim by reproducing it — benchmarks, API behavior, configuration

Assets

Asset What it produces
assets/research-brief.md Structured brief with findings, confidence assessment, evidence table, open questions
assets/research-log.md Traceable record of searches, sources, and decisions

Use both assets for every substantial investigation. Before closing the work, complete their durable-artifact sections and verify that retained sources and extracted claims are represented in the destination system.

Pre-Publication Gateway

For any piece that makes factual claims, load the relevant track's verification protocol before reporting back:

  • Journalistic: 7-step pre-publication protocol from references/journalistic-research.md
  • Industry: 7-step research protocol from references/industry-analysis.md
  • Technical: 5-step reproduction protocol from references/technical-verification.md

Portability

This skill is intentionally host-neutral. Use your agent's normal mechanisms to load the references, templates, and scripts listed here. Do not assume a particular profile system, task orchestrator, memory service, or response-handoff format.