From jaganpro-sf-skills-7
Generates Salesforce metadata XML for custom objects, fields, validation rules, record types, layouts, profiles; queries org schema via sf CLI. For .object-meta.xml and related files.
npx claudepluginhub jaganpro/sf-skillsThis skill uses the workspace's default tool permissions.
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.
CREDITS.mdREADME.mdassets/fields/checkbox-field.xmlassets/fields/currency-field.xmlassets/fields/date-field.xmlassets/fields/email-field.xmlassets/fields/formula-field.xmlassets/fields/lookup-field.xmlassets/fields/master-detail-field.xmlassets/fields/multi-select-picklist.xmlassets/fields/number-field.xmlassets/fields/phone-field.xmlassets/fields/picklist-field.xmlassets/fields/rollup-summary-field.xmlassets/fields/text-field.xmlassets/fields/textarea-field.xmlassets/fields/url-field.xmlassets/layouts/page-layout.xmlassets/objects/custom-object.xmlassets/permission-sets/permission-set.xmlProvides expert patterns for Salesforce development including LWC, Apex triggers/classes, REST/Bulk APIs, Connected Apps, and SFDX with scratch orgs/2GP.
Automates Salesforce deployments using sf CLI v2: dry-run validation, metadata deploys/retrievals, scratch org/sandbox management, CI/CD pipelines, and error troubleshooting.
Query and manage Salesforce CRM data via Salesforce CLI (sf). Run SOQL/SOSL queries, inspect schemas, CRUD records, bulk import/export, execute Apex, deploy metadata, raw REST API calls.
Share bugs, ideas, or general feedback.
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.
Use sf-metadata when the work involves:
.object-meta.xml, .field-meta.xml, .profile-meta.xml, and related metadata filesDelegate elsewhere when the user is:
Ask for or infer:
Unless the user explicitly opts out, assume new custom objects or fields need permission-set follow-up.
| Mode | Use when |
|---|---|
| generation | the user wants new or updated metadata XML |
| querying | the user needs object / field / metadata discovery |
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.
Check:
When new custom fields or objects are created:
fieldPermissions for eligible custom fieldsUse sf-deploy when the user needs the metadata rolled out.
fieldPermissions for eligible custom fields instead of leaving FLS as a manual afterthoughtWhen finishing, report in this order:
Suggested shape:
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>
| 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 |
| 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 |