agentleFS
Sign inStart free
AbilityaiAbilityai/cornelius/.claude/skills/extract-document-insights/SKILL.md

extract-document-insights

Skill109 starsChanged 38 days agoMITView on GitHub

Extract insights from external documents (research papers, books, articles). Spawns document-insight-extractor subagent. Requires session name.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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
  1. Very specific:

    NOT for personal content: - use /extract-insights for your conversations, transcripts.

    line 30

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Extract Document Insights

Extract insights from EXTERNAL documents with proper epistemic classification.

Purpose

User-invocable wrapper that spawns the document-insight-extractor subagent to:

  • Extract research findings, theoretical frameworks, hypotheses
  • Classify epistemic status (confirmed, theoretical, speculative)
  • Store in session-based folders
  • Deduplicate against existing knowledge base
  • Save to Brain/Document Insights/[session]/

When to Use

  • Analyzing research papers, academic articles
  • Processing books or book chapters
  • Extracting insights from web articles, reports
  • Any EXTERNAL content (not your personal thoughts)

NOT for personal content - use /extract-insights for your conversations, transcripts.

Usage

/extract-document-insights "2025-02-21 Ancient Wisdom Research" /path/to/document.md
/extract-document-insights "AI Agent Papers" "the transcript above"

Session name is REQUIRED - describes the research session for organization.

Process

  1. Parse arguments to extract session name and source
  2. Spawn document-insight-extractor subagent via Task tool with:
    Task(
  subagent_type="document-insight-extractor",
  prompt="Extract insights from: [source] into session '[session-name]'. Follow your mandatory workflow - contextualize, classify epistemically, search duplicates, create notes, update changelog."
)
  3. Report results - number of insights extracted, session folder path

  4. Suggest insight interview - Present to user:

    "[N] insights from [source] saved to Brain/Document Insights/[session]/.

    Before these get indexed, consider running /insight-interview [topic] to capture your own angles - where you agree, disagree, or see connections the research missed. Your responses save to Brain/AI Extracted Notes/ and both sets will be available for the next connection discovery run.

    Run /insight-interview [topic] to continue, or skip if you want to index these as-is."

Outputs

  • Insight notes in Brain/Document Insights/[session]/
  • Session changelog in same folder
  • Summary with epistemic breakdown (confirmed vs hypothetical)
  • Suggested next step: /insight-interview [topic] to layer in your personal perspective

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free