> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/run-operations/agent/agent-context/skills/using-skills.md). # Use Skills Use Skills when you want the Agent to follow a reusable way of doing a job. Skills are reusable ways of doing work that the Agent can use during a session. ## Let the Agent choose when the match is clear Normally, describe the job you want done. The Agent can select an available Skill when it matches the task. You do not need to know the Skill name for every piece of work. ## Invoke a Skill when you want a specific method Use **/skill** when you want the Agent to follow a particular Skill deliberately—for example when several methods could plausibly apply. If this case should differ from the normal method, explain the exception for this task. ## Follow the result, not just the Skill name A Skill can use other Project capabilities while it works, including files, connected systems, Knowledge or Workflows. Follow the session activity and verify important outputs in the system or file that owns the result. ## When the Skill needs improvement If the same correction keeps returning, tell a builder. Skills can be reviewed, tested and published as improved versions rather than making operators repeat the correction every time. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lleverage.ai/run-operations/agent/agent-context/skills/using-skills.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.