kugamon/salesforce-core-skills / plugins/salesforce-core/skills/sf-metadata
sf-metadata
VerifiedSalesforce metadata operations expert. Use when creating custom objects, fields, validation rules, record types, permission sets, or querying org metadata structures via a Salesforce MCP server. Do NOT use for comparing metadata across two orgs (use sf-orgdiff), Named or External Credentials and Platform Events (use sf-integration), or querying and loading records (use sf- data). Usage: /sf-metadata [create|update|delete|describe] {ObjectName|FieldName|type} ...
assets/profiles/profile.xml
View on GitHub<?xml version="1.0" encoding="UTF-8"?>
<!--
Profile Template
Usage: User profile defining permissions and access
RECOMMENDATION: Use Permission Sets instead of Profiles for granular permissions.
Profiles should define base access; Permission Sets for feature-specific access.
Placeholders:
- {{PROFILE_NAME}} - Profile API name
- {{DESCRIPTION}} - Profile purpose
- {{USER_LICENSE}} - License type (Salesforce, Salesforce Platform, etc.)
- {{IS_CUSTOM}} - true for custom profiles, false for standard
Notes:
- Standard profiles cannot be deleted
- Profile determines record types, page layouts, and login hours
- Field permissions and object permissions are typically managed here
- Consider using Permission Set Groups for complex permission models
-->
<Profile xmlns="http://soap.sforce.com/2006/04/metadata">
<custom>{{IS_CUSTOM}}</custom>
<description>{{DESCRIPTION}}</description>
<userLicense>{{USER_LICENSE}}</userLicense>
<!--
═══════════════════════════════════════════
OBJECT PERMISSIONS
═══════════════════════════════════════════
Define CRUD access for each object
-->
<objectPermissions>
<allowCreate>true</allowCreate>
<allowDelete>false</allowDelete>
<allowEdit>true</allowEdit>
<allowRead>true</allowRead>
<modifyAllRecords>false</modifyAllRecords>
<object>Account</object>
<viewAllRecords>false</viewAllRecords>
</objectPermissions>
<!-- Add more object permissions as needed -->
<!--
<objectPermissions>
<allowCreate>true</allowCreate>
<allowDelete>false</allowDelete>
<allowEdit>true</allowEdit>
<allowRead>true</allowRead>
<modifyAllRecords>false</modifyAllRecords>
<object>Custom_Object__c</object>
<viewAllRecords>false</viewAllRecords>
</objectPermissions>
-->
<!--
═══════════════════════════════════════════
FIELD PERMISSIONS (FLS)
═══════════════════════════════════════════
Define read/edit access for specific fields
-->
<fieldPermissions>
<editable>true</editable>
<field>Account.Industry</field>
<readable>true</readable>
</fieldPermissions>
<!-- Add more field permissions as needed -->
<!--
<fieldPermissions>
<editable>false</editable>
<field>Account.Sensitive_Field__c</field>
<readable>true</readable>
</fieldPermissions>
-->
<!--
═══════════════════════════════════════════
TAB VISIBILITY
═══════════════════════════════════════════
DefaultOn, DefaultOff, or Hidden
-->
<tabVisibilities>
<tab>standard-Account</tab>
<visibility>DefaultOn</visibility>
</tabVisibilities>
<!--
═══════════════════════════════════════════
RECORD TYPE ASSIGNMENTS
═══════════════════════════════════════════
Assign available record types
-->
<!--
<recordTypeVisibilities>
<default>true</default>
<recordType>Account.Business_Account</recordType>
<visible>true</visible>
</recordTypeVisibilities>
-->
<!--
═══════════════════════════════════════════
PAGE LAYOUT ASSIGNMENTS
═══════════════════════════════════════════
Map record types to page layouts
-->
<!--
<layoutAssignments>
<layout>Account-Account Layout</layout>
</layoutAssignments>
-->
<!--
═══════════════════════════════════════════
APPLICATION VISIBILITY
═══════════════════════════════════════════
-->
<applicationVisibilities>
<application>standard__LightningSales</application>
<default>true</default>
<visible>true</visible>
</applicationVisibilities>
<!--
═══════════════════════════════════════════
USER PERMISSIONS (SYSTEM PERMISSIONS)
═══════════════════════════════════════════
Enable specific system permissions
-->
<userPermissions>
<enabled>true</enabled>
<name>ViewSetup</name>
</userPermissions>
</Profile>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |