skills.rest
putrawitama
putrawitamaCOMMUNITY
Explore all skills by this author →
GitHub

object-builder

Create CRM objects across SQL and filesystem with .object.yaml generation.

1|1|Updated Mar 31, 2026
Search Tags:#schema#workspace#crm#duckdb#object-builder#pivot-view
One-click install
npx skills add https://github.com/putrawitama/DenchClaw --skill object-builder-putrawitama
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: object-builder
Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/crm/object-builder
Command: npx skills add https://github.com/putrawitama/DenchClaw --skill object-builder-putrawitama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CRM teams face the challenge of consistently creating and wiring CRM objects across SQL definitions and filesystem metadata, with synchronized pivot views and on-disk state.

Core Features & Use Cases

  • Automates object creation across SQL, filesystem, and view layers for CRM entities like lead, task, and company.
  • Auto-generates pivot views and ensures filesystem metadata (.object.yaml) stays in sync with the database schema.
  • Use Case: modeling a new object (e.g., lead) and executing a repeatable workflow to persist schema, generate views, and reflect on-disk state.

Quick Start

Create a new CRM object named lead with its fields and a linked company relation, then generate the .object.yaml and verify the v_lead view.

Frequently Asked Questions about object-builder

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

FAQPage Schema
How do I create and sync CRM objects across SQL and filesystem metadata?▼

To create and sync CRM objects across SQL and filesystem, you can automate object creation, generate .object.yaml metadata, and verify pivot views using DuckDB queries to ensure consistent schema and on-disk state.

What's the best way to generate pivot views for new CRM objects like leads or companies?▼

Generating pivot views for CRM objects like leads or companies is best handled by automating view creation alongside SQL schema persistence, ensuring the database views stay synchronized with filesystem metadata.

How does .object.yaml generation work for CRM schema synchronization?▼

The .object.yaml generation works by automatically creating filesystem metadata that mirrors your SQL database schema, keeping CRM object definitions, fields, and relationships consistently synchronized across both layers.

Can I use DuckDB to verify CRM object views and relationships?▼

Yes, you can use DuckDB to verify CRM object views and relationships by running queries against the generated pivot views, ensuring the newly created objects like leads, tasks, and companies are correctly wired.

Do I need to manually define SQL schemas and filesystem metadata separately for CRM entities?▼

No, you do not need to manually define SQL schemas and filesystem metadata separately, as the workflow automates object creation across both layers, auto-generates pivot views, and persists .object.yaml files with minimal manual steps.

Why does my CRM object schema become out of sync between the database and filesystem?▼

CRM object schemas become out of sync when database updates are not automatically reflected in filesystem metadata, a challenge solved by auto-generating .object.yaml files and pivot views during the object creation workflow.

Related Skills

Explore More Software Engineering Skills→
Snowflake-LabsSnowflake-Labs
1

oracle-connection

Configure and verify Oracle database connections for schema extraction.

Official
Intermediate
himes19himes19

crm

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

Community
Advanced
aspectrraspectrr

object-builder

Automate CRM object creation from SQL to filesystem with verification.

Community
Advanced
himes19himes19

object-builder

Automate CRM object provisioning from SQL schema to .object.yaml files and DuckDB verification.

Community
Advanced