rh-inf-verify

Coordinate topic-wide verification across the RH lifecycle into a read-only report.

12|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/reason-healthcare/rh-skills --skill rh-inf-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rh-inf-verify
Source: https://github.com/reason-healthcare/rh-skills/tree/main/skills/.curated/rh-inf-verify
Command: npx skills add https://github.com/reason-healthcare/rh-skills --skill rh-inf-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified, topic-level verification across the RH lifecycle by orchestrating separate stage verifications and producing one consolidated, read-only report that preserves stage attribution.

Core Features & Use Cases

  • Orchestrates stage-specific verification workflows (discovery, ingest, extract, formalize) via subagents and reports back with a single view.
  • Normalizes results into a unified topic summary, stage results, and recommended next actions.
  • Enforces read-only behavior and preserves stage attribution to support auditability.
  • Supports safe, non-destructive verification suitable for reviewer approval workflows.

Quick Start

Run rh-inf-verify verify <topic> to generate the unified verification report for that topic.

Frequently Asked Questions about rh-inf-verify

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

FAQPage Schema
How do I consolidate topic verification across clinical informatics lifecycle stages into a single report?

Topic verification across the clinical informatics lifecycle is consolidated by orchestrating stage-specific workflows into a single, read-only report. This unified view normalizes results, preserves stage attribution, and surfaces applicability, status, blockers, and next steps for each stage.

What is a unified topic-level verification report for workflow orchestration?

A unified topic-level verification report is a read-only summary that coordinates separate stage verifications across a workflow lifecycle. It normalizes stage results into a single view, preserving stage attribution and enforcing non-destructive checks to support auditability.

Does topic verification modify tracking.yaml or write to the system during the check?

Topic verification does not modify tracking.yaml or write to the system during the check. It enforces read-only, non-destructive behavior to ensure safe verification suitable for reviewer approval workflows without altering tracking data.

Can I use topic verification for reviewer approval workflows in clinical informatics?

Topic verification supports reviewer approval workflows in clinical informatics by providing safe, non-destructive checks. It enforces read-only behavior and preserves stage attribution, ensuring the verification process is auditable without altering tracking data.

What is the best way to verify topics across discovery, ingest, extract, and formalize stages?

The best way to verify topics across discovery, ingest, extract, and formalize stages is using workflow orchestration. It coordinates stage-specific verification workflows via subagents and reports back with a unified topic summary and recommended next actions.