denchclaw 2.3.21 → 2.4.0

package/skills/crm/SKILL.md

@@ -13,6 +13,20 @@ All actions should look into / edit and work on `{{WORKSPACE_PATH}}/**` by defau
 
 All your workspace chats and past conversations are stored in `{{WORKSPACE_PATH}}/.openclaw/web-chat/`.
 
+---
+
+## Table of Contents
+
+1. [Workspace Structure](#workspace-structure)
+2. [Startup](#startup)
+3. [workspace_context.yaml (READ-ONLY)](#workspace_contextyaml-read-only)
+4. [Naming Conventions](#naming-conventions)
+5. [Error Handling](#error-handling)
+6. [Critical Reminders](#critical-reminders)
+7. [Child Skills](#child-skills)
+
+---
+
 ## Workspace Structure
 
 ```
@@ -32,266 +46,13 @@ All your workspace chats and past conversations are stored in `{{WORKSPACE_PATH}
   WORKSPACE.md                  # Auto-generated schema summary
 ```
 
-## .object.yaml Format
-
-Every object directory MUST contain a `.object.yaml` file. This is a lightweight metadata projection that the sidebar reads. Generate it from DuckDB after creating or modifying any object.
-
-Template:
-
-```yaml
-id: "<object_id from DuckDB>"
-name: "<object_name>"
-description: "<object_description>"
-icon: "<lucide_icon_name>"
-default_view: "<table|kanban|calendar|timeline|gallery|list>"
-entry_count: <number>
-fields:
-  - name: "Full Name"
-    type: text
-    required: true
-  - name: "Email Address"
-    type: email
-    required: true
-  - name: "Status"
-    type: enum
-    values: ["New", "Contacted", "Qualified", "Converted"]
-  - name: "Assigned To"
-    type: user
-```
-
-### View Type Settings
-
-`.object.yaml` supports a `view_settings` block for configuring how each view type renders. These settings serve as defaults; individual saved views can override them.
-
-```yaml
-view_settings:
-  kanbanField: "Status" # enum field to group kanban columns by
-  calendarDateField: "Due Date" # date field for calendar events
-  calendarEndDateField: "End Date" # optional: end date for multi-day events
-  calendarMode: "month" # day | week | month | year
-  timelineStartField: "Start Date" # date field for timeline bar start
-  timelineEndField: "End Date" # date field for timeline bar end
-  timelineGroupField: "Status" # optional: enum field to group timeline rows
-  timelineZoom: "week" # day | week | month | quarter
-  galleryTitleField: "Name" # text field for gallery card title
-  galleryCoverField: "Image" # optional: field for gallery card cover
-  listTitleField: "Name" # text field for list row title
-  listSubtitleField: "Description" # optional: text field for list row subtitle
-```
-
-If an object has no custom date field, you MUST fall back to system timestamps:
-
-- `created_at` (always available on entries)
-- `updated_at` (always available on entries)
-
-These can be used in `calendarDateField`, `timelineStartField`, `timelineEndField`, filters, sorts, and date-based user requests.
-
-**View types:**
-
-| View Type  | Best for                        | Required settings           |
-| ---------- | ------------------------------- | --------------------------- |
-| `table`    | Spreadsheet-like data editing   | None (default)              |
-| `kanban`   | Status-based boards             | `kanbanField` (enum)        |
-| `calendar` | Date-based entries              | `calendarDateField` (date)  |
-| `timeline` | Gantt charts / project planning | `timelineStartField` (date) |
-| `gallery`  | Visual card grid                | None (auto-detects title)   |
-| `list`     | Simple compact list             | None (auto-detects title)   |
-
-When creating objects with specific use cases, set `default_view` and `view_settings` appropriately:
-
-- Task boards: `default_view: "kanban"` + `view_settings.kanbanField: "Status"`
-- Event calendars: `default_view: "calendar"` + `view_settings.calendarDateField: "Date"`
-- Project timelines: `default_view: "timeline"` + `view_settings.timelineStartField: "Start Date"` + `view_settings.timelineEndField: "End Date"`
-
-### Saved Views and Filters
-
-`.object.yaml` supports a `views` section for saved filter views. These views appear in the UI filter bar and can be created or modified by the agent to immediately change what the user sees (the UI live-reloads via the file watcher).
-
-**Filter operators by field type:**
-
-| Field Type          | Operators                                                                                  |
-| ------------------- | ------------------------------------------------------------------------------------------ |
-| text/richtext/email | contains, not_contains, equals, not_equals, starts_with, ends_with, is_empty, is_not_empty |
-| number              | eq, neq, gt, gte, lt, lte, between, is_empty, is_not_empty                                 |
-| date                | on, before, after, date_between, relative_past, relative_next, is_empty, is_not_empty      |
-| enum                | is, is_not, is_any_of, is_none_of, is_empty, is_not_empty                                  |
-| boolean             | is_true, is_false, is_empty, is_not_empty                                                  |
-| relation/user       | has_any, has_none, has_all, is_empty, is_not_empty                                         |
-| tags                | contains, not_contains, is_empty, is_not_empty                                             |
-
-**System timestamp columns are always available on every object entry**:
-
-- `created_at` (date/time)
-- `updated_at` (date/time)
-
-Treat them as date fields for filtering, sorting, calendar, and timeline operations even when `fields` has no `date` type columns.
-
-**Views template (append to .object.yaml):**
-
-```yaml
-views:
-  - name: "Active deals"
-    view_type: "table"
-    filters:
-      id: root
-      conjunction: and
-      rules:
-        - id: f1
-          field: status
-          operator: is_any_of
-          value:
-            - "Negotiating"
-            - "Proposal sent"
-        - id: f2
-          field: amount
-          operator: gte
-          value: 10000
-    sort:
-      - field: updated_at
-        direction: desc
-    columns:
-      - name
-      - status
-      - amount
-      - assignee
-
-  - name: "Board"
-    view_type: "kanban"
-    settings:
-      kanbanField: "Status"
-
-  - name: "Calendar"
-    view_type: "calendar"
-    settings:
-      calendarDateField: "Due Date"
-      calendarMode: "month"
-
-  - name: "Timeline"
-    view_type: "timeline"
-    settings:
-      timelineStartField: "Start Date"
-      timelineEndField: "End Date"
-      timelineGroupField: "Status"
-      timelineZoom: "week"
-
-  - name: "Overdue"
-    view_type: "table"
-    filters:
-      id: root
-      conjunction: and
-      rules:
-        - id: f1
-          field: due_date
-          operator: before
-          value: today
-        - id: f2
-          field: status
-          operator: is_not
-          value: Done
-
-active_view: "Active deals"
-```
-
-Each saved view can specify:
-
-- `view_type`: `table` | `kanban` | `calendar` | `timeline` | `gallery` | `list` (defaults to object's `default_view`)
-- `settings`: per-view-type configuration (overrides object-level `view_settings`)
-- `filters`: standard filter rules
-- `sort`: sort rules
-- `columns`: visible column names (for table view)
-
-When a user asks for date-based operations (e.g. move from one date to another) and no custom date fields exist, default to `created_at` unless the user explicitly asks for `updated_at`.
-
-**Date format**: All date filter values MUST use ISO 8601 `YYYY-MM-DD` strings (e.g. `"2026-03-01"`). The special value `today` is also supported for `on`, `before`, and `after` operators.
-
-**Date range filter** (`date_between`):
-
-```yaml
-- id: f1
-  field: Due Date
-  operator: date_between
-  value:
-    - "2026-03-01"
-    - "2026-03-31"
-```
-
-**Relative date filters** (e.g. "in the last 7 days"):
-
-```yaml
-- id: f1
-  field: created_at
-  operator: relative_past
-  relativeAmount: 7
-  relativeUnit: days
-```
-
-**OR groups** (match any rule):
-
-```yaml
-filters:
-  id: root
-  conjunction: or
-  rules:
-    - id: f1
-      field: status
-      operator: is
-      value: "Active"
-    - id: f2
-      field: priority
-      operator: is
-      value: "High"
-```
-
-**When the user asks to filter/show/hide entries by natural language**, write the `.object.yaml` with the appropriate views and set `active_view`. The web UI will pick up the change instantly via SSE file watcher. Every rule needs a unique `id` (short alphanumeric string). The root filter group also needs `id: root`.
-
-Generate by querying DuckDB then writing the file:
-
-```bash
-# 1. Query object + fields from DuckDB
-duckdb {{WORKSPACE_PATH}}/workspace.duckdb -json "
-  SELECT o.id, o.name, o.description, o.icon, o.default_view,
-         (SELECT COUNT(*) FROM entries WHERE object_id = o.id) as entry_count
-  FROM objects o WHERE o.name = 'lead'
-"
-duckdb {{WORKSPACE_PATH}}/workspace.duckdb -json "
-  SELECT name, type, required, enum_values FROM fields
-  WHERE object_id = (SELECT id FROM objects WHERE name = 'lead')
-  ORDER BY sort_order
-"
-
-# 2. Write .object.yaml from the query results
-mkdir -p {{WORKSPACE_PATH}}/lead
-cat > {{WORKSPACE_PATH}}/lead/.object.yaml << 'YAML'
-id: "AbCdEfGh..."
-name: "lead"
-description: "Sales leads tracking"
-icon: "user-plus"
-default_view: "table"
-entry_count: 20
-fields:
-  - name: "Full Name"
-    type: text
-    required: true
-  - name: "Email Address"
-    type: email
-    required: true
-  - name: "Status"
-    type: enum
-    values: ["New", "Contacted", "Qualified", "Converted"]
-  - name: "Score"
-    type: number
-  - name: "Notes"
-    type: richtext
-YAML
-```
-
 ## Startup
 
 On every conversation:
 
 1. Read `{{WORKSPACE_PATH}}/workspace_context.yaml` for org context, members, integrations, protected objects. **NEVER modify this file.**
 2. Install duckdb if it doesn't exist: `curl https://install.duckdb.org | sh`
-3. If `{{WORKSPACE_PATH}}/workspace.duckdb` does not exist, initialize it with the schema below.
+3. If `{{WORKSPACE_PATH}}/workspace.duckdb` does not exist, initialize it with the schema in the **duckdb-operations** child skill.
 
 ## workspace_context.yaml (READ-ONLY)
 
@@ -305,478 +66,6 @@ This file is generated by the CRM system and synced via S3. It contains:
 - `defaults`: Default view, date format, naming conventions.
 - `credits`: Current credit balance for enrichment/AI operations.
 
-## DuckDB Schema
-
-Initialize via `exec` with `duckdb {{WORKSPACE_PATH}}/workspace.duckdb`:
-
-```sql
--- Nanoid 32 macro: generates IDs matching the CRM's Supabase nanoid format
-CREATE OR REPLACE MACRO nanoid32() AS (
-  SELECT string_agg(
-    substr('0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz_-',
-      (floor(random() * 64) + 1)::int, 1), '')
-  FROM generate_series(1, 32)
-);
-
-CREATE TABLE IF NOT EXISTS objects (
-  id VARCHAR PRIMARY KEY DEFAULT (nanoid32()),
-  name VARCHAR NOT NULL,
-  description VARCHAR,
-  icon VARCHAR,
-  default_view VARCHAR DEFAULT 'table',
-  parent_document_id VARCHAR,
-  sort_order INTEGER DEFAULT 0,
-  source_app VARCHAR,
-  immutable BOOLEAN DEFAULT false,
-  created_at TIMESTAMPTZ DEFAULT now(),
-  updated_at TIMESTAMPTZ DEFAULT now(),
-  UNIQUE(name)
-);
-
-CREATE TABLE IF NOT EXISTS fields (
-  id VARCHAR PRIMARY KEY DEFAULT (nanoid32()),
-  object_id VARCHAR NOT NULL REFERENCES objects(id) ON DELETE CASCADE,
-  name VARCHAR NOT NULL,
-  description VARCHAR,
-  type VARCHAR NOT NULL,
-  required BOOLEAN DEFAULT false,
-  default_value VARCHAR,
-  related_object_id VARCHAR REFERENCES objects(id) ON DELETE SET NULL,
-  relationship_type VARCHAR,
-  enum_values JSON,
-  enum_colors JSON,
-  enum_multiple BOOLEAN DEFAULT false,
-  sort_order INTEGER DEFAULT 0,
-  created_at TIMESTAMPTZ DEFAULT now(),
-  updated_at TIMESTAMPTZ DEFAULT now(),
-  UNIQUE(object_id, name)
-);
-
-CREATE TABLE IF NOT EXISTS entries (
-  id VARCHAR PRIMARY KEY DEFAULT (nanoid32()),
-  object_id VARCHAR NOT NULL REFERENCES objects(id) ON DELETE CASCADE,
-  sort_order INTEGER DEFAULT 0,
-  created_at TIMESTAMPTZ DEFAULT now(),
-  updated_at TIMESTAMPTZ DEFAULT now()
-);
-
-CREATE TABLE IF NOT EXISTS entry_fields (
-  id VARCHAR PRIMARY KEY DEFAULT (nanoid32()),
-  entry_id VARCHAR NOT NULL REFERENCES entries(id) ON DELETE CASCADE,
-  field_id VARCHAR NOT NULL REFERENCES fields(id) ON DELETE CASCADE,
-  value VARCHAR,
-  created_at TIMESTAMPTZ DEFAULT now(),
-  updated_at TIMESTAMPTZ DEFAULT now(),
-  UNIQUE(entry_id, field_id)
-);
-
-CREATE TABLE IF NOT EXISTS statuses (
-  id VARCHAR PRIMARY KEY DEFAULT (nanoid32()),
-  object_id VARCHAR NOT NULL REFERENCES objects(id) ON DELETE CASCADE,
-  name VARCHAR NOT NULL,
-  color VARCHAR DEFAULT '#94a3b8',
-  sort_order INTEGER DEFAULT 0,
-  is_default BOOLEAN DEFAULT false,
-  created_at TIMESTAMPTZ DEFAULT now(),
-  updated_at TIMESTAMPTZ DEFAULT now(),
-  UNIQUE(object_id, name)
-);
-
-CREATE TABLE IF NOT EXISTS documents (
-  id VARCHAR PRIMARY KEY DEFAULT (nanoid32()),
-  title VARCHAR DEFAULT 'Untitled',
-  icon VARCHAR,
-  cover_image VARCHAR,
-  file_path VARCHAR NOT NULL UNIQUE,
-  parent_id VARCHAR REFERENCES documents(id) ON DELETE CASCADE,
-  parent_object_id VARCHAR REFERENCES objects(id) ON DELETE CASCADE,
-  sort_order INTEGER DEFAULT 0,
-  is_published BOOLEAN DEFAULT false,
-  created_at TIMESTAMPTZ DEFAULT now(),
-  updated_at TIMESTAMPTZ DEFAULT now()
-);
-
-INSTALL fts; LOAD fts;
-```
-
-### ALL ID fields must be a nanoid ID.
-
-## Auto-Generated Views
-
-After every object or field mutation, regenerate the PIVOT view for each affected object. Views are stored queries (zero data duplication) that make the EAV pattern invisible:
-
-```sql
--- Example: auto-generated view for "leads" object
-CREATE OR REPLACE VIEW v_leads AS
-PIVOT (
-  SELECT e.id as entry_id, e.created_at, e.updated_at,
-         f.name as field_name, ef.value
-  FROM entries e
-  JOIN entry_fields ef ON ef.entry_id = e.id
-  JOIN fields f ON f.id = ef.field_id
-  WHERE e.object_id = (SELECT id FROM objects WHERE name = 'leads')
-) ON field_name USING first(value);
-```
-
-Naming convention: `v_{object_name}` (e.g., `v_leads`, `v_companies`, `v_people`).
-
-Now query like a normal table:
-
-```sql
-SELECT * FROM v_leads WHERE "Status" = 'New' ORDER BY created_at DESC LIMIT 50;
-SELECT "Status", COUNT(*) FROM v_leads GROUP BY "Status";
-SELECT * FROM v_leads WHERE "Email Address" LIKE '%@gmail.com';
-```
-
-## SQL Operations Reference
-
-All operations use `exec` with `duckdb {{WORKSPACE_PATH}}/workspace.duckdb`. Batch related SQL in a single exec call with transactions.
-
-### Create Object
-
-```sql
-INSERT INTO objects (name, description, icon, default_view)
-VALUES ('lead', 'Sales leads tracking', 'user-plus', 'table')
-ON CONFLICT (name) DO NOTHING RETURNING *;
-```
-
-### Create Fields
-
-```sql
-INSERT INTO fields (object_id, name, type, required, sort_order)
-VALUES
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Full Name', 'text', true, 0),
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Email Address', 'email', true, 1),
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Phone Number', 'phone', false, 2)
-ON CONFLICT (object_id, name) DO NOTHING;
-```
-
-### Create Enum Field
-
-```sql
-INSERT INTO fields (object_id, name, type, enum_values, enum_colors, sort_order)
-VALUES (
-  (SELECT id FROM objects WHERE name = 'lead'), 'Status', 'enum',
-  '["New","Contacted","Qualified","Converted"]'::JSON,
-  '["#94a3b8","#3b82f6","#f59e0b","#22c55e"]'::JSON, 3
-) ON CONFLICT (object_id, name) DO NOTHING;
-```
-
-### Create Entry with Field Values
-
-```sql
-BEGIN TRANSACTION;
-INSERT INTO entries (object_id) VALUES ((SELECT id FROM objects WHERE name = 'lead')) RETURNING id;
--- Use the returned entry id:
-INSERT INTO entry_fields (entry_id, field_id, value) VALUES
-  ('<entry_id>', (SELECT id FROM fields WHERE object_id = (SELECT id FROM objects WHERE name = 'lead') AND name = 'Full Name'), 'Jane Smith'),
-  ('<entry_id>', (SELECT id FROM fields WHERE object_id = (SELECT id FROM objects WHERE name = 'lead') AND name = 'Email Address'), 'jane@example.com'),
-  ('<entry_id>', (SELECT id FROM fields WHERE object_id = (SELECT id FROM objects WHERE name = 'lead') AND name = 'Status'), 'New');
-COMMIT;
-```
-
-### Search Entries (via view)
-
-```sql
--- Simple search
-SELECT * FROM v_leads WHERE "Full Name" ILIKE '%john%';
-
--- Filter by field
-SELECT * FROM v_leads WHERE "Status" = 'New' ORDER BY created_at DESC;
-
--- Aggregation
-SELECT "Status", COUNT(*) as count FROM v_leads GROUP BY "Status";
-
--- Pagination
-SELECT * FROM v_leads ORDER BY created_at DESC LIMIT 20 OFFSET 0;
-```
-
-### Update Entry
-
-```sql
-INSERT INTO entry_fields (entry_id, field_id, value)
-VALUES ('<entry_id>', (SELECT id FROM fields WHERE object_id = '<obj_id>' AND name = 'Status'), 'Qualified')
-ON CONFLICT (entry_id, field_id) DO UPDATE SET value = excluded.value, updated_at = now();
-```
-
-### Delete (with cascade)
-
-```sql
--- Delete entry (cascades to entry_fields)
-DELETE FROM entries WHERE id = '<entry_id>';
-
--- Delete field (cascades to entry_fields)
-DELETE FROM fields WHERE id = '<field_id>';
-
--- Delete object (cascades to fields, entries, entry_fields) — check immutable first!
-DELETE FROM objects WHERE id = '<obj_id>' AND immutable = false;
-```
-
-### Bulk Import from CSV
-
-```sql
-COPY entries FROM '{{WORKSPACE_PATH}}/exports/import.csv' (AUTO_DETECT true);
-```
-
-### Export to CSV
-
-```sql
-COPY (SELECT * FROM v_leads) TO '{{WORKSPACE_PATH}}/exports/leads.csv' (HEADER true);
-```
-
-## Full Workflow: Create CRM Structure in One Shot
-
-EVERY object creation MUST complete ALL THREE steps below. Never stop after the SQL.
-
-**Step 1 — SQL: Create object + fields + view** (single exec call):
-
-```sql
-BEGIN TRANSACTION;
-
--- 1a. Create object
-INSERT INTO objects (name, description, icon, default_view)
-VALUES ('lead', 'Sales leads tracking', 'user-plus', 'table')
-ON CONFLICT (name) DO NOTHING;
-
--- 1b. Create all fields
-INSERT INTO fields (object_id, name, type, required, sort_order) VALUES
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Full Name', 'text', true, 0),
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Email Address', 'email', true, 1),
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Phone Number', 'phone', false, 2),
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Score', 'number', false, 4),
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Notes', 'richtext', false, 6)
-ON CONFLICT (object_id, name) DO NOTHING;
-
-INSERT INTO fields (object_id, name, type, enum_values, enum_colors, sort_order) VALUES
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Status', 'enum',
-   '["New","Contacted","Qualified","Converted"]'::JSON,
-   '["#94a3b8","#3b82f6","#f59e0b","#22c55e"]'::JSON, 3),
-  ((SELECT id FROM objects WHERE name = 'lead'), 'Source', 'enum',
-   '["Website","Referral","Cold Call","Social"]'::JSON, NULL, 5)
-ON CONFLICT (object_id, name) DO NOTHING;
-
--- 1c. MANDATORY: auto-generate PIVOT view
-CREATE OR REPLACE VIEW v_lead AS
-PIVOT (
-  SELECT e.id as entry_id, e.created_at, e.updated_at,
-         f.name as field_name, ef.value
-  FROM entries e
-  JOIN entry_fields ef ON ef.entry_id = e.id
-  JOIN fields f ON f.id = ef.field_id
-  WHERE e.object_id = (SELECT id FROM objects WHERE name = 'lead')
-) ON field_name USING first(value);
-
-COMMIT;
-```
-
-**Step 2 — Filesystem: Create object directory + .object.yaml** (exec call):
-
-```bash
-mkdir -p {{WORKSPACE_PATH}}/lead
-
-# Query the object metadata from DuckDB to build .object.yaml
-OBJ_ID=$(duckdb {{WORKSPACE_PATH}}/workspace.duckdb -noheader -list "SELECT id FROM objects WHERE name = 'lead'")
-ENTRY_COUNT=$(duckdb {{WORKSPACE_PATH}}/workspace.duckdb -noheader -list "SELECT COUNT(*) FROM entries WHERE object_id = '$OBJ_ID'")
-
-cat > {{WORKSPACE_PATH}}/lead/.object.yaml << 'YAML'
-id: "<use actual $OBJ_ID>"
-name: "lead"
-description: "Sales leads tracking"
-icon: "user-plus"
-default_view: "table"
-entry_count: <use actual $ENTRY_COUNT>
-fields:
-  - name: "Full Name"
-    type: text
-    required: true
-  - name: "Email Address"
-    type: email
-    required: true
-  - name: "Phone Number"
-    type: phone
-  - name: "Status"
-    type: enum
-    values: ["New", "Contacted", "Qualified", "Converted"]
-  - name: "Score"
-    type: number
-  - name: "Source"
-    type: enum
-    values: ["Website", "Referral", "Cold Call", "Social"]
-  - name: "Notes"
-    type: richtext
-YAML
-```
-
-**Step 3 — Verify**: Confirm both the view and filesystem exist:
-
-```bash
-# Verify view works
-duckdb {{WORKSPACE_PATH}}/workspace.duckdb "SELECT COUNT(*) FROM v_lead"
-# Verify .object.yaml exists
-cat {{WORKSPACE_PATH}}/lead/.object.yaml
-```
-
-## Kanban Boards
-
-When creating task/board objects, use `default_view = 'kanban'` and auto-create Status + Assigned To fields. Set `view_settings.kanbanField` to the enum field that defines columns. Remember: ALL THREE STEPS are required.
-
-**Step 1 — SQL:**
-
-```sql
-BEGIN TRANSACTION;
-INSERT INTO objects (name, description, icon, default_view)
-VALUES ('task', 'Task tracking board', 'check-square', 'kanban')
-ON CONFLICT (name) DO NOTHING;
-
--- Auto-create Status field with kanban-appropriate values
-INSERT INTO fields (object_id, name, type, enum_values, enum_colors, sort_order)
-VALUES ((SELECT id FROM objects WHERE name = 'task'), 'Status', 'enum',
-  '["In Queue","In Progress","Done"]'::JSON,
-  '["#94a3b8","#3b82f6","#22c55e"]'::JSON, 0)
-ON CONFLICT (object_id, name) DO NOTHING;
-
--- Auto-create Assigned To field (user type)
-INSERT INTO fields (object_id, name, type, sort_order)
-VALUES ((SELECT id FROM objects WHERE name = 'task'), 'Assigned To', 'user', 1)
-ON CONFLICT (object_id, name) DO NOTHING;
-
--- Auto-create default statuses
-INSERT INTO statuses (object_id, name, color, sort_order, is_default) VALUES
-  ((SELECT id FROM objects WHERE name = 'task'), 'In Queue', '#94a3b8', 0, true),
-  ((SELECT id FROM objects WHERE name = 'task'), 'In Progress', '#3b82f6', 1, false),
-  ((SELECT id FROM objects WHERE name = 'task'), 'Done', '#22c55e', 2, false)
-ON CONFLICT (object_id, name) DO NOTHING;
-
-CREATE OR REPLACE VIEW v_task AS
-PIVOT (
-  SELECT e.id as entry_id, e.created_at, e.updated_at,
-         f.name as field_name, ef.value
-  FROM entries e
-  JOIN entry_fields ef ON ef.entry_id = e.id
-  JOIN fields f ON f.id = ef.field_id
-  WHERE e.object_id = (SELECT id FROM objects WHERE name = 'task')
-) ON field_name USING first(value);
-
-COMMIT;
-```
-
-**Step 2 — Filesystem (MANDATORY):**
-
-```bash
-mkdir -p {{WORKSPACE_PATH}}/task
-cat > {{WORKSPACE_PATH}}/task/.object.yaml << 'YAML'
-id: "<query from DuckDB>"
-name: "task"
-description: "Task tracking board"
-icon: "check-square"
-default_view: "kanban"
-entry_count: 0
-view_settings:
-  kanbanField: "Status"
-fields:
-  - name: "Status"
-    type: enum
-    values: ["In Queue", "In Progress", "Done"]
-  - name: "Assigned To"
-    type: user
-YAML
-```
-
-**Step 3 — Verify:** `duckdb {{WORKSPACE_PATH}}/workspace.duckdb "SELECT COUNT(*) FROM v_task"` and `cat {{WORKSPACE_PATH}}/task/.object.yaml`.
-
-## Field Types Reference
-
-| Type     | Description                           | Storage                   | Query Cast  |
-| -------- | ------------------------------------- | ------------------------- | ----------- |
-| text     | General text, names, descriptions     | VARCHAR                   | none        |
-| email    | Email addresses (validated)           | VARCHAR                   | none        |
-| phone    | Phone numbers (normalized)            | VARCHAR                   | none        |
-| number   | Numeric values (prices, scores)       | VARCHAR                   | `::NUMERIC` |
-| boolean  | Yes/no flags                          | "true"/"false"            | `= 'true'`  |
-| date     | ISO 8601 dates                        | VARCHAR                   | `::DATE`    |
-| richtext | Rich text for Notes fields            | VARCHAR                   | none        |
-| user     | Member ID from workspace_context.yaml | VARCHAR                   | none        |
-| enum     | Dropdown with predefined values       | VARCHAR                   | none        |
-| relation | Link to entry in another object       | VARCHAR (entry ID)        | none        |
-| tags     | Free-form string array (labels, tags) | VARCHAR (JSON array str)  | none        |
-
-### System Timestamp Columns (Always Present)
-
-Every entry row always has:
-
-- `created_at` (TIMESTAMPTZ in `entries`)
-- `updated_at` (TIMESTAMPTZ in `entries`)
-
-Important:
-
-- These are system columns, so they are NOT listed in the `fields` table.
-- If `SELECT * FROM fields` shows no date fields, you still have `created_at` and `updated_at`.
-- Use these as date fallbacks for calendar/timeline views and date-based natural language requests.
-
-**user fields**: Resolve member name to ID from `workspace_context.yaml` `members` list BEFORE inserting. User fields store IDs like `usr_abc123`, NOT names.
-
-**enum fields**: Field definition stores `enum_values` as JSON array. Entry stores the selected value string. `enum_multiple = true` for multi-select (value stored as JSON array string).
-
-**relation fields**: Field stores `related_object_id` and `relationship_type`. Entry stores the related entry ID. `many_to_one` for single select, `many_to_many` for multi-select (JSON array of IDs).
-
-**tags fields**: Free-form string arrays for labels, domains, skills, keywords, etc. Value stored as JSON array string: `'["tag1","tag2","tag3"]'`. No predefined values — users can type any value. Displayed as removable chips in the UI.
-
-## CRM Patterns
-
-### Contact/Customer
-
-- Full Name (text, required), Email Address (email, required), Phone Number (phone), Company (relation to company object), Notes (richtext)
-- Universal pattern for clients, customers, patients, members
-
-### Lead/Prospect
-
-- Full Name (text, required), Email Address (email, required), Phone Number (phone), Status (enum: New/Contacted/Qualified/Converted), Source (enum: Website/Referral/Cold Call/Social), Score (number), Assigned To (user), Notes (richtext)
-- Sales, legal intake, real estate prospects
-
-### Company/Organization
-
-- Company Name (text, required), Industry (enum), Website (text), Type (enum: Client/Partner/Vendor), Relationship Status (enum), Notes (richtext)
-- B2B relationships, vendor management
-
-### Deal/Opportunity
-
-- Deal Name (text, required), Amount (number), Stage (enum: Discovery/Proposal/Negotiation/Closed Won/Closed Lost), Close Date (date), Probability (number), Primary Contact (relation), Assigned To (user), Notes (richtext)
-- Sales pipeline, project bids
-
-### Case/Project
-
-- Case Number (text, required), Title (text, required), Client (relation), Status (enum: Open/In Progress/Closed), Priority (enum: Low/Medium/High/Urgent), Due Date (date), Assigned To (user), Notes (richtext)
-- Legal cases, client projects
-
-### Property/Asset
-
-- Address (text, required), Property Type (enum), Price (number), Status (enum: Available/Under Contract/Sold), Square Footage (number), Bedrooms (number), Notes (richtext)
-- Real estate listings, asset management
-
-### Task/Activity (use kanban)
-
-- Title (text, required), Description (text), Assigned To (user), Due Date (date), Status (enum: In Queue/In Progress/Done), Priority (enum: Low/Medium/High), Notes (richtext)
-- Use `default_view = 'kanban'` — auto-creates Status and Assigned To fields
-
-## Document Management
-
-Documents are markdown files in `{{WORKSPACE_PATH}}/**`. The DuckDB `documents` table tracks metadata only; the `.md` file IS the content.
-
-### Create Document
-
-1. Write the `.md` file: `write {{WORKSPACE_PATH}}/projects/roadmap.md`
-2. Insert metadata into DuckDB:
-
-```sql
-INSERT INTO documents (title, icon, file_path, parent_id, sort_order)
-VALUES ('Roadmap', 'map', 'projects/roadmap.md', '<parent_doc_id>', 0);
-```
-
-### Cross-Nesting
-
-- **Document under Object**: Set `parent_object_id` on the document. Place `.md` file inside the object's directory.
-- **Object under Document**: Set `parent_document_id` on the object. Place object directory inside the document's directory.
-
 ## Naming Conventions
 
 - **Object names**: singular, lowercase, one word ("lead" not "Leads")
@@ -803,227 +92,61 @@ Never rename partially. If you can't complete all steps, don't start the rename
 - Protected object deletion: check `immutable` column AND `protected_objects` in `workspace_context.yaml`. NEVER delete protected objects.
 - Field type change: warn user before changing type on field with existing data.
 - Missing required fields: validate before INSERT, report which fields are missing.
-
-## Post-Mutation Checklist (MANDATORY)
-
-You MUST complete ALL steps below after ANY schema mutation (create/update/delete object, field, or entry). Do NOT skip any step. Do NOT consider the operation complete until all steps are done.
-
-### After creating or modifying an OBJECT or its FIELDS:
-
-- [ ] `CREATE OR REPLACE VIEW v_{object_name}` — regenerate the PIVOT view
-- [ ] `mkdir -p {{WORKSPACE_PATH}}/{object_name}/` — create the object directory
-- [ ] Write `{{WORKSPACE_PATH}}/{object_name}/.object.yaml` — metadata projection with id, name, description, icon, default_view, entry_count, and full field list
-- [ ] If object has a `parent_document_id`, place directory inside the parent document's directory
-- [ ] Update `WORKSPACE.md` if it exists
-
-### After adding or updating ENTRIES:
-
-- [ ] Update `entry_count` in the corresponding `.object.yaml`
-- [ ] Verify the view returns correct data: `SELECT * FROM v_{object} LIMIT 5`
-
-### After deleting an OBJECT:
-
-- [ ] `DROP VIEW IF EXISTS v_{object_name}` — remove the view
-- [ ] `rm -rf {{WORKSPACE_PATH}}/{object_name}/` — remove the directory (unless it contains nested documents that need relocating)
-- [ ] Update `WORKSPACE.md`
-
-### After creating or modifying a DOCUMENT:
-
-- [ ] Write the `.md` file to the correct path in `{{WORKSPACE_PATH}}/**`
-- [ ] `INSERT INTO documents` — ensure metadata row exists with correct `file_path`, `parent_id`, or `parent_object_id`
-
-These steps ensure the filesystem always mirrors DuckDB. The sidebar depends on `.object.yaml` files — if they are missing, objects will not appear.
-
-## Report Generation (Analytics / Charts)
-
-Reports are JSON config files (`.report.json`) that the web app renders as live interactive dashboards using Recharts. The agent creates these files to give the user visual analytics over their CRM data.
-
-### Report file format
-
-Store reports as `.report.json` files in `{{WORKSPACE_PATH}}/**` (wherever appropriate / create directories if you need for better structure). The JSON schema:
-
-```json
-{
-  "version": 1,
-  "title": "Report Title",
-  "description": "Brief description of what this report shows",
-  "panels": [
-    {
-      "id": "unique-panel-id",
-      "title": "Panel Title",
-      "type": "bar",
-      "sql": "SELECT ... FROM v_{object} ...",
-      "mapping": { "xAxis": "column_name", "yAxis": ["value_column"] },
-      "size": "half"
-    }
-  ],
-  "filters": [
-    {
-      "id": "filter-id",
-      "type": "dateRange",
-      "label": "Date Range",
-      "column": "created_at"
-    }
-  ]
-}
-```
-
-### Chart types
-
-| Type      | Best for                     | Required mapping                |
-| --------- | ---------------------------- | ------------------------------- |
-| `bar`     | Comparing categories         | `xAxis`, `yAxis`                |
-| `line`    | Trends over time             | `xAxis`, `yAxis`                |
-| `area`    | Volume trends                | `xAxis`, `yAxis`                |
-| `pie`     | Distribution/share           | `nameKey`, `valueKey`           |
-| `donut`   | Distribution (with center)   | `nameKey`, `valueKey`           |
-| `radar`   | Multi-dimensional comparison | `xAxis` (or `nameKey`), `yAxis` |
-| `scatter` | Correlation                  | `xAxis`, `yAxis`                |
-| `funnel`  | Pipeline/conversion          | `nameKey`, `valueKey`           |
-
-### Panel sizes
-
-- `"full"` — spans full width (6 columns)
-- `"half"` — spans half width (3 columns) — **default**
-- `"third"` — spans one third (2 columns)
-
-### Filter types
-
-- `dateRange` — date picker (from/to), filters on `column`
-- `select` — single-select dropdown, needs `sql` to fetch options
-- `multiSelect` — multi-select chips, needs `sql` to fetch options
-- `number` — min/max numeric range
-
-### SQL query rules for reports
-
-- Always use the auto-generated `v_{object}` PIVOT views — never raw EAV queries
-- SQL must be SELECT-only (no INSERT/UPDATE/DELETE)
-- Cast numeric fields: `"Amount"::NUMERIC` or `CAST("Amount" AS NUMERIC)`
-- Use `DATE_TRUNC('month', created_at)` for time-series grouping
-- Always include `ORDER BY` for consistent chart rendering
-- Use aggregate functions: `COUNT(*)`, `SUM(...)`, `AVG(...)`, `MIN(...)`, `MAX(...)`
-
-### Example reports
-
-**Pipeline Funnel:**
-
-```json
-{
-  "version": 1,
-  "title": "Deal Pipeline",
-  "description": "Deal count and value by stage",
-  "panels": [
-    {
-      "id": "deals-by-stage",
-      "title": "Deals by Stage",
-      "type": "funnel",
-      "sql": "SELECT \"Stage\", COUNT(*) as count FROM v_deal GROUP BY \"Stage\" ORDER BY count DESC",
-      "mapping": { "nameKey": "Stage", "valueKey": "count" },
-      "size": "half"
-    },
-    {
-      "id": "revenue-by-stage",
-      "title": "Revenue by Stage",
-      "type": "bar",
-      "sql": "SELECT \"Stage\", SUM(\"Amount\"::NUMERIC) as total FROM v_deal GROUP BY \"Stage\" ORDER BY total DESC",
-      "mapping": { "xAxis": "Stage", "yAxis": ["total"] },
-      "size": "half"
-    }
-  ],
-  "filters": [
-    { "id": "date", "type": "dateRange", "label": "Created", "column": "created_at" },
-    {
-      "id": "assignee",
-      "type": "select",
-      "label": "Assigned To",
-      "sql": "SELECT DISTINCT \"Assigned To\" as value FROM v_deal WHERE \"Assigned To\" IS NOT NULL",
-      "column": "Assigned To"
-    }
-  ]
-}
-```
-
-**Contact Growth:**
-
-```json
-{
-  "version": 1,
-  "title": "Contact Growth",
-  "description": "New contacts over time",
-  "panels": [
-    {
-      "id": "growth-trend",
-      "title": "Contacts Over Time",
-      "type": "area",
-      "sql": "SELECT DATE_TRUNC('month', created_at) as month, COUNT(*) as count FROM v_people GROUP BY month ORDER BY month",
-      "mapping": { "xAxis": "month", "yAxis": ["count"] },
-      "size": "full"
-    }
-  ]
-}
-```
-
-### Inline chat reports
-
-When a user asks for analytics in chat (without explicitly asking to save a report), emit the report JSON inside a fenced code block with language `report-json`. The web UI will render interactive charts inline:
-
-````
-Here's your pipeline analysis:
-
-```report-json
-{"version":1,"title":"Deals by Stage","panels":[{"id":"p1","title":"Deal Count","type":"bar","sql":"SELECT \"Stage\", COUNT(*) as count FROM v_deal GROUP BY \"Stage\" ORDER BY count DESC","mapping":{"xAxis":"Stage","yAxis":["count"]},"size":"full"}]}
-```
-
-Most deals are currently in the Discovery stage.
-````
-
-The user can then "Pin" the inline report to save it as a `.report.json` file.
-
-### Post-report checklist
-
-After creating a `.report.json` file:
-
-- [ ] Verify the report JSON is valid and all SQL queries work: test each panel's SQL individually
-- [ ] Choose which directory the report should be created in `{{WORKSPACE_PATH}}` based on the context of the conversation, if nothing vert relevant, create/use the `{{WORKSPACE_PATH}}/reports/` directory.
-- [ ] Write the file: `{{WORKSPACE_PATH}}/**/{slug}.report.json`
-- [ ] Tell the user they can view it in the workspace sidebar under whichever directory it was rightfully placed in based on the context.
-
-### Choosing the right chart type
-
-- **Comparing categories** (status breakdown, source distribution): `bar` or `pie`
-- **Time series** (growth, trends, revenue over time): `line` or `area`
-- **Pipeline/conversion** (deal stages, lead funnel): `funnel`
-- **Distribution/proportion** (market share, segment split): `pie` or `donut`
-- **Multi-metric comparison** (performance scores): `radar`
-- **Correlation** (price vs. size, score vs. revenue): `scatter`
-- When in doubt, `bar` is the safest default
+- **DuckDB SQL errors**: See the "Common DuckDB Pitfalls" section in the **duckdb-operations** child skill. The most frequent causes: unquoted field names with spaces (use `"Full Name"` not `Full Name`), wrong transaction syntax (`BEGIN TRANSACTION` not `BEGIN`), unescaped single quotes, and PIVOT views without the `IN (...)` field list.
+- **"Script not found" on action buttons**: The `.actions/` directory and/or script files were not created. See the **actions** child skill post-creation checklist.
 
 ## Critical Reminders
 
 - Handle the ENTIRE CRM operation from analysis to SQL execution to filesystem projection to summary
 - **NEVER SKIP FILESYSTEM PROJECTION**: After creating/modifying any object, you MUST create/update `{object}/.object.yaml` in workspace AND the `v_{object}` view. If you skip this, the object will be invisible in the sidebar. This is NOT optional.
-- **THREE STEPS, EVERY TIME**: (1) SQL transaction, (2) filesystem projection (.object.yaml + directory), (3) verify. An operation is NOT complete until all three are done.
+- **THREE STEPS, EVERY TIME**: (1) SQL transaction, (2) filesystem projection (.object.yaml + directory), (3) verify. An operation is NOT complete until all three are done. See **object-builder** child skill.
 - Always check existing data before creating (`SELECT` before `INSERT`, or `ON CONFLICT`)
 - Use views (`v_{object}`) for all reads — never write raw PIVOT queries for search
 - Never assume field names — verify with `SELECT * FROM fields WHERE object_id = ?`
 - **DATE FALLBACK**: If an object has no custom `date` field, use `created_at`/`updated_at` (from `entries`) instead of saying there are no date fields.
 - Extract ALL data from user messages — don't leave information unused
-- **REPORTS vs DOCUMENTS**: When the user asks for "reports", "analytics", "charts", "graphs", "metrics", "insights", or "breakdown" — use `.report.json` format (see Report Generation section above), NOT markdown. Only use markdown `.md` for SOPs, guides, notes, and prose documents. Reports render as interactive Recharts dashboards; markdown does not.
-- **INLINE CHART ARTIFACTS**: When answering analytics questions in chat, ALWAYS emit a `report-json` fenced code block so the UI renders interactive charts inline. Do NOT describe data in plain text when you can show it as a chart.
+- **REPORTS vs DOCUMENTS**: When the user asks for "reports", "analytics", "charts", "graphs", "metrics", "insights", or "breakdown" — use `.report.json` format (see **reports** child skill), NOT markdown. Only use markdown `.md` for SOPs, guides, notes, and prose documents.
+- **INLINE CHART ARTIFACTS**: When answering analytics questions in chat, ALWAYS emit a `report-json` fenced code block so the UI renders interactive charts inline.
 - **NOTES**: Always use type "richtext" for Notes fields
 - **USER FIELDS**: Resolve member name to ID from `workspace_context.yaml` BEFORE inserting
 - **ENUM FIELDS**: Use type "enum" with `enum_values` JSON array
-- **RELATION FIELDS**: Use type "relation" with `related_object_id`
+- **RELATION FIELDS (PROACTIVE)**: Use type "relation" with `related_object_id` and `relationship_type`. **ALWAYS create relation fields when objects are obviously linked** — don't wait for the user to ask. Examples: people→company, deal→contact, deal→company, task→project, case→client, invoice→company. If you're creating object B and object A exists, ask: "Would B entries reference A entries?" If yes, add a relation. Relation fields must be created via SQL (not the API). See **object-builder** child skill for the full relation pattern and common relation pairs.
 - **TAGS FIELDS**: Use type "tags" for free-form string arrays. Value stored as `'["tag1","tag2"]'`
+- **URL FIELDS**: Use type "url" for website addresses and links
+- **FILE FIELDS**: Use type "file" for file attachments (stores file path or URL)
+- **ACTION FIELDS (CRITICAL — READ CAREFULLY)**: Use type `"action"` with `default_value` containing `{"actions":[...]}` JSON. Action fields are excluded from PIVOT views. **When using file-based scripts (`scriptPath`), you MUST also: (1) `mkdir -p` the `.actions/` directory, (2) write every script file referenced in the config, (3) update `.object.yaml` with `action_config`.** If you skip creating the script files, the button will render but clicking it shows "Script not found". See **actions** child skill for the mandatory post-creation checklist and a complete end-to-end example.
 - **KANBAN**: Use `default_view = 'kanban'`, set `view_settings.kanbanField: "Status"`, auto-create Status and Assigned To fields
 - **CALENDAR**: Use `default_view = 'calendar'`, set `view_settings.calendarDateField` to the date field
 - **TIMELINE**: Use `default_view = 'timeline'`, set `view_settings.timelineStartField` and optionally `timelineEndField`
 - **VIEW TYPES**: Valid `default_view` values: `table`, `kanban`, `calendar`, `timeline`, `gallery`, `list`
+- **FILTER REQUESTS**: When the user asks to filter, narrow, show only, hide, segment, or otherwise change which entries appear in the UI, default to creating/updating a saved view in `.object.yaml` and set `active_view` so the UI updates immediately. Do this even if they did not explicitly ask to "create a view", unless they clearly want a one-off answer only.
+- **VIEW COLUMNS**: For saved table views, omit `columns` by default. If `columns` is not present, the table uses the default/all columns. `views[].columns` controls visibility only, not display order. Only write `columns` when the user explicitly asks for a specific visible subset.
+- **COLUMN REORDERING**: If the user asks to reorder table columns, do not try to encode that in `views[].columns`. Update the object's field `sort_order` in DuckDB, then regenerate `.object.yaml` so its top-level `fields` list matches the new schema order.
+- **COLUMN WIDTHS**: If the user asks to resize or set column widths, set `view_settings.column_widths` (object-level) or `views[].column_widths` (per-view) as a map of field name to pixel width (e.g. `column_widths: { "Full Name": 250, "Status": 150 }`). The UI also auto-persists widths when columns are drag-resized.
 - **PROTECTED OBJECTS**: Never delete objects listed in `workspace_context.yaml` `protected_objects`
-- **ONE EXEC CALL**: Batch related SQL in a single transaction — this is the whole point
+- **DUCKDB QUOTING**: Field names with spaces MUST be double-quoted in SQL: `"Full Name"`, `"Email Address"`, etc. Without quotes, DuckDB treats them as separate identifiers and the query fails.
+- **PIVOT VIEWS**: Always use the `IN (...)` clause to list field names explicitly. Exclude action fields with `AND f.type != 'action'`. See **duckdb-operations** child skill.
+- **ONE EXEC CALL**: Batch related SQL in a single transaction
 - **workspace_context.yaml**: READ-ONLY. Never modify. Data flows from the CRM UI only.
 - **Source of truth**: DuckDB for all structured data. Filesystem for document content and navigation tree. Never duplicate entry data to the filesystem.
 - **ENTRY COUNT**: After adding entries, update `entry_count` in `.object.yaml`.
-- **NAME CONSISTENCY**: The DuckDB `objects.name`, the filesystem directory name, and `.object.yaml` `name` MUST be identical. A mismatch between ANY of these three will break the UI. Before finishing any object creation or modification, verify: `objects.name == directory_name == yaml.name`. See "Renaming / Moving Objects" under Naming Conventions.
+- **NAME CONSISTENCY**: The DuckDB `objects.name`, the filesystem directory name, and `.object.yaml` `name` MUST be identical. See Naming Conventions above.
 - **NEVER POLLUTE THE WORKSPACE**: Always keep cleaning / organising the workspace to something more nicely structured. Always look out for bloat and too many random files scattered around everywhere for no reason, every time you do any actions in filesystem always try to come up with the most efficient and nice file system structure inside the workspace.
 - **TEMPORARY FILES**: All temporary scripts / code / text / other files as and when needed for processing must go into `tmp/` directory (create it in the workspace if it doesn't exist, only if needed).
+
+---
+
+## Child Skills
+
+This skill covers workspace fundamentals. For specialized operations, see these child skills (all inside the `crm/` skill folder):
+
+| Skill | Path | Covers |
+|-------|------|--------|
+| **DuckDB Operations** | `crm/duckdb-operations/SKILL.md` | DuckDB schema initialization, field types reference, auto-generated PIVOT views, SQL CRUD operations (create/read/update/delete objects, fields, entries), bulk import/export |
+| **Object Builder** | `crm/object-builder/SKILL.md` | Full 3-step workflow (SQL → filesystem → verify), CRM patterns (contact, lead, company, deal, case, property, task), kanban boards, post-mutation checklist, renaming objects |
+| **Views & Filters** | `crm/views-filters/SKILL.md` | `.object.yaml` format and template, view type settings (kanban, calendar, timeline, gallery, list), saved views, filter operators by field type, date format rules |
+| **Documents** | `crm/documents/SKILL.md` | Document management (markdown files), cross-nesting (documents under objects, objects under documents), entry detail pages (optional per-entry markdown) |
+| **Reports** | `crm/reports/SKILL.md` | Report generation (`.report.json` format), chart types (bar, line, area, pie, donut, radar, scatter, funnel), panel sizes, filter types, inline chat reports, post-report checklist |
+| **Actions** | `crm/actions/SKILL.md` | Action field type (`type: "action"`), executable buttons on entries, server-side script execution in any language (JS, Python, bash, etc.), inline JS SDK, NDJSON stdout protocol, environment variable context, bulk parallel execution, action_runs table, UI rendering in table/kanban/entry panel |
+
+All child skills are seeded into the workspace alongside this parent skill and can be read at `{{WORKSPACE_PATH}}/skills/crm/<child>/SKILL.md`.