asq-local-cache

You can cache stable SFDC metadata locally using a YAML-based persistence file. This local cache acts as a single source of truth for identity and preferences, preventing redundant SFDC queries across multiple skills.

Persisting user configuration and AR numbers is best handled by a centralized local cache file. It provides upsert and lookup utilities, ensuring cross-skill consistency and faster access to stable account data.

Auto-setup for a local YAML metadata cache triggers automatically on first use. It detects your SFDC identity and manager, then creates the initial cache file structure to store preferences and Genie rooms.

Yes, you need the pyyaml dependency to manage a local config cache for ASQ skills. The cache relies on YAML-based persistence to store and retrieve user preferences and metadata efficiently.

Yes, a local cache speeds up Slack and Calendar data retrieval by persisting stable metadata locally. This avoids repeated external lookups and accelerates the overall ASQ lifecycle workflow.

A single source of truth for identity and preferences in ASQ operations is a local YAML cache. It stores SFDC identity, manager details, and user preferences, allowing all ASQ skills to read and write consistently.