The request asks for a specific operation: generating Salesforce Custom Metadata Type metadata. The community skill platform-custom-metadata-type-generate 3 does exactly this, creating, generating, or validating the __mdt object, its fields, and deployable metadata. Sibling skills for other Salesforce metadata types and the Salesforce metadata context skill 6 are listed as related options.
- 1
- 2
- 3
Sources
- 3GitHub - forcedotcom/sf-skills: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. · GitHubgithub.com · read just now
- 5GitHub - Jaganpro/sf-skills: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active development continues at github.com/forcedotcom/afv-library. · GitHubgithub.com · read just now
- 6GitHub - forcedotcom/sf-skills: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. · GitHubgithub.com · read just now
For agents: the 10 actions behind this answer
· Salesforce: The #1 AI CRM website read, tools not yet checked
Salesforce is the #1 AI CRM, helping companies connect with customers in a whole new way — uniting the data, apps, and agents that run the business.
create_record · Salesforce (Activepieces) verified and signed
Create Record — Create a record of a given object.
addExample · Einstein Vision and Einstein Language verified and signed
Create an Example
platform-custom-metadata-type-generate · platform-custom-metadata-type-generate verified and signed
Use to create, generate, or validate Salesforce Custom Metadata Type metadata — the __mdt object, fields, and deployable records. Trigger on custom metadata types, CMDT, __mdt objects, .md-meta.xml files, or cross-org reference/config data; also admin-maintained mapping/lookup/crosswalk tables (conf
generating-custom-object · generating-custom-object verified and signed
Use this skill when users need to create, generate, or validate Salesforce Custom Object metadata. Trigger when users mention custom objects, creating objects, object metadata, .object files, sharing models, name fields, or validation rules on objects. Also use when users say things like "create a c
sf-metadata · sf-metadata verified and signed
Salesforce metadata generation and querying with 120-point scoring. TRIGGER when: user creates custom objects, fields, validation rules, or touches .object-meta.xml, .field-meta.xml, .profile-meta.xml files. DO NOT TRIGGER when: permission set analysis (use sf-permissions), deploying metadata (use s
platform-metadata-api-context-get · platform-metadata-api-context-get verified and signed
REQUIRED companion for Salesforce metadata generation — load this schema/API-context skill in the SAME turn as ANY metadata generator (if you load a generator, you ALSO load this). Use whenever you create, generate, edit, or author metadata or a *-meta.xml file (custom object, field, flow, and 604 M
platform-custom-field-generate · platform-custom-field-generate verified and signed
Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values pe
platform-custom-report-type-generate · platform-custom-report-type-generate verified and signed
Use to create, generate, or validate Salesforce Custom Report Type metadata. Trigger on custom report types, CRTs, cross-object reports, report builder data sources, exposing fields for reporting across related objects, inner vs outer joins in reports, report type categories, or deployment errors fo
platform-custom-setting-generate · platform-custom-setting-generate verified and signed
Use to create, generate, or validate Salesforce Custom Setting metadata. Trigger on custom settings (hierarchy/list), customSettingsType, SetupOwnerId, per-profile/per-user config overrides, feature flags/toggles, kill switches, or admin on/off switches (e.g. bypass triggers during a data load); als
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.