ds-intake-audit

Audits and trust-ranks existing research assets to select the next workflow anchor.

1.1k|116|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/OpenLAIR/dr-claw --skill ds-intake-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ds-intake-audit
Source: https://github.com/OpenLAIR/dr-claw/tree/main/skills/ds-intake-audit
Command: npx skills add https://github.com/OpenLAIR/dr-claw --skill ds-intake-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Research quests often do not start from a blank state: baselines, experiment results, drafts, or reviewer comments may already exist. This Skill audits that pre-existing state, ranks each asset by trustworthiness, reconciles it with durable records, and decides which research stage should take over next instead of blindly restarting from zero.

Core Features & Use Cases

  • State Inventory: Classifies the quest into intake states such as baseline_ready, main_result_ready, draft_ready, or review_package_ready using a structured audit template.
  • Trust Ranking: Labels every major asset as trusted, usable_with_verification, reference_only, stale_or_conflicting, or missing_context, preserving provenance.
  • Route Recommendation: Records a durable decision artifact that hands off to the correct next anchor such as baseline, experiment, analysis-campaign, write, or rebuttal.
  • Use Case: A user says "baseline 已经有了,不要重新复现" — the Skill inspects existing baselines and results, confirms what is trustworthy, backfills durable records, and routes the quest directly to the experiment or writing stage.

Quick Start

Audit the current quest's existing baselines, results, and drafts, then tell me which research stage should continue next.

Frequently Asked Questions about ds-intake-audit

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

FAQPage Schema
How do I continue a research project that already has a baseline?

Run an intake audit that inventories existing baseline assets, verifies the metric contract and provenance, and confirms the baseline through durable artifact records. It then routes the quest to the experiment stage without rerunning completed work.

How to triage existing experiment results before writing a paper?

Classify each result by trust level such as trusted, usable_with_verification, or stale_or_conflicting, then reconcile verified results into durable records. The audit recommends whether analysis, writing, or rebuttal should run next.

When should I not use an intake audit for a research quest?

Skip the intake audit when the quest is genuinely blank and should start with normal scouting or baseline stages, when the state is already normalized with an obvious next step, or when the task is not research-related.

Can an intake audit handle reviewer comments and revision tasks?

Yes. When review materials or revision requests define the real task, the audit classifies the state as review_package_ready and routes the quest to the rebuttal stage instead of treating it as a fresh paper-writing pass.

Why does the audit refuse to mark an old baseline as trusted?

A baseline is only marked trusted when its metric contract, source, and comparability are clear. If provenance or verification evidence is missing, the audit records the gap explicitly rather than fabricating a clean history.