Cómo usar
- Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
- Consulta las herramientas, credenciales y entornos necesarios en el documento original.
- Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill define-evidence-protocolAntes de empezar
- La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
- Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill
Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.
define-evidence-protocol
Purpose
Define research questions, eligible evidence scope, query concepts, inclusion/exclusion rules, provenance requirements, and stopping evidence.
Input contract
yaml
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
- State the question, target population or domain, comparison, outcomes, and time boundaries.
- Define eligible evidence, exclusion rules, source-independence requirements, and extraction fields.
- Specify batch boundaries, novelty dimensions, and relative stopping evidence.
- 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
yaml
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-protocolresolved: inclusion-criteria-design
