skills.rest
himes19
himes19COMMUNITY
Explore all skills by this author →
GitHub

object-builder

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

Updated Apr 12, 2026
Search Tags:#crm#sql#kanban#duckdb#pivot#object-builder
One-click install
npx skills add https://github.com/himes19/pulsevolt-infra --skill object-builder-himes19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: object-builder
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/crm/object-builder
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill object-builder-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables end-to-end creation and configuration of workspace objects for CRM patterns, bridging SQL schema definitions, filesystem metadata, and validation checks with a post-mutation checklist.

Core Features & Use Cases

  • Automates the three-step object workflow: SQL mutation to define the object and fields, filesystem metadata generation (.object.yaml), and verification via a generated DuckDB view.
  • Supports common CRM patterns (e.g., Lead, Task) and automatically updates pivot views, field lists, and optional relations according to best practices.
  • Provides a robust post-mutation checklist to ensure the workspace mirrors DuckDB and is ready for exploration in the sidebar.

Quick Start

Run the three-step workflow to create a CRM object from SQL through filesystem metadata to verification.

Frequently Asked Questions about object-builder

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

FAQPage Schema
How do I create CRM objects from SQL schemas and generate filesystem metadata?▼

To create CRM objects from SQL schemas, you run a three-step workflow: SQL mutation to define fields, filesystem metadata generation as .object.yaml, and verification via a generated DuckDB view.

What is the process for provisioning workspace objects like leads and tasks in DuckDB?▼

Provisioning workspace objects in DuckDB involves applying SQL mutations to define the schema, generating .object.yaml metadata files on disk, and verifying the results against an automatically updated DuckDB pivot view.

How do I configure Kanban patterns and optional relations when building CRM objects?▼

When building CRM objects, Kanban patterns and optional relations are automatically configured during filesystem metadata generation, updating field lists and views according to established CRM best practices.

Do I need any external dependencies to generate .object.yaml files and validate them?▼

No external dependencies are required to generate .object.yaml files and validate them, as the workflow relies entirely on SQL mutations and DuckDB views for self-contained schema definition and verification.

What's the best way to verify CRM object creation and ensure the workspace is ready for exploration?▼

The best way to verify CRM object creation is completing the provided post-mutation checklist, which ensures the workspace accurately mirrors DuckDB views and is fully ready for sidebar exploration.

Why does my CRM object creation workflow require filesystem metadata alongside SQL mutations?▼

CRM object creation requires filesystem metadata alongside SQL mutations because the .object.yaml files persist workspace configurations like fields, views, and Kanban patterns, bridging database schema definitions and application-level validation.

Related Skills

Explore More Software Engineering Skills→
putrawitamaputrawitama
1

duckdb-operations

Initialize DuckDB CRM schemas and CRUD pipelines for objects, fields, and entries.

Community
Advanced
putrawitamaputrawitama
1

crm

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

Community
Advanced
aspectrraspectrr

object-builder

Automate CRM object creation from SQL to filesystem with verification.

Community
Advanced
putrawitamaputrawitama
1

object-builder

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

Community
Advanced