Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill define-evidence-protocolAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
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
