crm

Organize CRM workspace setup and governance across DuckDB and the filesystem.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill consolidates workspace fundamentals for CRM—enabling consistent setup, governance, and evolution of objects, fields, entries, and associated documents, views, and workflows across the DuckDB-backed data model and the filesystem projection.

Core Features & Use Cases

  • Centralizes CRM workspace fundamentals (DuckDB schema, object builder patterns, document linkage, and view templates) for consistent onboarding and governance.
  • Enables end-to-end object/field/entry mutations with filesystem projection and verification to keep UI in sync with data and documents.
  • Supports cross-skill guidance for specialized operations (DuckDB operations, documents, reports, actions, and views).

Quick Start

Initialize your CRM workspace by bootstrapping DuckDB schemas, objects, and views, then connect documents and workflows to enable end-to-end CRM operations.

Frequently Asked Questions about crm

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

FAQPage Schema
How do I organize and govern a CRM workspace using DuckDB?

To organize CRM workspace governance using DuckDB, you need a system that centralizes schema setup, object builder patterns, and document linkage. This ensures consistent onboarding and reliable end-to-end workspace evolution across your data and filesystem.

What is the best way to keep CRM UI views in sync with DuckDB data?

Keeping CRM UI views in sync with DuckDB requires enforcing end-to-end three-step mutations: executing SQL, applying filesystem projection, and running verification. This approach auto-regenerates PIVOT views, ensuring the UI reliably matches the underlying data.

How do I set up CRM objects, fields, and entries with filesystem projection?

Setting up CRM objects, fields, and entries with filesystem projection involves applying structured mutations across DuckDB and the filesystem. This process enforces consistent naming and automatically regenerates PIVOT views to maintain reliable UI synchronization.

Does this CRM workspace setup support automated view regeneration?

Yes, this CRM workspace setup supports automated view regeneration. It applies a three-step mutation process involving SQL execution, filesystem projection, and verification, which automatically auto-regenerates PIVOT views to keep your workspace UI consistently updated.

Why does my CRM workspace UI show outdated data after mutating DuckDB objects?

Your CRM workspace UI shows outdated data when mutations skip the necessary filesystem projection and verification steps. By enforcing a complete three-step mutation process, the system auto-regenerates PIVOT views and keeps the UI reliably synchronized with DuckDB.