concept-extractor
Skill2 starsChanged 38 days agoMITView on GitHub
Use to exhaustively extract core knowledge concepts, scientific terms, and specialized vocabulary from a document to build a comprehensive wiki-linked knowledge graph.
In this repository15 other files it gives its agents.
- notemdproSkill
- batch-processorSkill
- content-generatorSkill
- diagram-generatorSkill
- formula-healerSkill
- link-analyzerSkill
- mermaid-healerSkill
- mermaid-summarizerSkill
- qa-extractorSkill
- selection-processorSkill
- system-architectureSkill
- test-driven-developmentSkill
- text-translatorSkill
- web-researcherSkill
- workflow-runnerSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
When executing this skill, DO NOT STOP at 3 to 5 concepts.
- Distinctive: line 20
When the user asks you to extract concepts from a specific Markdown file (or text), follow these steps strictly:
- Distinctive: line 24
Read the entire target document thoroughly.
- Distinctive: line 30
Normalization: Always normalize to the singular form (e.g., "Isotope" instead of "Isotopes") and capitalize Title Case (e.g., "DNA …
- Very specific: line 54
After creating the atomic concept notes, you must run the link-analyzer skill (or do it manually if instructed) to go back into the …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
NoteMD Pro - Concept Extraction (Agentic Workflow)
Overview
This skill transforms standard Markdown text into an interconnected Knowledge Graph by exhaustively extracting every relevant concept and generating atomic notes with proper backlinks.
⚠️ Critical Rule: Exhaustive Extraction
When executing this skill, DO NOT STOP at 3 to 5 concepts. You must thoroughly scan the entire document and extract every single core knowledge point, technical term, scientific principle, proper noun, and specialized vocabulary word. A comprehensive document (e.g., 1000 words) might yield 15-30 distinct concepts.
Your goal is to be as complete and reasonable as possible, ensuring the end-user's Knowledge Graph is densely populated and highly interconnected.
Step-by-Step Agent Instructions
When the user asks you to extract concepts from a specific Markdown file (or text), follow these steps strictly:
Step 1: Comprehensive Parsing
Read the entire target document thoroughly. Mentally (or in your scratchpad) list every concept following these criteria:
- Scientific & Technical Terms: e.g., "DNA Replication", "Ribosome", "Stellar Nucleosynthesis", "Isotope", "Spectroscopy", "Amino Acid".
- Theories & Principles: e.g., "Statistical Mechanics", "Conservation of Energy".
- Proper Nouns & Tools: e.g., "Tesseract OCR", "Python multiprocessing", "Markdown".
- Abstract Concepts: Limit abstract ideas unless they are central to the domain. Focus on specific noun-phrases.
- Normalization: Always normalize to the singular form (e.g., "Isotope" instead of "Isotopes") and capitalize Title Case (e.g., "DNA Replication").
Step 2: Generate Atomic Concept Notes
For every single concept you identified in Step 1, create a separate atomic note file in the target directory (often a Concepts/ folder or the same folder as the source).
Filename: [Concept Name].md
Content Format:
# [Concept Name]
Brief 1-2 sentence definition or summary of the concept (derive this from your internal knowledge base or the source text context).
## Linked From
- [[Name of the Original Source File]](Note: Always append the exact name of the file you are extracting from to the ## Linked From section, wrapped in [[wiki-links]])
Step 3: Inject Wiki-Links into Source
After creating the atomic concept notes, you must run the link-analyzer skill (or do it manually if instructed) to go back into the original source file and wrap the occurrences of those concepts with Obsidian wiki-links: [[Concept Name|original text]].
Output Quality Checklist for the Agent
- Did I extract all possible valid concepts, or did I stop early out of laziness? (Aim for exhaustive depth).
- Are the concepts normalized to singular, Title Case forms?
- Did I create an individual
.mdfile for every extracted concept? - Did I add the
## Linked Frombacklink in every concept note?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

