Skip to content

@W-21482430 feat: migrate exp lwr site knowledge docs to skill#27

Merged
hsinghbisht-sfdc merged 29 commits intoforcedotcom:mainfrom
scottmo:experience-lwr-site
Mar 18, 2026
Merged

@W-21482430 feat: migrate exp lwr site knowledge docs to skill#27
hsinghbisht-sfdc merged 29 commits intoforcedotcom:mainfrom
scottmo:experience-lwr-site

Conversation

@scottmo
Copy link
Copy Markdown
Contributor

@scottmo scottmo commented Mar 11, 2026

Migrated knowledge docs from Expert Framework MCP to skill.

Also made some changes to re-organize some of the sections and added TOC for longer knowledge docs based on https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices#structure-longer-reference-files-with-table-of-contents.

@W-21482430@

- **keyPrefix**: 3-character identifier unique to each standard object (Account=001, Contact=003)
- **ObjectApiName**: Custom object API name including the "__c" suffix

Obtain object information from the `objectList` output:
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the objectList + knowledge are no longer together in one response - do you see any issues of this instruction referencing the output from the IA? Just wondering

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be fine.


- `type`: Always `"sfdc_cms__view"`
- `title`: Human-readable display title (e.g., About Us)
- `contentBody`: Include all `required` properties from `schemaDefinition`. Use `examplesOfContentType` for reference.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With skills do we get this schemaDefinition?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will be from MCP. That's why I mentioned we still need MCP.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@scottmo scottmo changed the title feat: migrate exp lwr site knowledge docs to skill @W-21482430 feat: migrate exp lwr site knowledge docs to skill Mar 13, 2026
@salesforce-cla
Copy link
Copy Markdown

Thanks for the contribution! It looks like @jeffcarey is an internal user so signing the CLA is not required. However, we need to confirm this.

@@ -0,0 +1,196 @@
---
name: salesforce-experience-lwr-site
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please follow the recommended naming recommendation for skills

Just to follow consistent pattern which we are about to do for all other existing type is generating* i.e. generating-experience-lwr-site

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this PR is old, going ahead with merge, we will track this change as part of PR #53

@hsinghbisht-sfdc hsinghbisht-sfdc merged commit 690f722 into forcedotcom:main Mar 18, 2026
2 checks passed
@scottmo scottmo deleted the experience-lwr-site branch March 18, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants