Skip to content

kugamon/salesforce-core-skills / plugins/salesforce-core/skills/sf-metadata

sf-metadata

Verified

Salesforce 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} ...

FileKindSize
CREDITS.mdmarkdown2.3 KB
LICENSEother1.1 KB
README.mdmarkdown3.5 KB
SKILL.mdskill md33.8 KB
assets/fields/checkbox-field.xmlconfig971 B
assets/fields/currency-field.xmlconfig1.3 KB
assets/fields/date-field.xmlconfig1.0 KB
assets/fields/email-field.xmlconfig1.1 KB
assets/fields/formula-field.xmlconfig2.3 KB
assets/fields/lookup-field.xmlconfig2.1 KB
assets/fields/master-detail-field.xmlconfig1.8 KB
assets/fields/multi-select-picklist.xmlconfig2.0 KB
assets/fields/number-field.xmlconfig1.4 KB
assets/fields/phone-field.xmlconfig1.0 KB
assets/fields/picklist-field.xmlconfig2.1 KB
assets/fields/rollup-summary-field.xmlconfig2.7 KB
assets/fields/text-field.xmlconfig1.2 KB
assets/fields/textarea-field.xmlconfig1.1 KB
assets/fields/url-field.xmlconfig940 B
assets/layouts/page-layout.xmlconfig6.5 KB
assets/objects/custom-object.xmlconfig2.4 KB
assets/permission-sets/permission-set.xmlconfig5.7 KB
assets/profiles/profile.xmlconfig5.2 KB
assets/record-types/record-type.xmlconfig3.7 KB
assets/validation-rules/validation-rule.xmlconfig5.1 KB
references/best-practices-scoring.mdmarkdown3.6 KB
references/customfield-metadata-schema.jsonconfig16.1 KB
references/customobject-metadata-schema.jsonconfig49.9 KB
references/execution-modes.mdmarkdown7.0 KB
references/field-types-guide.mdmarkdown8.8 KB
references/flexipage-metadata-schema.jsonconfig11.6 KB
references/fls-best-practices.mdmarkdown7.8 KB
references/layout-metadata-schema.jsonconfig17.8 KB
references/mcp-pagination.mdmarkdown3.1 KB
references/metadata-types-reference.mdmarkdown8.5 KB
references/naming-conventions.mdmarkdown5.6 KB
references/permset-auto-generation.mdmarkdown2.8 KB
references/quickaction-metadata-schema.jsonconfig6.9 KB
references/recordtype-metadata-schema.jsonconfig2.9 KB
references/validationrule-metadata-schema.jsonconfig1.2 KB
scripts/mcp_validator.pyscript4.5 KB
scripts/pre-mcp-validate.pyscript4.3 KB
scripts/validate_metadata_operation.pyscript13.9 KB

assets/permission-sets/permission-set.xml

View on GitHub
<?xml version="1.0" encoding="UTF-8"?>
<!--
    Permission Set Template

    Usage: Granular permissions assigned to users on top of their profile

    BEST PRACTICE: Use Permission Sets for feature-based access control.
    Organize by feature or function, not by user role.

    Placeholders:
    - {{PERMISSION_SET_NAME}} - API name (e.g., "Invoice_Manager")
    - {{LABEL}} - User-friendly name (e.g., "Invoice Manager")
    - {{DESCRIPTION}} - Purpose of this permission set
    - {{LICENSE}} - Optional: specific license required
    - {{REQUIRES_ACTIVATION}} - true for session-based permissions

    Naming Convention:
    - Feature-based: "Invoice_Manager", "Report_Builder"
    - Integration: "Integration_API_Access"
    - Admin: "Admin_User_Management"
-->
<PermissionSet xmlns="http://soap.sforce.com/2006/04/metadata">
    <label>{{LABEL}}</label>
    <description>{{DESCRIPTION}}</description>
    <hasActivationRequired>{{REQUIRES_ACTIVATION}}</hasActivationRequired>
    <!-- Optional: Restrict to specific license -->
    <!-- <license>{{LICENSE}}</license> -->

    <!--
    ═══════════════════════════════════════════
    OBJECT PERMISSIONS
    ═══════════════════════════════════════════
    Grant CRUD access for objects
    -->
    <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)
    ═══════════════════════════════════════════
    Grant read/edit access for specific fields
    -->
    <fieldPermissions>
        <editable>true</editable>
        <field>Custom_Object__c.Sensitive_Field__c</field>
        <readable>true</readable>
    </fieldPermissions>

    <fieldPermissions>
        <editable>false</editable>
        <field>Custom_Object__c.Read_Only_Field__c</field>
        <readable>true</readable>
    </fieldPermissions>

    <!--
    ═══════════════════════════════════════════
    TAB SETTINGS
    ═══════════════════════════════════════════
    Available, None, or Visible
    -->
    <tabSettings>
        <tab>Custom_Object__c</tab>
        <visibility>Visible</visibility>
    </tabSettings>

    <!--
    ═══════════════════════════════════════════
    RECORD TYPE ASSIGNMENTS
    ═══════════════════════════════════════════
    Make record types visible to users with this permission set
    -->
    <!--
    <recordTypeVisibilities>
        <recordType>Custom_Object__c.Record_Type_Name</recordType>
        <visible>true</visible>
    </recordTypeVisibilities>
    -->

    <!--
    ═══════════════════════════════════════════
    USER PERMISSIONS (SYSTEM PERMISSIONS)
    ═══════════════════════════════════════════
    Enable specific system-level permissions
    -->
    <!--
    <userPermissions>
        <enabled>true</enabled>
        <name>ApiEnabled</name>
    </userPermissions>
    -->

    <!--
    ═══════════════════════════════════════════
    APEX CLASS ACCESS
    ═══════════════════════════════════════════
    Grant access to Apex classes (for Visualforce, Lightning)
    -->
    <!--
    <classAccesses>
        <apexClass>MyApexController</apexClass>
        <enabled>true</enabled>
    </classAccesses>
    -->

    <!--
    ═══════════════════════════════════════════
    CUSTOM PERMISSIONS
    ═══════════════════════════════════════════
    Enable custom permissions (for feature flags)
    -->
    <!--
    <customPermissions>
        <enabled>true</enabled>
        <name>Feature_Flag_Name</name>
    </customPermissions>
    -->
</PermissionSet>

<!--
    PERMISSION SET ORGANIZATION PATTERNS
    ════════════════════════════════════════════

    1. Feature-Based (RECOMMENDED):
       - "Sales_Forecasting_Access"
       - "Marketing_Campaign_Manager"
       - "Customer_Support_Tools"

    2. Integration-Based:
       - "ERP_Integration_API"
       - "Marketing_Automation_Sync"

    3. Object-Based:
       - "Invoice_Full_Access"
       - "Contact_Read_Only"

    4. Environment/Session-Based:
       - "Elevated_Admin_Session" (requires activation)
       - "After_Hours_Access"

    PERMISSION SET GROUPS:
    Combine multiple permission sets into a single assignable group:
    - "Sales_Rep_Standard" = Sales_Forecasting + Account_Access + Report_Viewer
-->
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: 472kUpdated Claude CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall