cirra-ai-sf: Salesforce Admin Suite
Orchestrates three independent Salesforce plugins into a unified development workflow. Each plugin works standalone; this meta-skill coordinates them when all three are active.
CRITICAL: Dependency Check on Session Start
When this skill is loaded, you MUST check whether the sub-plugins listed below are also installed and available. Check by looking for their SKILL.md files or skill names in the current session.
If any sub-plugin is missing, warn the user immediately:
"cirra-ai-sf is an orchestration layer for three sub-plugins. I can see that [missing plugin(s)] is not installed. This means I won't have access to [what it provides]. You can install it with
claude /plugin install github:cirra-ai/skills/[plugin-name], or I can proceed on a best-effort basis without it."
Then proceed with whatever plugins ARE available. Do not silently fall back to generic knowledge — the user should know what they're missing so they can make an informed choice.
If plugins are available you MUST use them! Don't make up your own methodology
Sub-Plugins
| Plugin | Domain | Scoring |
|---|---|---|
| cirra-ai-sf-apex | Apex classes, triggers, tests, batch jobs | 150 points / 8 categories |
| cirra-ai-sf-flow | Record-triggered, screen, autolaunched, scheduled flows | 110 points / 6 categories |
| cirra-ai-sf-data | SOQL queries, DML operations, test data factories | Pass/fail pre-flight checks |
Each plugin includes its own MCP deployment validator — no cross-plugin dependencies.
Routing Rules
When a user request arrives, route to the appropriate plugin:
| Request Type | Route To | Examples |
|---|---|---|
| Write/review Apex code | cirra-ai-sf-apex | "Create a trigger handler", "Review this Apex class" |
| Create/validate a Flow | cirra-ai-sf-flow | "Build a record-triggered flow", "Score this flow XML" |
| Query/insert/update data | cirra-ai-sf-data | "Query all Accounts", "Create 200 test records" |
| Mixed (code + data) | Both | "Deploy the trigger and create test data" |
Orchestration Order
When building a complete feature:
1. cirra-ai-sf-metadata → Create custom objects/fields (if needed) 2. cirra-ai-sf-apex → Deploy Apex classes/triggers cirra-ai-sf-flow → Deploy Flows (parallel with Apex if independent) 3. cirra-ai-sf-data → Create test data, verify with SOQL
Objects and fields must exist before code that references them can be deployed.
Validation Flow
Each plugin validates its own domain independently:
- •cirra-ai-sf-data: Pre-flight checks on
soql_query/sobject_dmlparams (missing sObject, PII detection, syntax errors) — pass/fail - •cirra-ai-sf-apex: 150-point scoring on
metadata_create/metadata_updatefor ApexClass/ApexTrigger — delegates to ApexValidator - •cirra-ai-sf-flow: 110-point scoring on
metadata_create/metadata_updatefor Flow/FlowDefinition — delegates to EnhancedFlowValidator
No plugin needs to import from another plugin's codebase.
Prerequisites
CRITICAL: Call cirra_ai_init() once per session before using any Cirra AI MCP tools.
cirra_ai_init(sf_user="your-username")
Related Skills
These plugins complement the core three but are independent:
| Skill | Purpose |
|---|---|
| cirra-ai-sf-metadata | Custom objects, fields, Permission Sets |
| cirra-ai-sf-lwc | Lightning Web Components |
| cirra-ai-sf-soql | Advanced SOQL optimization |
| cirra-ai-sf-ai-agentscript | Agentforce agent authoring |