platform-metadata-api-context-get

Retrieve Salesforce Metadata API field definitions and XML structures.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-metadata-api-context-get
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-metadata-api-context-get
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/platform-metadata-api-context-get
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-metadata-api-context-get

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly understand, author, and modify Salesforce Metadata API files without loading unnecessary documentation or guessing field structures.

Core Features & Use Cases

  • Metadata Type Reference: Find field definitions, required values, and XML structure for Salesforce metadata types.
  • Salesforce DX Guidance: Understand where files live in force-app style projects and how metadata maps to SFDX source format.
  • Efficient Research: Use section-specific loading guidance to minimize token usage when working with large metadata JSON references.
  • Practical Use Cases: Create a CustomObject file, inspect a Flow definition, validate a Profile permission block, or determine the correct XML for a Salesforce settings component.

Quick Start

Ask for the specific Salesforce metadata type and section you need, such as the fields and sample XML for CustomObject.

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 find the correct XML structure for a Salesforce CustomObject metadata file?

To structure a Salesforce CustomObject metadata file, you need field definitions and required values from the Metadata API. This reference provides type-specific XML formats and nested subtypes to validate your metadata authoring without loading full documentation.

What is the correct XML format for Salesforce Profile permissions in an SFDX project?

Salesforce Profile permissions require specific XML blocks defined by the Metadata API. You can validate required fields and correct namespace structures for your SFDX source format by looking up the specific metadata type section.

How do I modify a Salesforce Flow definition XML without loading the entire metadata reference?

You can modify a Salesforce Flow definition XML efficiently by using selective section loading. This targets only the necessary type-specific fields and nested subtypes, minimizing token usage while ensuring namespace correctness during metadata authoring.

Does this Metadata API reference work with Salesforce DX project structures?

Yes, it applies to Salesforce DX project structures by mapping metadata types to their SFDX source format. It clarifies where files live in force-app style projects and helps validate required fields for your metadata components.

What's the best way to validate required fields and nested subtypes in Salesforce metadata XML?

The best way to validate required fields and nested subtypes in Salesforce metadata XML is through type-specific Metadata API lookups. This ensures namespace correctness and verifies field definitions directly against the required format.