Skip to content
Back to skills

Categorize Evidence

ASecurity

Cluster an evidence corpus by theme, method, chronology, mechanism, or another declared schema.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
researchgo

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill categorize-evidence --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Categorize Evidence?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Categorize Evidence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-categorize-evidence/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-categorize-evidence)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: categorize-evidence
description: "Cluster an evidence corpus by theme, method, chronology, mechanism, or another declared schema."
---

# categorize-evidence

## Purpose

Cluster an evidence corpus by a declared thematic, methodological, chronological, mechanistic, or other schema.

## Input contract

```yaml
required: [evidence_records, category_schema]
optional: [coding_rules, multi_label_policy, seed_categories]
constraints: [category assignments require record evidence and allow explicit multi-label or unknown states]
```

## Procedure

1. Define category semantics and assignment rules.
2. Code each record using the declared evidence fields.
3. Review boundary cases and preserve multi-label or unresolved assignments.
4. Summarize category coverage and representative records.

If categorized sources now need claim-level structured records, consider `extract-evidence-record` as the next tactic.

## Output contract

```yaml
produces: [categorized_corpus, category_definitions, boundary_cases, coverage_summary]
delta_fields: [findings, evidence_updates, uncertainties, open_questions]
```

## Quality gates

- Categories are mutually interpretable even when not mutually exclusive.
- Every assignment is traceable to record fields.

## Failure and counterexamples

Do not force records into categories whose definitions do not fit, and do not confuse frequency with evidential importance.

## Provenance map

- `resolved: knowledge-acquisition-categorize-papers`
- `concept: knowledge-structuring/source-categorization-patterns`
- `intermediate: Pass4/map-field-taxonomy`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…