Agent skill

Sf Metadata

Salesforce metadata generation and querying with 120-point scoring.

Install Sf Metadata

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-metadata -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-metadata --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-metadata .claude/skills/sf-metadata && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sf-metadata" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-metadata into .claude/skills/sf-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-metadata", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-metadata

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-metadata -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-metadata --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sf-metadata .agents/skills/sf-metadata && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sf-metadata" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-metadata into .agents/skills/sf-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-metadata", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-metadata -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-metadata --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sf-metadata .cursor/skills/sf-metadata && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sf-metadata" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-metadata into .cursor/skills/sf-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-metadata", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Jaganpro/sf-skills.git --path skills/sf-metadata

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-metadata -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-metadata --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sf-metadata .gemini/skills/sf-metadata && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sf-metadata" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-metadata into .gemini/skills/sf-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-metadata", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-metadata

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-metadata -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sf-metadata .github/skills/sf-metadata && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sf-metadata" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-metadata into .github/skills/sf-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-metadata", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-metadata -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-metadata --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sf-metadata .opencode/skills/sf-metadata && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sf-metadata" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-metadata into .opencode/skills/sf-metadata/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-metadata", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sf-metadata
GitHub stars: 424
Token cost: ~1.6k tokens
SKILL.md length: 527 words
Files: 49 (incl. references, assets)
Skills in repo: 36
Repo updated: Apr 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Salesforce metadata generation and querying with 120-point scoring.

Works in 5 steps: Choose the mode → Start from templates or CLI describe data → Validate metadata quality → …
: user creates custom objects
SKILL.md covers When This Skill Owns the Task, Required Context to Gather First, Recommended Workflow and High-Signal Rules, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Sf Metadata is an agent skill from Jaganpro/sf-skills. 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 sf-deploy), or Flow XML (use sf-flow).

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 50 other files, including reference files and assets (for example `CREDITS.md` and `README.md`).

It sits in Sales & Support, covering CRM management. It works with Salesforce. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.

When your agent uses it

: user creates custom objects
Validation rules
Touches .object-meta.xml
.field-meta.xml

Example prompts

“/sf-metadata”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Choose the mode
Start from templates or CLI describe data
Validate metadata quality
Plan permission impact by default
Hand off deployment

What it can do on your machine

Read from SKILL.md and the folder at commit 53c9956. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sf Metadata loads about 1.6k tokens when it runs, and up to ~27k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 527 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~87
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~27k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 527 words, ~1,558 tokens.

Download SKILL.mdSave it as .claude/skills/sf-metadata/SKILL.md (or your agent's skills folder). This skill also uses 48 other files; get the full folder from GitHub.

name: sf-metadata
description: 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 sf-deploy), or Flow XML (use sf-flow).
license: MIT
metadata.version: 1.2.0
metadata.author: Jag Valaiyapathy
metadata.scoring: 120 points across 6 categories

sf-metadata: Salesforce Metadata Generation and Org Querying

Use this skill when the user needs metadata definition or org metadata discovery: custom objects, fields, validation rules, record types, page layouts, permission sets, or schema inspection with sf CLI.

When This Skill Owns the Task

Use sf-metadata when the work involves:

object, field, validation rule, record type, layout, profile, or permission-set metadata
.object-meta.xml, .field-meta.xml, .profile-meta.xml, and related metadata files
describing schema before coding or Flow work
generating metadata XML from requirements

Delegate elsewhere when the user is:

analyzing permission access rather than defining metadata → sf-permissions
deploying metadata → sf-deploy
editing Flow XML → sf-flow

Required Context to Gather First

Ask for or infer:

whether the user wants generation or querying
metadata type(s) involved
target object / field / package directory
target org alias if querying is required
whether new custom objects or fields should also include permission-set / FLS generation

Unless the user explicitly opts out, assume new custom objects or fields need permission-set follow-up.

Recommended Workflow

1. Choose the mode

Mode	Use when
generation	the user wants new or updated metadata XML
querying	the user needs object / field / metadata discovery

2. Start from templates or CLI describe data

For generation, use the assets under:

assets/objects/
assets/fields/
assets/permission-sets/
assets/profiles/
assets/record-types/
assets/validation-rules/
assets/layouts/

For querying, prefer sf metadata and sobject describe commands.

Recent SDR/CLI support worth knowing when reading older examples: CnfgItemSourceDefinition, ExtlClntAppOauthSecuritySettings, and UIBundle are now source-supported under their current names. See references/metadata-types-reference.md.

3. Validate metadata quality

Check:

naming conventions
structural correctness
field-type fit
security / FLS implications
downstream deployment dependencies

4. Plan permission impact by default

When new custom fields or objects are created:

default to generating or updating a Permission Set unless the user opts out
include fieldPermissions for eligible custom fields
note any metadata categories that are excluded because Salesforce treats them as system-managed or always-available
remember that object CRUD alone does not make custom fields visible

Show full SKILL.md (215 more words)Show less

5. Hand off deployment

Use sf-deploy when the user needs the metadata rolled out.

High-Signal Rules

field-level security is often the hidden blocker after deployment
object permissions ≠ field permissions
prefer permission sets over profile-centric access patterns
generate Permission Set follow-up by default for new custom objects and fields
include fieldPermissions for eligible custom fields instead of leaving FLS as a manual afterthought
avoid hardcoded IDs in formulas or metadata logic
validation rules should have intentional bypass strategy when operationally necessary
create metadata before attempting Flow or data tasks that depend on it

Output Format

When finishing, report in this order:

Metadata created or queried
Files created or updated
Key schema/security decisions
Permission / layout follow-ups
Deploy next step

Suggested shape:

text

Metadata task: <generate / query>
Items: <objects, fields, rules, layouts, permsets>
Files: <paths>
Notes: <naming, field types, security, dependencies>
Next step: <deploy, assign permset, or verify in Setup>

Cross-Skill Integration

Need	Delegate to	Reason
deploy metadata	sf-deploy	rollout and validation
build Flows on new schema	sf-flow	declarative automation
build Apex on new schema	sf-apex	code against metadata
analyze permission access after creation	sf-permissions	access auditing
seed data after deploy	sf-data	test data creation

Reference Map

Start here

Security / scoring / examples

Score Guide

Score	Meaning
108+	strong production-ready metadata
96–107	good metadata with minor review items
84–95	acceptable but validate carefully
< 84	block deployment until corrected

Files

SKILL.md and 48 other files (references, assets) in skills/sf-metadata of Jaganpro/sf-skills.

SKILL.md
CREDITS.md
README.md
assets/fields/checkbox-field.xml
assets/fields/currency-field.xml
assets/fields/date-field.xml
assets/fields/email-field.xml
assets/fields/formula-field.xml
assets/fields/lookup-field.xml
assets/fields/master-detail-field.xml
assets/fields/multi-select-picklist.xml
assets/fields/number-field.xml
assets/fields/phone-field.xml
assets/fields/picklist-field.xml
assets/fields/rollup-summary-field.xml
assets/fields/text-field.xml
assets/fields/textarea-field.xml
assets/fields/url-field.xml
assets/layouts
… and 30 more

Open the folder on GitHubat commit 53c9956

Compare with similar skills

Sf Metadata next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sf Metadata compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sf Metadata this skillJaganpro/sf-skills	424	—	~1.6k	Automated safety check: Pass	MIT	5 mo ago
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib	154	—	~4.3k	Automated safety check: Pass	MIT	5 days ago
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib	154	—	~2k	Automated safety check: Pass	MIT	5 days ago
Dev SetupPortwood-Global-Solutions/Portwood	125	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Automation Sandbox Post Copy Configureforcedotcom/sf-skills	1.1k	—	~5.3k	Automated safety check: Notes	Apache-2.0	yesterday
Automation Sandbox Post Copy Configureforcedotcom/sf-skills	1.1k	—	~5.4k	Automated safety check: Notes	Apache-2.0	yesterday

Similar skills

Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
154 GitHub stars~4.3k tokensUpdated 5 days ago
Sales & SupportAuto-check passed
Soql Lib Selector
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
154 GitHub stars~2k tokensUpdated 5 days ago
Sales & SupportAuto-check passed
Dev Setup
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
125 GitHub stars~1.1k tokensUpdated today
Sales & SupportAuto-check passed
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
1.1k GitHub stars~5.3k tokensUpdated yesterday
Sales & SupportAuto-check: notes
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
1.1k GitHub stars~5.4k tokensUpdated yesterday
Sales & SupportAuto-check: notes
Google Maps Export
gmapsscraper/google-maps-agent-skills
Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).
132 GitHub stars~1.2k tokensUpdated 4 mo ago
Sales & SupportAuto-check passed

Questions about Sf Metadata

What does Sf Metadata do?

Salesforce metadata generation and querying with 120-point scoring. Sf Metadata is an agent skill from Jaganpro/sf-skills. Salesforce metadata generation and querying with 120-point scoring.

When should I use Sf Metadata?

Sf Metadata fits situations like: : user creates custom objects; validation rules; touches .object-meta.xml; .field-meta.xml.

How do I install Sf Metadata in Claude Code?

Run `npx skills add Jaganpro/sf-skills --skill sf-metadata -a claude-code`. Or copy the skill folder (skills/sf-metadata in Jaganpro/sf-skills) into .claude/skills/sf-metadata in your project. Claude Code loads it when a task matches its description.

How do I install Sf Metadata in Codex?

Run `npx skills add Jaganpro/sf-skills --skill sf-metadata -a codex`. Or copy the skill folder (skills/sf-metadata in Jaganpro/sf-skills) into .agents/skills/sf-metadata in your project. Codex loads it when a task matches its description.

Can I use Sf Metadata in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jaganpro/sf-skills --skill sf-metadata -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sf-metadata, .gemini/skills/sf-metadata, .github/skills/sf-metadata and .opencode/skills/sf-metadata in your project.

What does Sf Metadata need to run?

SKILL.md names no scripts, command-line tools or credentials: Sf Metadata is instructions for the agent only.

Does Sf Metadata access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sf Metadata safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sf Metadata use?

Sf Metadata is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sf Metadata use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 26k tokens, read only when the agent opens those files.

What are the alternatives to Sf Metadata?

Skills that share tags, products or a category with Sf Metadata: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars), Dev Setup (Portwood-Global-Solutions/Portwood, 125 stars) and Automation Sandbox Post Copy Configure (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sf Metadata?

Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.

Source: Jaganpro/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sf Metadata

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

sf-metadata: Salesforce Metadata Generation and Org Querying

When This Skill Owns the Task

Required Context to Gather First

Recommended Workflow

1. Choose the mode

2. Start from templates or CLI describe data

3. Validate metadata quality

4. Plan permission impact by default

5. Hand off deployment

High-Signal Rules

Output Format

Cross-Skill Integration

Reference Map

Start here

Security / scoring / examples

Score Guide

Files

Compare with similar skills

Similar skills

More from Jaganpro/sf-skills

Related

Questions about Sf Metadata