model-route
Skill15 starsChanged 7 months agoMITView on GitHub
Use when selecting Claude model tier for Salesforce development tasks. Recommend haiku, sonnet, or opus based on Apex complexity, deploy risk, and budget.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- TheKREATORS/my-claude-skillsedited, first seen Mar 19, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- TheKREATORS/my-claude-skills★ 169% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository58 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asideSkill
- checkpointSkill
- configure-sccSkill
- continuous-agent-loopSkill
- mcp-server-patternsSkill
- prompt-optimizerSkill
- refactor-cleanSkill
- resume-sessionSkill
- save-sessionSkill
- search-firstSkill
- security-scanSkill
- sessionsSkill
- sf-2gp-security-reviewSkill
- sf-agentforce-developmentSkill
- sf-agentforce-mcp-actionsSkill
- sf-apex-async-patternsSkill
- sf-apex-best-practicesSkill
- sf-apex-constraintsSkill
- sf-apex-cursorSkill
- sf-apex-enterprise-patternsSkill
- sf-apex-testingSkill
- sf-api-designSkill
- sf-approval-processesSkill
- sf-aura-developmentSkill
- sf-build-fixSkill
- sf-cli-referenceSkill
- sf-data-modelingSkill
- sf-debuggingSkill
- sf-deployment-constraintsSkill
- sf-deploymentSkill
- sf-devops-ci-cdSkill
- sf-docs-lookupSkill
- sf-e2e-testingSkill
- sf-experience-cloudSkill
- sf-flow-developmentSkill
- sf-governor-limitsSkill
- sf-harness-auditSkill
- sf-helpSkill
- sf-integrationSkill
- sf-lwc-constraintsSkill
- sf-lwc-developmentSkill
- sf-lwc-testingSkill
- sf-metadata-managementSkill
- sf-platform-events-cdcSkill
- sf-quickstartSkill
- sf-security-constraintsSkill
- sf-securitySkill
- sf-soql-constraintsSkill
- sf-soql-optimizationSkill
- sf-tdd-workflowSkill
- sf-testing-constraintsSkill
- sf-trigger-constraintsSkill
- sf-trigger-frameworksSkill
- sf-visualforce-developmentSkill
- strategic-compactSkill
- update-docsSkill
- update-platform-docsSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Before starting a task where model choice significantly affects quality or cost
- Distinctive: line 14
When deciding between haiku, sonnet, and opus for a Salesforce development task
- Distinctive: line 15
When the user wants cost-conscious model selection guidance
- Distinctive: line 16
When routing sub-agent work to the appropriate model tier
- Very specific: line 41
Use opus when the task requires deep understanding of Salesforce architecture, security implications, or governor limit analysis across …
- Very specific: line 51
Use haiku when the task is deterministic, well-scoped, and unlikely to have subtle correctness issues.
- Very specific: line 61
Use sonnet (default) for standard development work that requires understanding but follows well-known patterns.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Model Route — Task-to-Model Tier Recommendation
Recommend the best model tier for the current task by complexity and budget.
When to Use
- Before starting a task where model choice significantly affects quality or cost
- When deciding between haiku, sonnet, and opus for a Salesforce development task
- When the user wants cost-conscious model selection guidance
- When routing sub-agent work to the appropriate model tier
Usage
/model-route [task-description] [--budget low|med|high]
Routing Heuristic
haiku: deterministic, low-risk mechanical changessonnet: default for implementation and refactorsopus: architecture, deep review, ambiguous requirements
Model names (haiku, sonnet, opus) refer to the current Claude model mapped to that tier in your Claude Code configuration.
Output Format
- recommended model
- confidence level
- why this model fits
- fallback model if first attempt fails
Salesforce Routing Examples
Opus — Complex Reasoning Tasks
Use opus when the task requires deep understanding of Salesforce architecture, security implications, or governor limit analysis across multiple execution paths.
| Task | Why Opus |
| Governor limit audit across trigger/flow/batch chains | Must trace cumulative DML/SOQL across async boundaries, understand order of execution, and reason about worst-case heap/CPU scenarios |
Security review of @RestResource or with sharing/without sharing decisions | Requires nuanced reasoning about record access, CRUD/FLS enforcement, SOQL injection vectors, and org-wide defaults |
| Architecture review for large-scale data model changes | Must evaluate cascade effects on triggers, flows, validation rules, sharing rules, and downstream integrations |
Haiku — Mechanical / Low-Risk Tasks
Use haiku when the task is deterministic, well-scoped, and unlikely to have subtle correctness issues.
| Task | Why Haiku |
Formatting LWC components (fix indentation, add missing @api decorators) | Purely mechanical — no logic changes, just style compliance |
| Simple Apex fixes (rename a variable, fix a typo in a label, add a missing null check) | Single-line or few-line changes with obvious correctness |
Adding <meta.xml> boilerplate or updating apiVersion across components | Repetitive, pattern-based edits with no ambiguity |
Sonnet — Balanced Implementation Tasks
Use sonnet (default) for standard development work that requires understanding but follows well-known patterns.
| Task | Why Sonnet |
| Code review of an Apex trigger handler or service class | Needs to understand patterns and spot issues, but follows standard review criteria |
Generating Apex test classes with @TestSetup, mocking, and assertions | Requires understanding the class under test, but test generation follows repeatable patterns |
| Implementing a new LWC component with wire adapters and error handling | Standard implementation work — needs context awareness but not deep architectural reasoning |
Arguments
[task-description]optional free-text--budget low|med|highoptional
Examples
/model-route Review the sharing model for the new Patient__c object hierarchy
/model-route Fix the CSS alignment on the accountDashboard LWC --budget low
/model-route Generate test coverage for OpportunityTriggerHandler
/model-route Audit all SOQL queries in force-app for governor limit risks --budget highDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.