skill-optimiser-description

Reducing false positives involves refining the frontmatter and description to define realistic prompt examples and trigger boundaries. This clarifies expected outputs and prevents overlapping with broader tasks during validation workflows.

Your skill triggers on broad prompts because its description lacks specific trigger boundaries and realistic prompt examples. Refining the frontmatter clarifies the expected output and prevents overlapping with neighboring tasks to stop unwanted activations.

Defining trigger boundaries requires specifying when to use the skill, its concrete output, and probable user prompts directly in the frontmatter. This approach isolates the skill from neighboring tasks and reduces false positives during validation.

Yes, you can apply prompt-engineering to fix skill descriptions by rewriting them to include probable user prompts and expected outputs. This clarifies the trigger conditions and ensures the skill activates correctly during publication workflows.

You need to refine a skill description when it triggers on broad prompts or overlaps with larger tasks during validation. Rewriting the frontmatter to specify trigger limits, expected outputs, and realistic prompts prevents these unwanted activations.