W-21685788: skill selection rule

[jodarove]

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

What changed

The added rule, makes the agent pick the best skill for each task step, instead of using one skill for everything. it improves plan quality, skill-task fit, and output accuracy by forcing per-task skill re-evaluation and skill switching when appropriate.

Why

It solves the common failure mode where execution quality drops because the agent:

• stays locked into an initial skill,
• applies a generic skill to specialized work,
• or reuses the same skill across unrelated tasks.

When testing AFV, there's only one skill selected for the whole process. depending on the selected skill, the task at hand went well or bad. Example: if using salesforce data as skill, then the app creation went bad, if using app creation, then the data part was bad.

Notes

I added the new rule (the one im testing with); i also tried to add it for a4v-global-rule; i will test the flow with the a4v-global-rules modification.

@W-21685788@

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)

[jodarove]

attaching a trace.md,

trace.md.zip

[gbockus-sf]

None of this should be required. I think we need to swing back to the specific case where a skill isn't getting called and so some analysis. Basically all of these should just be standard AFV behavior.

[gbockus-sf]

@mikemikula