Total Skills
4
Author Profile: cchrisv
Skills published by cchrisv with real stars/downloads and source-aware metadata.
Total Stars
0
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
flow-well-architected
0
Stars
0
Downloads
0
lwc-well-architected
0
Stars
0
Downloads
0
observing-agentforce
0
Stars
0
Downloads
0
testing-agentforce
0
Stars
0
Downloads
0
Published Skills
flow-well-architected
Nine-principle framework for well-architected Salesforce Flows. Use when: building new flows, reviewing flow architecture, naming flow elements, documenting flow decisions, optimizing flow performance, extracting subflows, adding error handling to flows, planning flow testing strategy, refactoring monolith or spaghetti flows, evaluating flow design quality.
Repository SourceNeeds Review
lwc-well-architected
Atomic design framework for scalable LWC development. Use when: creating new Lightning Web Components, refactoring existing LWC, reviewing LWC code, determining component level (atom/molecule/organism/template/page/utility/flow), enforcing unidirectional data flow, adding accessibility or SLDS compliance, writing LWC Jest tests, migrating god components, or building Flow-reactive screen components.
Repository SourceNeeds Review
observing-agentforce
Analyze production Agentforce agent behavior using session traces and Data Cloud. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries. DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use developing-agentforce); writes or runs test specs (use testing-agentforce); uses sf agent preview for local development iteration; deploys or publishes agents.
Repository SourceNeeds Review
testing-agentforce
Write, run, and analyze structured test suites for Agentforce agents. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric selection, or custom evaluations; interprets test results or diagnoses test failures; asks about batch testing, regression suites, or CI/CD test integration. DO NOT TRIGGER when: user creates, modifies, previews, or debugs .agent files (use developing-agentforce); deploys or publishes agents; writes Agent Script code; uses sf agent preview for development iteration; analyzes production session traces (use observing-agentforce).
Repository SourceNeeds Review