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/validation-rules/validation-rule.xml

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

    Usage: Enforce data quality by preventing invalid data entry

    Placeholders:
    - {{RULE_API_NAME}} - API name (e.g., "Require_Close_Date_When_Closed")
    - {{ACTIVE}} - true or false
    - {{DESCRIPTION}} - Rule purpose and business logic
    - {{ERROR_FORMULA}} - Formula that returns TRUE when invalid
    - {{ERROR_FIELD}} - Field to display error on (optional)
    - {{ERROR_MESSAGE}} - User-friendly error message

    Notes:
    - Formula returns TRUE = validation fails (error shown)
    - Formula returns FALSE = validation passes (record saved)
    - Keep formulas simple for maintainability
    - Consider bypass mechanism for integrations/admins
-->
<ValidationRule xmlns="http://soap.sforce.com/2006/04/metadata">
    <fullName>{{RULE_API_NAME}}</fullName>
    <active>{{ACTIVE}}</active>
    <description>{{DESCRIPTION}}</description>
    <errorConditionFormula>{{ERROR_FORMULA}}</errorConditionFormula>
    <!-- Optional: Display error on specific field instead of top of page -->
    <errorDisplayField>{{ERROR_FIELD}}</errorDisplayField>
    <errorMessage>{{ERROR_MESSAGE}}</errorMessage>
</ValidationRule>

<!--
    COMMON VALIDATION PATTERNS
    ════════════════════════════════════════════

    1. Required Field Based on Status:
    ───────────────────────────────────────────
    AND(
        ISPICKVAL(Status__c, 'Closed'),
        ISBLANK(Close_Date__c)
    )
    Error: "Close Date is required when Status is Closed"

    2. Date Must Be Future:
    ───────────────────────────────────────────
    Due_Date__c < TODAY()
    Error: "Due Date must be in the future"

    3. Date Range Validation:
    ───────────────────────────────────────────
    End_Date__c < Start_Date__c
    Error: "End Date must be after Start Date"

    4. Numeric Range:
    ───────────────────────────────────────────
    OR(
        Discount_Percent__c < 0,
        Discount_Percent__c > 100
    )
    Error: "Discount must be between 0% and 100%"

    5. Email Format:
    ───────────────────────────────────────────
    NOT(REGEX(Email__c, "^[a-zA-Z0-9._-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}$"))
    Error: "Please enter a valid email address"

    6. Phone Format (US):
    ───────────────────────────────────────────
    NOT(REGEX(Phone__c, "^\\(?[0-9]{3}\\)?[-. ]?[0-9]{3}[-. ]?[0-9]{4}$"))
    Error: "Phone must be in format: (XXX) XXX-XXXX"

    7. Cross-Object Validation:
    ───────────────────────────────────────────
    AND(
        NOT(ISBLANK(Account.Type)),
        Account.Type != 'Customer',
        Amount__c > 100000
    )
    Error: "Opportunities over $100K require Customer account type"

    8. Dependent Picklist Enforcement:
    ───────────────────────────────────────────
    AND(
        ISPICKVAL(Type__c, 'Service'),
        NOT(ISPICKVAL(Sub_Type__c, 'Consulting')),
        NOT(ISPICKVAL(Sub_Type__c, 'Support'))
    )
    Error: "Service type requires Consulting or Support sub-type"

    9. Prevent Editing Closed Records:
    ───────────────────────────────────────────
    AND(
        NOT(ISNEW()),
        ISPICKVAL(PRIORVALUE(Status__c), 'Closed'),
        ISCHANGED(Status__c)
    )
    Error: "Cannot reopen closed records"

    10. Bypass Pattern (Recommended):
    ───────────────────────────────────────────
    AND(
        NOT($Permission.Bypass_Validation__c),
        [your validation logic here]
    )
    Note: Create Custom Permission "Bypass_Validation__c" for admins/integrations


    VALIDATION RULE BEST PRACTICES
    ════════════════════════════════════════════

    ✓ Include bypass mechanism for system integrations
    ✓ Use clear, actionable error messages
    ✓ Display error on specific field when possible
    ✓ Document business requirement in description
    ✓ Test with bulk data operations
    ✓ Consider impact on integrations and data loads

    ✗ Don't create complex formulas (hard to maintain)
    ✗ Don't duplicate validation logic in triggers
    ✗ Don't use validation for business logic (use flows/triggers)
    ✗ Don't block system users from fixing data issues
-->
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: 471kUpdated Claude CodeCodexVerifiedInstall
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