Skip to content
Promptsio
Search prompts, tools, agents…

How-to guide

Write a skill description that actually triggers

The description decides whether your skill ever loads. Learn what to put in it, with weak and strong examples and a quick way to test it.

  • Time 10 min
  • Level Intermediate
  • Steps 5
  • Updated

The AI sees only the name and description of every installed skill. If the description does not match what the user asks, the skill never runs, however good the instructions are.

Step by step

0/5 done

  1. 1 Say what it does and when to use it

    Write one sentence for each. A good pattern: "Does X. Use when the user asks for Y or mentions Z."

  2. 2 Use the user's words

    People say "summarise the call", not "synthesise a transcript". Include the phrases, file types and tools they actually mention.

  3. 3 Weak versus strong

    Weak: Helps with documents.

    Strong: Turns meeting notes or a transcript into decisions, action items with owners, and open questions. Use after any meeting or when the user pastes notes.

  4. 4 Keep it focused

    A description that claims too much will load for the wrong tasks. If you need "and also", consider a second skill.

  5. 5 Test it

    Write five requests that should trigger the skill and five that should not, and try them. Adjust the wording until it loads for the first group and stays quiet for the second.

Was this helpful?