Skills for programs
A skill is a folder with a SKILL.md file that teaches the agent a task it can reuse. Writing a skill is covered on Skills & custom commands. This page covers how a program controls the skills a run sees.
The Syntic Code SDK packages are not released yet. This page describes the behaviour of the syntic command today.
Which skills a run sees
Skills are found in the project and in your user folder when a run starts. A plugin installed for the run adds its skills too:
syntic -p "check the migration" --plugin db-tools@my-marketplace--plugin takes name@marketplace, and the marketplace must already be saved. See Plugins for programs.
To run without skills, use --bare: it turns skill discovery off for the run, together with plugins, hooks from settings files and auto-memory. --safe-mode does the same and also turns off instruction files and every MCP server.
Skills in the interactive app
In the app, type / and the skill name to start a skill, or use the skills list (/skills). Skills are read when the session starts. After changing a skill’s files in the interactive app, run /reload-skills to re-scan skills and custom agents without restarting. Plugin reloads use /reload-plugins. A print run (-p) reads skills once at start, so the next run picks up the change.
What a skill can set
A skill’s frontmatter can name a model, an effort level and a set of tools. Those fields are not applied to the run yet, so the skill runs with the settings of the session. Keep the run’s model and tool choices in the flags, not in the skill.
Limits
- A skill cannot widen the run’s permissions. The run’s permission mode and allow and deny rules decide what a skill’s tool calls may do. See Permissions for programs.
Related
- Plugins for programs covers how a plugin brings in skills, hooks and servers.
- Subagents for programs covers agents that can use skills.