How to write a Skill

From Tygron Support wiki
Jump to navigation Jump to search

When to write skills:

  • Repeated task that need to be done the same every time.
  • Domain specific information, such as terminology, runbooks and style guides.
  • Specifications, schemas and configurations
  • Failure cases and their resolutions.

When not to write skills:


How to write a Skill:
  1. Choose a unique name
  2. Write a short description (one or two sentences) of what this skill does and when it should be used
  3. Write the skill content using short sentences and a limited amount of lines
  4. Test your skill repeatedly
  5. Move what should be put in a separate skill
  6. Remove what can be cut

Tips

  • Moderate detail: Not too comprehensive, but also not too exhaustive. Border cases can be put in separate skills.
  • Stepwise guidance, preferable with working example.
  • Keep description under 1024 characters.
  • Keep instructions under 500 lines or 5000 tokens.
  • Tell Agents when to perform an action