Adding Skills to Agents

attach skills to your inference.sh agents so they can load context on demand.

from the registry

the fastest way to add a skill:

1. open your agent's settings → prompt tab
2. scroll to the skills section
3. click browse to open the skill browser
4. search and select a skill

the skill's name, description, and URL are filled in automatically.

by URL

point to any skill hosted anywhere:

1. in the skills section, click + url
2. fill in:

1name: api-docs2description: REST API documentation for the payment service3url: https://api.inference.sh/skills/yourteam/api-docs/content

the URL can point to:

• a skill on inference.sh (https://api.inference.sh/skills/{ns}/{name}/content)
• a raw file on github (https://raw.githubusercontent.com/...)
• any HTTPS URL that returns text/markdown

inline

write skill content directly in the agent config:

1. click + text
2. fill in name, description, and the content itself

good for short, agent-specific instructions that don't need to be shared:

1name: response-style2description: guidelines for tone and formatting3content: |4  always respond in lowercase.5  use bullet points for lists.6  keep responses under 200 words unless asked for detail.

how skill_get works at runtime

when your agent runs, the skills you've added appear in the skill_get tool:

1skill_get: retrieves skill content.23available skills:4- code-review: guidelines for reviewing pull requests5- api-docs: REST API documentation for the payment service67parameters:8  skill: the name of the skill to retrieve9  path: optional path to a supporting file (e.g. references/api-docs.md)

the agent decides when to call skill_get based on the conversation. typical flow:

1. user asks something related to a skill's description
2. agent calls skill_get(skill="code-review") → gets the main instructions
3. if the instructions reference supporting files, agent calls skill_get(skill="code-review", path="references/checklist.md") → gets the specific file
4. agent uses the loaded context to respond

content is cached per session — loading the same skill twice doesn't re-fetch.

how many skills?

there's no hard limit, but keep descriptions concise. every skill adds a line to the tool description. 5-15 well-described skills is a good range — enough to cover the domain without overwhelming the agent's context.

if you find yourself adding 20+ skills, consider whether some should be supporting files within a parent skill rather than separate skills.

next

• creating skills — build your own skills
• using with other agents — install skills to Claude Code, Cursor, and more
• skills overview — how skills work