CMS Search Skills by thrylokya · Pull Request #63 · forcedotcom/afv-library

thrylokya · 2026-03-17T20:08:22Z

References: Contributing guide · Skill authoring guide · Agent Skills spec

What changed

Why

Notes

Skills

Manual checklist

Description quality

Describes what the skill does and the expected output
Includes relevant Salesforce domain keywords (Apex, LWC, SOQL, metadata types, etc.)
Trigger phrases are specific enough for Vibes to select this skill reliably

Instructions

Clear goal statement
Step-by-step workflow
Validation rules for generated output
Defined output / artifact

Context efficiency

Core instructions are concise — supporting material lives in templates/, examples/, or docs/ subdirectories
No unnecessary background explanation in the body

Automated checks

Enforced by CI (npm run validate:skills) per the Agent Skills spec:

Directory is one level deep, named in kebab-case (max 64 chars), contains SKILL.md
Frontmatter name matches directory name; description is present, ≥ 20 words, ≤ 1024 characters, and includes trigger language
Body is non-empty and under 500 lines
Name uses gerund form ⚠ (warning — does not block merge)

hsinghbisht-sfdc · 2026-03-18T08:28:31Z

@@ -0,0 +1,86 @@
+---
+name: cms-media-options


This PR is not following proper skill directly structure and please make sure validate_skill check passes in the PR.

hsinghbisht-sfdc · 2026-03-18T08:29:05Z

+---
+name: cms-media-options
+description: REQUIRED entry point for ALL media and image searches. Every request to find, search, locate, retrieve, browse, get, look up, or use images, photos, pictures, media, icons, illustrations, hero images, banners, thumbnails, logos MUST go through this skill first. Checks which search sources are available, presents only those options, and delegates to the appropriate search skill based on the user's choice. Never search for media directly — always start here.
+license: Apache-2.0


Please remove this license.

hsinghbisht-sfdc · 2026-03-18T08:29:32Z

+license: Apache-2.0
+compatibility: Python 3.x or Python 2.7+ recommended, bash 3.2+ (Git Bash/WSL on Windows). Cross-platform: Mac, Windows (Git Bash/WSL), Linux, POSIX.
+metadata:
+  author: afv-library


remove author.

vratan-sf · 2026-03-18T12:34:00Z

Follow the folder structure here: https://agentskills.io/specification
Put scripts in the scripts/ folder.

Move stuff from your rules file into SKILL.md. You only want a skill, not a rule. You can also break down your skill.md file into multiple markdown files. The main markdown is in SKILL.md while the other markdown files can be in the references folder and referred from SKILL.md

vratan-sf · 2026-03-20T05:42:18Z

Please follow the skill naming conventions here
"Skill names should use gerund form (verbs ending in “-ing”). Gerund-based names create a clear and readable skill library. "
So, perhaps your this skill name can be something like "searching-cms-d360" or some such. Similarly, change the name of the other 2 skills.

skesanthosh · 2026-03-20T07:46:27Z

@@ -0,0 +1,40 @@
+---
+name: cms-d360-search
+description: Data Cloud AI Hybrid Search via search_electronic_media or search_content_in_d360 MCP tool. Performs semantic search across Salesforce CMS and 3rd-party DAMs using natural language queries. Invoked from cms-media-search when the user selects Data Cloud – AI Hybrid Search.


@thrylokya is there any reason for mentioning search_content_in_d360? our tool is search_electronic_media

@skesanthosh : I am not going to merge this right away. So, there are 2 approaches I am trying. First, is to have a modular one and see if skills are rightly invoked from another skill. Based on our observations, this is not happening too consistently.
The other approach is to have the entire functionality in one skill making it less modular. Based on how our Blitz goes, we will decide on teh approach.
On the naming convention, I already asked Alex for the labels. Once she is back with her suggestions, I can merge them.

skesanthosh · 2026-03-20T07:48:57Z

+
+Semantic search across Salesforce CMS and connected 3rd-party DAMs. Invoked by `cms-media-search` when the user selects **Data Cloud – AI Hybrid Search**.
+
+Best for natural language queries, cross-system searches, and semantic similarity (vs exact keyword matching).


Hybrid Search includes both Vector/Semantic + Keyword based matching

Based on our observations, a skill invoking from another skill is not happening too consistently(this we observed in blitz). So just trying out various options.

skesanthosh · 2026-03-20T07:56:45Z

@@ -0,0 +1,40 @@
+---
+name: cms-d360-search


I think we should not have cms prefix for this skill, we didn't have it in the tool name either

skesanthosh · 2026-03-20T07:57:31Z

@@ -0,0 +1,40 @@
+---
+name: cms-d360-search
+description: Data Cloud AI Hybrid Search via search_electronic_media or search_content_in_d360 MCP tool. Performs semantic search across Salesforce CMS and 3rd-party DAMs using natural language queries. Invoked from cms-media-search when the user selects Data Cloud – AI Hybrid Search.


Minor: "Invoked from cms-media-search when the user selects Data Cloud – AI Hybrid Search." is this required in description?

skesanthosh · 2026-03-20T08:00:50Z

+
+Input: `query` = the user's search query string. Refer to the tool's schema for additional parameters.
+
+## Step 3: Present Results and Handle Selection


Just wondering, are we having this skill just for this step 3? because the tool description and input schema are enough for invoking the tool with right parameters.

thrylokya added 2 commits March 18, 2026 01:36

added cms search skills

2b0ce1a

added cms search rule

f0f1c64

hsinghbisht-sfdc reviewed Mar 18, 2026

View reviewed changes

vratan-sf reviewed Mar 18, 2026

View reviewed changes

thrylokya added 10 commits March 20, 2026 08:59

Merge branch 'forcedotcom:main' into main

7a1f865

Created cms-d360-search

e0529fd

Created cms-d360-search

4fbd0e0

Created cms-media-search

4c13958

Delete rules/a4d-image-search-routing-rule.md

6a4ed00

Delete skills/build_cms_search_input.py

70d7406

Delete skills/build_cms_search_input.sh

1db330b

Delete skills/check_mcp.py

59d7edd

Delete skills/check_mcp.sh

5e6352e

Delete skills/SKILL.md

7650288

vratan-sf reviewed Mar 20, 2026

View reviewed changes

Merge branch 'main' into main

5961882

skesanthosh reviewed Mar 20, 2026

View reviewed changes

thrylokya added 7 commits March 20, 2026 16:29

Delete skills/cms-d360-search directory

6be8da9

Delete skills/cms-keyword-search directory

71bb1d8

Delete skills/cms-media-search directory

36e89c4

Create searching media SKILL.md

e515d3c

Update SKILL.md

bdf0ff8

Update SKILL.md

e1764f5

Update use-skills.md

513b27d

thrylokya added 10 commits March 24, 2026 01:39

Update SKILL.md

3af96f7

Merge branch 'main' into main

9bb0d37

Update SKILL.md

1aa66ef

Merge branch 'main' into main

2441aa3

Update SKILL.md

ea83058

Update SKILL.md

e3c5f1b

Delete rules/vibe-coding/use-skills.md

5c74072

Create use-skills.md

28cf871

Merge branch 'main' into main

0394e98

Update use-skills.md

81d4fc1

thrylokya closed this by deleting the head repository Mar 26, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CMS Search Skills#63

CMS Search Skills#63
thrylokya wants to merge 30 commits intoforcedotcom:mainfrom
thrylokya:main

thrylokya commented Mar 17, 2026

Uh oh!

hsinghbisht-sfdc Mar 18, 2026

Uh oh!

hsinghbisht-sfdc Mar 18, 2026

Uh oh!

hsinghbisht-sfdc Mar 18, 2026

Uh oh!

vratan-sf Mar 18, 2026

Uh oh!

vratan-sf Mar 20, 2026

Uh oh!

skesanthosh Mar 20, 2026

Uh oh!

thrylokya Mar 20, 2026

Uh oh!

skesanthosh Mar 20, 2026

Uh oh!

thrylokya Mar 20, 2026

Uh oh!

skesanthosh Mar 20, 2026

Uh oh!

skesanthosh Mar 20, 2026

Uh oh!

skesanthosh Mar 20, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants


		Semantic search across Salesforce CMS and connected 3rd-party DAMs. Invoked by `cms-media-search` when the user selects Data Cloud – AI Hybrid Search.

		Best for natural language queries, cross-system searches, and semantic similarity (vs exact keyword matching).


		Input: `query` = the user's search query string. Refer to the tool's schema for additional parameters.

		## Step 3: Present Results and Handle Selection

Conversation

thrylokya commented Mar 17, 2026

What changed

Why

Notes

Skills

Manual checklist

Automated checks

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants