crm

Name: crm
Availability: InStock
Author: himes19

Initialize and govern a DuckDB CRM workspace with synchronized filesystem projections.

Updated Apr 12, 2026

Search Tags:#documents #workspace #crm #views #duckdb #pivot-views #object-modeling

Ready to run

npx skills add https://github.com/himes19/pulsevolt-infra --skill crm-himes19

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: crm
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/crm
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill crm-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Workspace foundational setup for a CRM environment, including startup procedures, naming conventions, and central guidance for how to manage a DuckDB-backed workspace and linked documents.

Core Features & Use Cases

Step-by-step startup guidance for initializing the workspace, including DuckDB setup and schema guidance.
Enforces naming conventions, hierarchical object organization, and triple-alignment (DuckDB objects, filesystem directories, and .object.yaml projections).
Provides a three-step mutation workflow (SQL → filesystem → verify) to keep views, objects, and documents in sync.

Quick Start

Run the 3-step object builder workflow to create your first object and its view.

Frequently Asked Questions about crm

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

FAQPage Schema

How do I set up a CRM workspace in DuckDB?▼

To set up a CRM workspace in DuckDB, follow step-by-step startup guidance that initializes the database schema, establishes naming conventions, and projects hierarchical objects onto the filesystem with .object.yaml files.

What is the three-step mutation workflow for CRM object modeling?▼

The three-step mutation workflow for CRM object modeling executes a SQL transaction, projects changes to the filesystem directories, and verifies alignment to keep DuckDB objects, views, and linked documents synchronized.

How are PIVOT views generated for CRM objects?▼

PIVOT views are generated deterministically by auto-linking relations between modeled objects, ensuring filesystem projections and DuckDB structures stay in sync without manual view construction.

How do I keep filesystem projections in sync with DuckDB objects?▼

Filesystem projections stay in sync with DuckDB objects through enforced triple-alignment, requiring a SQL transaction, a filesystem projection update, and a verification step for every workspace mutation.

What naming conventions are enforced when initializing a CRM workspace?▼

Initializing a CRM workspace enforces naming conventions across hierarchical object organization, ensuring consistent mapping between DuckDB schema objects, filesystem directories, and .object.yaml projections.