salesforce-admin
Skill0 starsChanged 6 months agoMITView on GitHub
Declarative metadata skills for animuscrm — custom objects, fields, platform events, global value sets, validation rules, page layouts, list views, and profile/permission set FLS.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- PranavNagrecha/AwesomeSalesforceSkillstheir own version, first seen Sep 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- PranavNagrecha/AwesomeSalesforceSkills★ 17same name
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 repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- architecture-decision-recordsSkill
- salesforce-code-analyzerSkill
- salesforce-developer-apexSkill
- salesforce-devopsSkill
- salesforce-test-overwatchSkill
- skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 3 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Add Description__c (LongTextArea, 32768 chars) by default
- Very specific: line 33
Create .field-meta.xml for each requested field (see create-custom-field skill)
- Distinctive: line 48
Should it be required?
- Very specific: line 77
Always include: label, description, required (false by default), trackHistory (false by default)
- Very specific: line 106
Create fields/ subfolder with .field-meta.xml for each payload field
- Very specific: line 136
Use this when a picklist field should share values with other objects (e.g.
- Very specific: line 167
Add GlobalValueSet entry to manifest/package.xml
- Very specific: line 181
Default layout name is typically <ObjectName__c> Layout
- Very specific: line 187
Use <behavior>Edit</behavior> for editable fields, <behavior>Readonly</behavior> for read-only
- Distinctive: line 188
Always include the Name field in the first section
- Very specific: line 219
Always create at least the All list view for new custom objects
- Distinctive: line 233
Never edit a full profile file — they are enormous and org-specific.
- Very specific: line 237
Add <objectPermissions> block for the object:
- Very specific: line 249
Add <fieldPermissions> block for each field that needs access:
- Very specific: line 267
Add <objectPermissions> and <fieldPermissions> entries (same structure as above)
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Salesforce Admin Skill — animuscrm
Covers declarative metadata creation: custom objects, custom fields, platform events, validation rules, page layouts, and field-level security.
skill: create-custom-object
Trigger phrase: "create a custom object" / "new object"
Pre-Creation Checklist (confirm before writing any file)
- Is the object truly custom, or can a standard object be extended?
- What is the sharing model? (default: ReadWrite)
- What should the Name field be? (Text label or AutoNumber)
- Which profiles/permission sets need access?
- Which page layouts will include this object?
Steps
- Create
force-app/main/default/objects/<Name__c>/folder - Create
<Name__c>.object-meta.xmlwith:deploymentStatus: DeployedsharingModel: ReadWrite (unless specified otherwise)label,pluralLabelnameField(Text or AutoNumber as appropriate)description— always required
- Create
fields/subfolder - Add
Description__c(LongTextArea, 32768 chars) by default - Create
.field-meta.xmlfor each requested field (see create-custom-field skill) - Naming conventions: PascalCase +
__csuffix (e.g.SalesOrder__c) - Deploy command:
sf project deploy start --metadata CustomObject:<Name__c> --target-org dev-org
skill: create-custom-field
Trigger phrase: "add a field" / "new field on"
Pre-Creation Checklist
- Is the field type appropriate for the data? (Text vs LongTextArea vs Number vs Picklist)
- Should it be required?
- For Lookup: what is the relationship name? What happens on delete (restrict vs cascade)?
- For Picklist: what are the values? Is there a global picklist to reuse?
- Which profiles/permission sets need Read or Edit access?
- Which page layout section should it appear in?
Field Type Reference
| Requested | Salesforce XML type |
| Text (≤255) | Text |
| Long text / rich text | LongTextArea / Html |
| Number / decimal | Number |
| Currency | Currency |
| Percent | Percent |
| Date | Date |
| Date + Time | DateTime |
| True/False | Checkbox |
| Lookup | Lookup |
| Master-Detail | MasterDetail |
| Dropdown | Picklist |
| Multi-select | MultiselectPicklist |
| Phone | Phone |
| URL | Url |
| Auto-increment | AutoNumber |
| Calculated | Formula |
Steps
- Create
force-app/main/default/objects/<ObjectName__c>/fields/<FieldName__c>.field-meta.xml - Always include:
label,description,required(false by default),trackHistory(false by default) - For Lookup: include
referenceToandrelationshipName - For Picklist: include
valueSetwith all values; mark first as default - For Formula: include
formulaandreturnType - Naming: PascalCase +
__c(e.g.TotalAmount__c) - Deploy command:
sf project deploy start --metadata CustomField:<ObjectName__c>.<FieldName__c> --target-org dev-org
skill: create-platform-event
Trigger phrase: "create a platform event" / "new platform event"
Pre-Creation Checklist
- Volume type: StandardVolume (default) or HighVolume (>100k events/day)?
- Publish behavior: PublishAfterCommit (default) or PublishImmediately?
- What are the payload fields and their types?
- Note: Lookup, MasterDetail, and Formula fields are NOT supported on platform events
Steps
- Create
force-app/main/default/objects/<Name__e>/folder - Create
<Name__e>.object-meta.xmlwith:eventType: StandardVolume (or HighVolume if specified)publishBehavior: PublishAfterCommit (or PublishImmediately if specified)label,pluralLabel,descriptiondeploymentStatus: Deployed
- Create
fields/subfolder with.field-meta.xmlfor each payload field - Naming: PascalCase +
__esuffix (e.g.OrderPlaced__e) - Deploy command:
sf project deploy start --metadata CustomObject:<Name__e> --target-org dev-org
skill: create-validation-rule
Trigger phrase: "create a validation rule" / "add a validation rule"
Steps
- Create
force-app/main/default/objects/<ObjectName__c>/validationRules/<RuleName>.validationRule-meta.xml - Include:
active(true),description,errorConditionFormula,errorMessage - Include
errorDisplayFieldif the error should highlight a specific field - Formula returns
truewhen the record is invalid (i.e. when the error fires) - Rule names: Descriptive_Snake_Case (e.g.
Amount_Cannot_Be_Negative) - Deploy command:
sf project deploy start --metadata ValidationRule:<ObjectName__c>.<RuleName> --target-org dev-org
skill: create-global-value-set
Trigger phrase: "create a global picklist" / "global value set" / "shared picklist"
Use this when a picklist field should share values with other objects (e.g. a Status field reused across multiple objects).
Steps
- Create
force-app/main/default/globalValueSets/<ValueSetName>.globalValueSet-meta.xml - XML structure:
<?xml version="1.0" encoding="UTF-8"?> <GlobalValueSet xmlns="http://soap.sforce.com/2006/04/metadata"> <customValue> <fullName>Value1</fullName> <default>true</default> <label>Value1</label> </customValue> <customValue> <fullName>Value2</fullName> <default>false</default> <label>Value2</label> </customValue> <description>Description of what this value set is used for</description> <masterLabel>Value Set Label</masterLabel> <sorted>false</sorted> </GlobalValueSet> - To reference it in a field (instead of inline values), use
valueSetNamein the field-meta.xml:<valueSet> <restricted>true</restricted> <valueSetName>GlobalValueSetAPIName</valueSetName> </valueSet> - Naming: PascalCase, no suffix (e.g.
UsageStatus,OrderStatus) - Add
GlobalValueSetentry tomanifest/package.xml - Deploy command:
sf project deploy start --metadata GlobalValueSet:<ValueSetName> --target-org dev-org
skill: create-page-layout
Trigger phrase: "add to page layout" / "create page layout" / "update layout"
Steps
- File path:
force-app/main/default/objects/<ObjectName__c>/layouts/<ObjectName__c>-<LayoutName>.layout-meta.xml- Default layout name is typically
<ObjectName__c> Layout - Example:
Usage__c-Usage Layout.layout-meta.xml
- Default layout name is typically
- Key XML structure:
<layoutSections>— group fields into sections with 1 or 2 columns<layoutColumns>→<layoutItems>— each item is a field, blank, or separator- Required fields must appear in the layout
- Use
<behavior>Edit</behavior>for editable fields,<behavior>Readonly</behavior>for read-only
- Always include the Name field in the first section
- Group related fields together (dates together, lookups together, etc.)
- Add
Layoutentry tomanifest/package.xml - Deploy command:
sf project deploy start --metadata Layout:"<ObjectName__c>-<LayoutName>" --target-org dev-org
skill: create-list-view
Trigger phrase: "create a list view" / "add list view" / "default list view"
Steps
- File path:
force-app/main/default/objects/<ObjectName__c>/listViews/<ListViewName>.listView-meta.xml- Standard names:
All(all records),Recent(recently viewed)
- Standard names:
- Key XML structure:
<?xml version="1.0" encoding="UTF-8"?> <ListView xmlns="http://soap.sforce.com/2006/04/metadata"> <fullName>All</fullName> <columns>NAME</columns> <columns>Field1__c</columns> <columns>Field2__c</columns> <filterScope>Everything</filterScope> <label>All</label> </ListView> <filterScope>options:Everything,Mine,Queue,Delegated,MyTerritory- To add filter criteria, include
<filters>with<field>,<operation>,<value> - Always create at least the
Alllist view for new custom objects - Add
ListViewentry tomanifest/package.xml - Deploy command:
sf project deploy start --metadata ListView:<ObjectName__c>.<ListViewName> --target-org dev-org
skill: grant-profile-fls-access
Trigger phrase: "grant access to profile" / "add FLS to profile" / "grant System Administrator access"
Important
Never edit a full profile file — they are enormous and org-specific. Use Permission Sets for new access grants wherever possible. Only edit a profile file when the spec explicitly requires it (e.g. System Administrator access to a new object).
Steps for Permission Set (preferred)
- File path:
force-app/main/default/permissionsets/<Name>.permissionset-meta.xml - Add
<objectPermissions>block for the object:<objectPermissions> <allowCreate>true</allowCreate> <allowDelete>true</allowDelete> <allowEdit>true</allowEdit> <allowRead>true</allowRead> <modifyAllRecords>false</modifyAllRecords> <object>Usage__c</object> <viewAllRecords>false</viewAllRecords> </objectPermissions> - Add
<fieldPermissions>block for each field that needs access:<fieldPermissions> <editable>true</editable> <field>Usage__c.Status__c</field> <readable>true</readable> </fieldPermissions> - Deploy command:
sf project deploy start --metadata PermissionSet:<Name> --target-org dev-org
Steps for Profile (only when explicitly required)
- Retrieve the profile first — never edit from scratch:
sf project retrieve start --metadata Profile:Admin --target-org dev-org - Add
<objectPermissions>and<fieldPermissions>entries (same structure as above) - Deploy command:
sf project deploy start --metadata Profile:Admin --target-org dev-org
Post-Grant Verification
- Confirm the object appears in the App Launcher or navigation for the target profile
- Confirm each field is visible and editable as expected
- Confirm the list view is accessible
Post-Creation Verification
- Confirm global value sets are deployed before any field that references them
- Confirm field-level security is set for all relevant profiles/permission sets
- Confirm field is added to the correct page layout and section
- Confirm a list view exists for every new custom object
- For picklists: confirm all required values are present
- For lookups: confirm relationship name does not conflict with existing relationships
- For platform events: confirm publishBehavior matches the use case (transactional vs fire-and-forget)
Does 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.

