epistemic-pkm-research

Guide epistemic classification and PKM artifact structuring with duplicate checks.

5|4|Updated Dec 4, 2017
One-click install
npx skills add https://github.com/Nathan-Schwartz/dotfiles --skill epistemic-pkm-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epistemic-pkm-research
Source: https://github.com/Nathan-Schwartz/dotfiles/tree/main/claude/.claude/skills/epistemic-pkm-research
Command: npx skills add https://github.com/Nathan-Schwartz/dotfiles --skill epistemic-pkm-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides behavioral guidance for producing epistemically classified PKM artifacts.

Core Features & Use Cases

  • Guidance for epistemic classification of PKM notes and artifacts.
  • Reference material structuring with PKM schemas, provenance tagging, and behavioral prompts.
  • Duplicate checking and proper formatting guidance to ensure verifiable artifacts.

Quick Start

Instruct the epistemic-explore agent to load this reference and apply its PKM guidance to classify a new PKM artifact.

Frequently Asked Questions about epistemic-pkm-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify epistemic PKM artifacts for reference materials?

Epistemic PKM artifact classification applies behavioral guidance and structured schemas to tag reference materials with provenance, distinguishing between ref and synth outputs for verifiable knowledge management.

What is the best way to structure PKM notes with provenance tagging?

PKM note structuring uses defined schemas and provenance tagging to organize artifacts, outputting them under project-root scratch areas or permanent pkm directories to maintain clear epistemic boundaries.

Can I check for duplicate qmd files when producing PKM artifacts?

Qmd duplicate checking is supported as an optional feature during PKM artifact production, ensuring verifiable reference materials by identifying overlapping content before final classification.

How do I distinguish between ref and synth outputs in a PKM directory?

Ref and synth outputs are distinguished by applying epistemic classification rules, separating reference materials from synthesized notes within project-root scratch areas or permanent pkm directories.

Does epistemic classification require specific dependencies or environments?

Epistemic classification requires no external dependencies, operating through behavioral guidance applied by an epistemic-explore agent to format and organize reference artifacts within your existing PKM setup.

When should I not use qmd duplicate checking for PKM notes?

Qmd duplicate checking is optional, so you can skip it when synthesizing novel notes or when working in temporary project-root scratch areas where overlapping reference content is expected during exploration.