Skip to content

Remove redundant "When to Apply" sections from skill bodies#669

Merged
pushpak1300 merged 1 commit intolaravel:mainfrom
sulimanbenhalim:fix/remove-redundant-when-to-apply-sections
Mar 16, 2026
Merged

Remove redundant "When to Apply" sections from skill bodies#669
pushpak1300 merged 1 commit intolaravel:mainfrom
sulimanbenhalim:fix/remove-redundant-when-to-apply-sections

Conversation

@sulimanbenhalim
Copy link
Contributor

What

Removes the ## When to Apply section from 19 skill files across all variants (Livewire 2/3/4, Pest 3/4, Inertia React/Vue/Svelte v1/v2, Tailwind v3/v4, Folio, Flux UI free/pro, Volt, Wayfinder, Pennant)

Why

Both Anthropic's published docs and their internal skill-creator skill say the same thing

The Skill authoring best practices are clear that the description field owns "when to use":

"The description field enables Skill discovery and should include both what the Skill does and when to use it."

It also asks authors to challenge every token: "Does Claude really need this explanation?"

The skill-creator skill (Anthropic's meta-skill for building skills) goes further:

"All 'when to use' info goes here [in the description], not in the body."

Every removed section was already covered by the skill's description frontmatter — nothing was lost, just duplicate content loaded into context on every trigger

Verification

Each skill's ## When to Apply bullets were checked against its description field before removal — every bullet was already there. No triggering behavior changes, since the description is the only thing Claude reads to decide whether to invoke a skill

@pushpak1300
Copy link
Member

Thanks this make sense. The earlier skill-creator plugin add those section but the updated one is removing them so make sense to remove it. Also this needs to be removed from individual skill.

@pushpak1300 pushpak1300 merged commit 4996d04 into laravel:main Mar 16, 2026
23 checks passed
@sulimanbenhalim sulimanbenhalim deleted the fix/remove-redundant-when-to-apply-sections branch March 16, 2026 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants