documents

Create and manage Markdown entry documents linked to CRM entries in DuckDB.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/putrawitama/DenchClaw --skill documents-putrawitama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documents
Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/crm/documents
Command: npx skills add https://github.com/putrawitama/DenchClaw --skill documents-putrawitama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures every CRM entry has a connected, human-readable Markdown document that acts as the primary long-form record and audit trail, and it keeps that document synchronized with the entry's metadata in DuckDB via the documents table and mutation logs.

Core Features & Use Cases

  • Automatically creates or repairs a connected entry document when an entry is created or mutated, ensuring a registered file path, appropriate title, and linkage to the entry_id and parent_object_id.
  • Keeps an activity log within the entry document to record mutations and changes for an auditable history.
  • Enforces naming conventions and cross-nesting rules so documents live under the correct object directory while remaining discoverable and human-readable.
  • Supports standalone object-level documents in addition to entry documents, with clear distinction in the documents table.
  • Synchronizes Markdown content with metadata in DuckDB, updating or creating the relevant documents row as needed to maintain consistency.

Quick Start

Create or update an entry and automatically generate or repair its connected Markdown document, register it in DuckDB, and append an activity log.

Frequently Asked Questions about documents

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

FAQPage Schema
How do I automatically create linked Markdown documents for CRM entries in DuckDB?

To create linked Markdown documents for CRM entries in DuckDB, this skill automatically generates or repairs a human-readable file during entry creation or batch mutations. It registers the document path and links it to the entry_id and parent_object_id for seamless tracking.

How does Markdown content synchronization work with the documents metadata table?

Markdown content synchronization updates or creates the relevant row in the DuckDB documents table as needed. This ensures the human-readable file and the structured metadata remain perfectly consistent during any entry mutation or batch update.

What is the best way to maintain an audit log for CRM document mutations?

The best way to maintain an audit log for CRM document mutations is to append an activity log within the entry document itself. This records changes and history automatically during updates to ensure an auditable CRM workflow.

Does this document management approach enforce file naming and cross-nesting rules?

Yes, this document management approach enforces naming conventions and cross-nesting rules. It ensures documents live under the correct object directory while remaining discoverable and human-readable across standalone object-level and entry documents.

Can I manage standalone object-level documents alongside entry documents in DuckDB?

Yes, you can manage standalone object-level documents alongside entry documents in DuckDB. The documents table maintains a clear distinction between the two types, ensuring both are properly registered and linked.