views-filters

Organize saved views and filter rules for CRM objects via .object.yaml projections.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/putrawitama/DenchClaw --skill views-filters-putrawitama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: views-filters
Source: https://github.com/putrawitama/DenchClaw/tree/main/skills/crm/views-filters
Command: npx skills add https://github.com/putrawitama/DenchClaw --skill views-filters-putrawitama

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CRM teams spend time configuring and reconfiguring views and filters across objects. This skill standardizes how saved views, per-view settings, and date rules are defined and reused.

Core Features & Use Cases

  • .object.yaml format and template used to project object metadata
  • View type settings for kanban, calendar, timeline, gallery, and list
  • Saved views and filters for fast, consistent data segmentation across workspace

Quick Start

Create a saved table view for Status and Date filters to surface relevant CRM records.

Frequently Asked Questions about views-filters

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

FAQPage Schema
How do I define saved CRM views and filters using object metadata?

Saved CRM views are organized using .object.yaml projections to define per-view settings, filters, and sorts. This mechanism standardizes data segmentation across lead, contact, and opportunity workflows so teams can reuse configurations across Kanban, calendar, and table views.

What view types can I configure for CRM objects using .object.yaml?

You can configure view type settings for Kanban, calendar, timeline, gallery, and list views using .object.yaml projections. This allows you to apply specific filters and sorts to customize how CRM records are displayed across different workflows.

How do I create a saved table view with Status and Date filters for CRM records?

Create a saved table view by defining Status and Date filter rules within .object.yaml fields. This configuration surfaces relevant CRM records by applying consistent data segmentation and per-view settings across your workspace.

Does this approach to CRM data organization work for lead, contact, and opportunity workflows?

Yes, this approach applies saved views and filter rules specifically to lead, contact, and opportunity workflows. It uses .object.yaml projections to standardize data segmentation across multiple CRM view interfaces.

Why standardize CRM saved views and per-view settings instead of configuring them manually?

Standardizing CRM saved views eliminates repetitive manual configuration across objects. Defining filters, sorts, and date rules via .object.yaml templates ensures fast, consistent data segmentation and reusable per-view settings across the workspace.