research

Validate a model claim by running a focused probe and merging evidence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dylan-conlin/orch-go --skill research-dylan-conlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/dylan-conlin/orch-go/tree/main/skills/src/worker/research
Command: npx skills add https://github.com/dylan-conlin/orch-go --skill research-dylan-conlin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, constrained approach to validating a single model claim by running one predefined probe method and recording concrete evidence, ensuring reproducibility and minimal drift in assessment.

Core Features & Use Cases

  • Structured, one-claim probing: read the spawn context, select exactly one method, and generate a probe artifact.
  • Evidence-first verification: requires concrete observations to update the knowledge base model.
  • Merge findings into parent model for traceability and governance.

Quick Start

Read SPAWN_CONTEXT.md and follow the constraint: pick exactly one claim and one method, run the probe, and merge the results into the model.

Frequently Asked Questions about research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a single model claim with a focused probe?

To validate a single model claim, read the spawn context, select exactly one predefined method, execute the probe, and write a parseable artifact. This structured approach ensures minimal drift and reproducible evidence collection.

What is the best way to update a knowledge base with probe evidence?

Updating a knowledge base with probe evidence requires writing a probe artifact to the model directory and merging the finding into the parent model. This ensures traceability and governance for the observed evidence.

How do I record concrete evidence when testing a model claim?

Recording concrete evidence when testing a model claim involves generating a parseable probe artifact in the designated probes directory. This evidence-first verification requires actual observations before merging results into the parent model.

Can I run multiple methods simultaneously to verify model claims?

No, this verification approach is strictly constrained to picking exactly one claim and one method per probe. This disciplined constraint prevents assessment drift and ensures reproducible evidence collection for the parent knowledge base.

Do I need a spawn context to start probing a model claim?

Yes, reading the SPAWN_CONTEXT.md file is required before probing a model claim. This context provides the necessary constraints and scenario information to select one method and execute the validation probe correctly.