views-filters

Generate and apply dynamic CRM views and filters across multiple view types.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/aspectrr/denchclaw-workspace --skill views-filters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: views-filters
Source: https://github.com/aspectrr/denchclaw-workspace/tree/main/skills/crm/views-filters
Command: npx skills add https://github.com/aspectrr/denchclaw-workspace --skill views-filters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CRM teams often struggle to derive actionable insights from scattered views and ad-hoc filters, leading to slow decision-making and inconsistent data perspectives.

Core Features & Use Cases

  • Saved views: create and persist complex filter configurations across multiple view types (table, kanban, calendar, timeline, gallery, list) to switch contexts instantly.
  • View settings: per-view-type configuration (kanbanField, calendarDateField, etc.) and automatic column visibility for streamlined dashboards.
  • Data models: leverages object metadata and .object.yaml style projections to drive UI filters, sorting, and field mappings without manual scripting.

Quick Start

Edit the crm/views-filters/.object.yaml to define a new saved view and set active_view.

Frequently Asked Questions about views-filters

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

FAQPage Schema
How do I create and save CRM filters for different view types?

To create saved CRM filters, you edit the crm/views-filters/.object.yaml file to define view configurations and set the active_view. This persists complex filter configurations across table, kanban, and calendar views for instant context switching.

What is the best way to configure kanban and calendar views using object metadata?

Configuring kanban and calendar views requires defining per-view-type settings like kanbanField and calendarDateField within your .object.yaml file. This uses object metadata to drive UI filters and field mappings automatically without manual scripting.

Can I use DuckDB to manage and back my saved CRM views?

Yes, saved CRM views are backed by DuckDB metadata to define view settings, filters, and the active_view state. This allows you to organize data models and projections efficiently for streamlined dashboards.

How do CRM saved views improve data organization and decision-making?

CRM saved views improve data organization by allowing teams to persist complex filter configurations across multiple view types. This eliminates scattered ad-hoc filters, ensuring consistent data perspectives and faster decision-making.

Do I need to manually script UI filters and sorting for CRM data models?

No, you do not need to manually script UI filters or sorting. The system leverages object metadata and .object.yaml style projections to drive UI filters, sorting, and field mappings automatically based on your defined views.