skills.rest
glfruit
glfruitCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pkm-core

Unify PKM vault configurations and frontmatter conventions across skills.

Updated Feb 6, 2026
Search Tags:#markdown#pkm#obsidian#naming-conventions#frontmatter#vault-paths
One-click install
npx skills add https://github.com/glfruit/gorin-skills --skill pkm-core
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pkm-core
Source: https://github.com/glfruit/gorin-skills/tree/main/openclaw/pkm-core
Command: npx skills add https://github.com/glfruit/gorin-skills --skill pkm-core

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PKM Core provides the foundational conventions that all note-type skills share, including vault paths, frontmatter rules, and Obsidian syntax, ensuring consistency and reusability across the PKM toolkit.

Core Features & Use Cases

  • Shared vault path standards and a single source of truth for vault-config.yaml.
  • Unified frontmatter and naming conventions to keep notes interoperable across Atlas, Octopus, Loom.
  • Reference materials and syntax guidelines (Obsidian) to accelerate knowledge work and cross-skill integration.
  • Use Case: A PKM workflow where multiple skills save and link notes consistently, enabling reliable indexing and cross-referencing.

Quick Start

Configure your environment to rely on PKM Core for vault mappings and frontmatter conventions, then reference it from dependent PKM skills.

Frequently Asked Questions about pkm-core

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

FAQPage Schema
How do I unify Obsidian frontmatter conventions across multiple vaults?▼

To unify Obsidian frontmatter conventions, apply standardized fields, ASCII keys, and consistent date formats to ensure notes remain interoperable and properly indexed across shared pipelines.

What is the best way to standardize PKM vault paths and naming rules?▼

Standardizing PKM vault paths involves applying a single source of truth from vault-config.yaml alongside strict naming conventions, ensuring consistent note organization and reliable cross-referencing across skills.

How do I maintain consistent markdown notes when using multiple knowledge management skills?▼

Maintaining consistent markdown notes requires enforcing unified frontmatter fields and shared Obsidian syntax references, allowing multiple skills to save, link, and index notes without structural conflicts.

Does this approach to PKM configuration support cross-skill integration for notes?▼

Yes, this PKM configuration approach supports cross-skill integration by validating note structures through a shared pipeline, ensuring that frontmatter and vault mappings remain interoperable across different workflows.

Why do my knowledge base notes have broken cross-references after importing from different sources?▼

Broken cross-references often occur because of inconsistent vault path mappings and non-standardized frontmatter, which prevent reliable indexing and linking across the shared knowledge management pipeline.

Related Skills

Explore More Education & Research Skills→
Nero-kkNero-kk

wiki-setup

Initialize an Obsidian vault with directories, configuration files, and sanity checks.

Community
Intermediate
emanueleieloemanueleielo

cortex

Manage Markdown knowledge graphs with typed links and visual scene generation.

Community
Intermediate
89jobrien89jobrien
1

obsidian-vault

Enforce YAML frontmatter, templates, and wikilinks in Obsidian Vault notes.

Community
Intermediate
giwankimgiwankim

obsidian-markdown

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, and frontmatter.

Community
Basic