research-verification

Verify research assumptions and external resources with preflight checks.

2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/swannysec/robot-tools --skill research-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-verification
Source: https://github.com/swannysec/robot-tools/tree/main/research-toolkit/skills/research-verification
Command: npx skills add https://github.com/swannysec/robot-tools --skill research-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a pre-flight verification checklist to ensure research conclusions and assumptions are validated before finalizing plans, preventing costly errors.

Core Features & Use Cases

  • Existence Verification: Confirm external resources exist (docs, APIs, registries) before relying on them.
  • Schema & Version Checks: Validate configurations and versions to avoid misconfigurations.
  • Environment & Integration: Capture environment assumptions and integration touchpoints to prevent surprises in deployment.
  • Use Case: Before publishing a research plan, run the checklist to verify critical resources and assumptions, then document decisions.

Quick Start

Run the verification checklist at the start of any new research task to validate resources and assumptions.

Frequently Asked Questions about research-verification

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

FAQPage Schema
How do I verify external API resources before finalizing a research plan?

Research verification reduces plan failures by codifying preflight checks for existence, schema, version, and environment assumptions, ensuring conclusions are validated before finalization.

What is the best way to validate environment assumptions and registry configurations during research?

Validate environment assumptions and configurations by running preflight checks that capture integration touchpoints, verify schemas, and document decisions to prevent deployment surprises.

How do I use a preflight checklist to check API existence and schema versions?

Run a preflight checklist at the start of research tasks to confirm API existence, verify schema versions, and evaluate configurations before publishing plans.

Can this verification process prevent misconfigurations when evaluating external APIs?

Yes, this verification process prevents misconfigurations by validating configurations and versions during research, ensuring APIs and registries are checked for schema accuracy before finalizing plans.

When should I run preflight checks for research assumptions and documentation?

Run preflight checks for research assumptions at the start of any new research task and before publishing plans to verify critical resources and validate decisions.

What are the limitations of manual verification for external resources and integration touchpoints?

Without a codified preflight checklist, manual verification risks missing existence checks, schema validation, or environment assumptions, leading to plan failures and deployment surprises.