platform-metadata-api-context-get

Provides field definitions and XML structure reference for 604 Salesforce Metadata API types.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill platform-metadata-api-context-get-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-metadata-api-context-get
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/platform-metadata-api-context-get
Command: npx skills add https://github.com/padjei/SF_Build --skill platform-metadata-api-context-get-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes references (resource) components.

What problem does it solve? Authoring or editing Salesforce metadata XML files (like .object-meta.xml or .flow-meta.xml) requires knowing exact field names, types, required values, and namespace rules, and looking these up manually across Salesforce documentation is slow and error-prone. ## Core Features & Use Cases - Metadata Type Reference: Access field definitions, descriptions, WSDL schema segments, and sample XML for all 604 Metadata API types (CustomObject, Flow, Profile, PermissionSet, and more). - Token-Optimized Loading: Extract only the JSON sections you need (fields, description, examples) using jq, Python, or Node.js, reducing token consumption by 60-80% per file. - XML Generation Guidance: Enforces correct namespace, root elements, required fields, file naming conventions, and Salesforce DX directory structure for deployable metadata. - Use Case: When asked to create a Flow metadata file, load only the 'fields' section from Flow.json, check required fields, and generate a valid .flow-meta.xml ready for sf project deploy validate. ## Quick Start Ask the AI to show only the 'fields' section from CustomObject.json so you can author a new custom object metadata file.

Frequently Asked Questions about platform-metadata-api-context-get

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Salesforce CustomObject metadata XML file?▼

Load the 'fields' section from CustomObject.json to see required fields like label, pluralLabel, nameField, deploymentStatus, and sharingModel. Then generate XML with the namespace http://soap.sforce.com/2006/04/metadata and save it as MyObject__c.object-meta.xml.

How do I look up fields for a Salesforce metadata type?▼

Use jq or a JSON parser to extract only the 'fields' section from the type's JSON file, for example: jq '.fields' data/metadata_api/Flow.json. Avoid reading the entire file, which wastes 60-80% of tokens on verbose WSDL segments.

Does this skill cover SOQL queries or runtime sObject data?▼

No. This skill covers only Metadata API XML authoring for deployment. SOQL, DML, and runtime sObject access belong to the Enterprise API, and developer records like TraceFlag belong to the Tooling API.

Why does my generated Salesforce metadata file fail to deploy?▼

Common causes are a missing or incorrect namespace, omitted required fields, or wrong file naming. Verify the namespace is exactly http://soap.sforce.com/2006/04/metadata and run sf project deploy validate before deploying.

What Salesforce API version does this metadata reference support?▼

The documentation is generated from Metadata API version 67.0 (Summer 26) and covers 604 metadata types. Newer org versions may include additional fields or types not documented here.

What should I do when a metadata type name is not found?▼

File names are case-sensitive PascalCase like CustomObject.json. Consult references/metadata_index_table.md and use normalize-and-substring matching, then fuzzy matching for typos, to recover the correct type name.