documents

Automate CRM document management and linked entry notes across object hierarchies.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/himes19/pulsevolt-infra --skill documents-himes19
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documents
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/crm/documents
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill documents-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the management of CRM documents and their associated entry notes, ensuring every row has a connected markdown document that serves as the long-form companion and audit trail.

Core Features & Use Cases

  • Establish connected entry documents for CRM entries and keep them in sync during mutations, including notes, detail pages, and cross-nested references.
  • Maintain a DuckDB-backed documents registry with metadata like title, file_path, parent_object_id, and entry_id to support robust auditing and cross-linking.
  • Support entry detail pages where each entry gets a human-readable markdown file under its object, with a running activity log and mutation history.

Quick Start

Create or update the connected entry document when you create or mutate an entry, and register it in the documents table.

Frequently Asked Questions about documents

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

FAQPage Schema
How do I automate CRM document management for linked entry notes?

Automating CRM document management involves creating connected markdown entry documents that sync during mutations, while registering metadata in a DuckDB-backed documents table for auditing and cross-linking.

What are connected entry documents and when do I need them for CRM entries?

Connected entry documents are markdown files linked to CRM entries across object hierarchies. You need them when creating or updating row notes, detail pages, or documents to maintain a long-form companion and audit trail.

How do I maintain an audit log for CRM entry mutations and detail pages?

To maintain an audit log for CRM entry mutations, create human-readable markdown detail pages under each entry's object, storing a running activity log and mutation history alongside a documents registry.

Does DuckDB support a documents registry for tracking CRM file paths and metadata?

Yes, DuckDB supports a documents registry that tracks metadata like title, file_path, parent_object_id, and entry_id, enabling robust auditing and cross-linking across connected entry documents.

How do I handle cross-nesting rules when updating linked CRM documents?

Handling cross-nesting rules requires enforcing a storage model that keeps connected entry documents in sync during mutations, ensuring references across object hierarchies remain consistent and logged.

What limitations should I consider when using markdown for CRM document management?

Using markdown for CRM document management requires enforcing a strict storage model with a documents registry and mutation logs, meaning you must register every created or updated entry document to maintain consistency.