chore: remove stale manifest.json and DOCS_ONLY.md @W-23538245@
manifest.json was a hand-curated skill registry last updated Feb 2026
that nothing consumes. DOCS_ONLY.md incorrectly states the repo contains
no code.
Add stability disclaimer to README
Skills are under active development and don't carry GA-level stability
guarantees. This note sets expectations for developers who fork or sync
the repo that skill names, structure, and availability may change without
notice.
Signed-off-by: Hemant Singh Bisht <hsinghbisht@salesforce.com>
fix: update stale skill name references to match new naming convention
- README.md: update folder structure examples from old names
(generating-apex, generating-custom-object, generating-flow) to new
names (platform-apex-generate, platform-custom-object-generate,
automation-flow-generate)
- samples/AGENT.md (b2e + b2x): update using-ui-bundle-salesforce-data
to experience-ui-bundle-salesforce-data-access
fix: allow nested YAML lists in metadata sub-keys (sync with internal)
The validator incorrectly rejected skills with list-type fields (e.g.
cliTools) nested under metadata sub-keys. This syncs the
parseMetadataBlock() fix from sf-skills-internal that distinguishes
direct-child lists from nested ones.
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Adds a new skill for Salesforce Flow Approval Processes
(processType: ApprovalWorkflow), a distinct flow type not covered
by the existing generating-flow skill.
Key contributions:
- Full architecture guide: orchestration, Background Steps, Approval
Steps, Screen Flows, WebLink trigger, Lightning page components
- Explicit delegation rule: AutoLaunched and Screen Flows are generated
via the generating-flow MCP pipeline; only the ApprovalWorkflow
orchestration XML is written manually
- Hard-stop constraints mapped to known deployment/runtime errors
- XML reference patterns in references/xml-patterns.md
- Common errors quick reference table with root causes and fixes
- Required deployment order to avoid dependency failures
