Agent skills for data jobs: what a SKILL.md holds

An agent skill is a plain markdown file that teaches your agent one job. It says when to start, what to ask the user for, which tools to call in which order and how to hand the result back. Claude Code reads skills from a folder, and the same file works as written instructions in any agent that accepts them.

Skills matter most for data jobs, because that is where agents improvise. Ask an agent for someone's work email with no instructions and it may guess a pattern. A skill replaces the guess with a procedure.

What is an agent skill?

A skill is one file called SKILL.md in a folder named for the skill. The file starts with a short block of metadata, a name and a description, then plain instructions. The description decides when the agent picks the skill, so it holds the phrases a user would say.

In Claude Code the folder lives in `~/.claude/skills/`. The agent reads every skill's name and description, and loads the full file only when the task matches. That keeps a large set of skills cheap to carry.

What does a good data skill hold?

Six parts, in this order.

1. The trigger. Three or four phrases a user would say, in the description.
2. The inputs. What the agent must ask for when the user has not given it, such as a company domain next to a name.
3. The calls. Which endpoints to try, and in what order.
4. The fallback. What to do when a provider fails, and what not to retry.
5. The answer rule. How to report the result, and what to say when nothing was found.
6. The cost rules. Read the price first, say it, and stop after two failures.

The last three are where a skill earns its place. Without an answer rule an agent will present a guessed email as a fact. Without a cost rule a failing loop keeps spending.

What does a real skill look like?

This is the shape of the looot skill for finding a professional email, shortened. The full file is on the skill page and you can fetch it raw.

---
name: looot-find-professional-emails
description: Find a professional email. Use when the user says things like "find the work email of Jane Doe at example.com". Runs through looot, billed per call.
---

## Ask for these inputs
- Full name of the person
- Company domain, such as example.com

## Run it
1. looot discover --mode auto --query "professional email finder"
2. looot inspect <endpoint-id>   (read the price, tell the user)
3. looot run <endpoint-id> --input '{...}' --idempotency-key <key> --wait
4. On a provider error or timeout, try the next endpoint. On a bad input, fix the input.

## Answer rule
Give the email, its verification status and the confidence score on one line.
Never present an unverified address as confirmed.

How do I install one?

Set up looot once so the agent has the commands. Then save the skill file where your agent reads skills.

For Claude Code, one command does it:

mkdir -p ~/.claude/skills/looot-find-professional-emails && curl -fsSL https://looot.ai/agent-skills/find-professional-emails/SKILL.md -o ~/.claude/skills/looot-find-professional-emails/SKILL.md

Every skill in the library has the same command with its own name. For other agents, paste the file into the place that agent keeps instructions.

Does a skill cost anything?

The file is free. Running it is billed per call at the price the agent reads with the inspect command before the run. A skill never writes a price into the file, so the number the agent quotes is the one in force at run time. What an AI agent costs explains how to estimate a job from those prices.

Try it: a prompt for your agent

What it cannot do

• A skill is instructions, not a guarantee. The agent can still ignore one, so keep the rules short and specific.
• A skill does not make a provider return data it does not have. A miss is still a miss.
• looot does not run skills on a schedule. Anything that needs scheduled runs is not available yet.

Last checked 2026-10-04 against the looot skill file and the skill library. Author: the looot team.