Skip to content
Automation
Skill

/define-evidence-protocol

Define research questions, evidence scope, queries/concepts, inclusion/exclusion rules, provenance requirements, and stopping evidence for an acquisition task.

From plugin
de-anthropocentric-research-engine
499200 skills
Install
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill define-evidence-protocol --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/define-evidence-protocol

Context preview

The summary Claude sees to decide when to auto-load this skill.

Define research questions, evidence scope, queries/concepts, inclusion/exclusion rules, provenance requirements, and stopping evidence for an acquisition task.

SKILL.md

define-evidence-protocol.SKILL.md
name: define-evidence-protocol
description: "Define research questions, evidence scope, queries/concepts, inclusion/exclusion rules, provenance requirements, and stopping evidence for an acquisition task."

define-evidence-protocol

Purpose

Define research questions, eligible evidence scope, query concepts, inclusion/exclusion rules, provenance requirements, and stopping evidence.

Input contract

required: [research_question, evidence_scope, inclusion_rules]
optional: [exclusion_rules, query_concepts, quality_rubric, stopping_policy]
constraints: [eligible universe, provenance fields, and stopping evidence must be explicit]

Procedure

1. State the question, target population or domain, comparison, outcomes, and time boundaries. 2. Define eligible evidence, exclusion rules, source-independence requirements, and extraction fields. 3. Specify batch boundaries, novelty dimensions, and relative stopping evidence. 4. Record unresolved scope choices before acquisition begins.

If the protocol fixes inclusion, exclusion, and stopping rules, consider `select-seed-evidence` as the next tactic.

Output contract

produces: [evidence_protocol, eligible_universe, query_concepts, screening_rules, provenance_requirements, stopping_evidence]
delta_fields: [decisions, assumption_updates, uncertainties, open_questions]

Quality gates

  • The eligible universe and exclusion rules are operational.
  • Stopping evidence names numerator, denominator, batch increment, source references, direction, threshold, and rationale when relative quantities apply.

Failure and counterexamples

Do not use provider names as a protocol, and do not declare coverage from search volume without a defined eligible universe.

Provenance map

  • `resolved: define-search-protocol`
  • `resolved: inclusion-criteria-design`
Read more
Ships withde-anthropocentric-research-engine

The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.

Get the whole plugin