Strategy for mining concepts from sources — systematic extraction, page
Scanned 9/5/2026
Install to Claude Code
npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill concept-extraction --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Concept Extraction?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/yogsoth-ai-concept-extraction)More formats (shields.io, HTML) on the badges page.
---
name: concept-extraction
description: Strategy for mining concepts from sources — systematic extraction, page
creation, alias resolution.
execution: strategy
dependencies:
tactics:
- concept-decomposition
- knowledge-structuring-consistency-checking
sops:
- source-gathering
---
# Concept Extraction
Mine source pages for concepts. Create concept pages, resolve aliases, ensure every concept is properly named and connected.
## Guiding Focus
Extract concepts systematically from sources. Prefer precision over recall — it's better to have 20 well-defined concepts than 50 vague ones. Resolve naming conflicts immediately.
## Available Tactics
- concept-decomposition — break compound concepts into atomic parts
- consistency-checking — verify extracted concepts don't conflict
## Budget Slice
| Metric | S | M | L |
|--------|---|---|---|
| Sources processed | 8 | 20 | 40 |
| Concepts extracted | 12 | 30 | 60 |
| Aliases resolved | 3 | 10 | 20 |
## State Ledger Template
```
| Metric | Target | Current | Status |
|---------------------|--------|---------|--------|
| Sources processed | X | 0 | ⬜ |
| Concepts extracted | X | 0 | ⬜ |
| Aliases resolved | X | 0 | ⬜ |
```
<HARD-GATE>
Cannot exit until 80% of budget met. Print state ledger before each iteration decision.
</HARD-GATE>
<!-- BEGIN available-tables (generated) -->
## Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use |
| --- | --- |
| concept-decomposition | Tactic for breaking compound concepts into atomic parts — split over-broad concepts, identify sub-components, create child pages. |
| knowledge-structuring-consistency-checking | Tactic for verifying ontology consistency — detect contradictions, cycles, orphans, and type violations. |
## Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
| --- | --- |
| source-gathering | SOP for gathering source material relevant to the ontology domain — fetch papers and web pages into source pages. |
<!-- END available-tables (generated) -->
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!