views-filters

Define CRM object views, filters, and date rules in .object.yaml format.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes and documents the configuration of object-level views, saved views, filters, and date formatting using the .object.yaml contract, enabling consistent UI behavior and easier collaboration across CRM objects.

Core Features & Use Cases

  • enforces .object.yaml structure for CRM objects, ensuring a single source of truth for views and field mappings
  • supports multiple view types (kanban, calendar, timeline, gallery, table/list) with per-view settings
  • enables saved views and filter presets to quickly switch contexts in the UI
  • defines date handling rules, including fallbacks to system timestamps (created_at / updated_at) when custom date fields are absent

Quick Start

Create or update an object's .object.yaml to define default views, settings, and filters, then refresh the UI to apply the saved configuration.

Frequently Asked Questions about views-filters

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

FAQPage Schema
How do I configure saved views and filters for CRM objects in .object.yaml?

To configure saved views and filters for CRM objects, define the view types, per-view settings, and filter presets directly within your .object.yaml file. This establishes a single source of truth for consistent UI behavior and context switching.

What view types are supported when defining CRM object views in .object.yaml?

CRM object views support multiple view types including kanban, calendar, timeline, gallery, and table/list formats. You can specify per-view settings within the .object.yaml structure to customize each layout independently.

How does date formatting work for CRM data models when custom date fields are missing?

Date formatting in CRM data models falls back to system timestamps, specifically created_at or updated_at, when custom date fields are absent. This ensures date handling rules remain functional across all object configurations.

Do I need any external dependencies to standardize object-level views and date rules?

No external dependencies are required to standardize object-level views and date rules. The skill operates independently using the .object.yaml contract to enforce structure for CRM objects without needing additional components.

Why use .object.yaml to manage CRM filter presets instead of configuring views directly in the UI?

Using .object.yaml to manage CRM filter presets provides a single source of truth for field mappings and view configurations, ensuring consistent UI behavior and enabling easier collaboration across different CRM object models.

Can I apply different filter presets to kanban and calendar views within the same CRM object?

Yes, you can apply different filter presets and per-view settings to kanban, calendar, and other view types within the same CRM object by defining them individually in the .object.yaml structure.