Author deployable Salesforce List View metadata XML
Generate Salesforce List View metadata — label/fullName rules, filterScope, filter/operation/value triples, booleanFilterLogic, columns, visibility strategy, folder placement, and a verification checklist
- What
- Generate Salesforce List View metadata — label/fullName rules, filterScope, filter/operation/value triples, booleanFilterLogic, columns, visibility strategy, folder placement, and a verification checklist
- Cost
- Free
- Needs
- Salesforce org access (a free Developer Edition org works) and the Salesforce CLI for deployment — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's skill for generating deployable Salesforce List View metadata: the critical rules (custom fields use exact API names like `Status__c`, never labels; standard fields on custom objects use the defined names — NAME, OWNER.ALIAS, CREATED_DATE, LAST_UPDATE; operations must match field types — equals/notEqual for picklists, 0/1 for booleans, no text-only operators on non-text fields; file name, fullName and uniqueness must align; files go under `objects/<Object>/listViews/`); a 6-step workflow (gather the target object and requirements → examine existing examples in the repo/org → write a spec: fullName, label under 40 chars, filterScope, filters, booleanFilterLogic, ordered columns → author the XML → validate locally → deploy and verify in the UI); the visibility strategy decision (all users vs owner-only/restricted, defaulting to all users); column-density guidance; and a common deployment errors table with fixes. Honest caveats: methodology plus XML authoring — you still deploy with the Salesforce CLI against your own org; every field name and picklist value must exist in the target org's schema or deployment fails. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: Salesforce org access (a free Developer Edition org works) and the Salesforce CLI for deployment — the skill is guidance the agent follows, not software to install Install "Author deployable Salesforce List View metadata XML" for me. It teaches my agent @forcedotcom's List View workflow: the critical rules (API names not labels, NAME/OWNER.ALIAS for standard fields, operations matching field types, file/fullName alignment, placement under objects/<Object>/listViews/), the 6-step workflow (requirements → existing examples → written spec → XML authoring → local validation → deploy and verify in the UI), the visibility strategy, and the common deployment errors table. Apache-2.0 licensed. Repository: https://github.com/forcedotcom/sf-skills/blob/main/plugins/builder/salesforce-development/skills/platform-list-view-generate/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "platform-list-view-generate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. hand the agent the target object API name and the view requirements; deploy the generated XML with the Salesforce CLI and verify records/columns/visibility in the UI yourself). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.