cpm:library

Store external documents with structured YAML front-matter in a CPM library.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-library
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cpm:library
Source: https://github.com/ninthspace/claude-code-marketplace/tree/main/cpm/skills/library
Command: npx skills add https://github.com/ninthspace/claude-code-marketplace --skill cpm-library

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Curate a project reference library by importing external documents with structured YAML front-matter, enabling CPM skills to discover and reuse contextual information during planning and execution.

Core Features & Use Cases

  • Intake: Import local files or URLs and generate required front-matter fields (title, source, added, last-reviewed, scope, summary) to store in docs/library/.
  • Consolidation: Reconcile amendments to maintain a clean, current library document set.
  • Batch processing & progress tracking: Manage long-running imports with a session state to guard against partial writes.

Quick Start

Import a local document or URL to begin populating the library.

Frequently Asked Questions about cpm:library

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

FAQPage Schema
How do I organize external project documentation for cross-skill reuse?

Consolidating library documents involves reconciling amendments to maintain a clean, current document set. It enforces required front-matter fields like title, source, scope, and summary to ensure a consistent downstream format for tooling.

How do I add YAML front-matter to multiple documents at once?

Importing external documents requires generating structured YAML front-matter including title, source, added, last-reviewed, scope, and summary fields. This enforced metadata enables cross-skill discovery and contextual reuse during planning execution.

Can I import both local files and URLs into a structured documentation library?

The required front-matter fields for library entries are title, source, added, last-reviewed, scope, and summary. Enforcing these fields ensures consistent formatting across documents and enables reliable cross-skill discovery during CPM planning.

How do I prevent partial writes during a long-running document import?

Document consolidation is needed when you have imported multiple external documents and need to reconcile amendments. This maintains a clean library set by ensuring all entries have consistent front-matter and a standardized downstream format for tooling.

What is the best way to maintain a current project reference library for planning?

Library entries support cross-skill discovery by enforcing structured YAML front-matter fields such as scope and summary. This standardized metadata allows other CPM planning skills to find and reuse contextual information from the stored documents.