Agent Skills sound like a developer thing. The idea behind them is simple enough that anyone who writes instructions for a team can understand it, and it is worth knowing even if you never open a code editor.

The short version

An Agent Skill is a folder. The one required file is called SKILL.md. It holds a short name, a description of when the skill applies, and the instructions an AI agent should follow when a task matches. Optional extras sit beside it: a scripts folder, reference notes, templates. That is the whole format.

The official overview describes it as "a lightweight, open format for extending AI agent capabilities with specialized knowledge and workflows" and puts the core in one sentence: a skill is a folder containing a SKILL.md file. [Source: agentskills.io/home]

Why it exists

An agent can be capable and still not know how your team does things: how a monthly report is laid out, which checks a document review needs, what a good follow-up after a site visit looks like. Writing that down once in a folder means you stop re-explaining it every time.

The overview describes three stages. At startup the agent sees only each skill's name and description. When a task matches, it reads the full SKILL.md. Then it follows the steps, running bundled code or opening referenced files only when it needs them. Because the full instructions load only when a task calls for them, an agent can keep many skills on hand without filling up its working memory. [Source: agentskills.io/home]

What it looks like in practice

Google publishes a public repository of skills for its own products and cloud services, each one a folder built to the same format. The README shows installing them with a single command. [Source: github.com/google/skills] Open one folder and read its SKILL.md from top to bottom. It takes about ten minutes, and you will understand the format better than from any summary, including this one.

Now think of something you already do every week. "Draft a follow-up message after a site visit." "Summarise the week's enquiries into three bullets." The description says when the skill applies. The instructions say how to do it. Your own version is a text file.

A non-coder's check before you trust one

Three questions, asked before you let any skill touch real work:

  1. Does the description say clearly when it applies? A vague description means the agent fires it at the wrong moment.
  2. Are the steps checkable? "Make it good" is not a step. "List the three numbers you used and where each came from" is.
  3. Does it do anything irreversible, like sending a message or paying for something? Read those lines twice, and keep a human in that step.

Where to start

Pick one task you repeat every week. Write its steps as plain sentences, the way you would explain it to a new colleague. Put them in a folder with a SKILL.md at the top. You have just made a skill, whether or not anyone else ever uses it.

Sources: agentskills.io/home (the Agent Skills overview), github.com/google/skills (the repository README).

— Devesh Sarkaar, founder of Aivesh Academy & Gharleads, Indore