What is a "skill" — and how the agent publishes your site
In Zero to a live website, the last step said: "ask the agent to add a favicon, robots.txt, llms.txt and sitemap." One instruction — done. It works because there's a skill behind it. Once that clicks, it speeds up everything.
A skill = a remembered procedure
A skill is a small recipe the agent remembers. Instead of improvising each time (and re-making the same mistakes), it reaches for the proven steps and runs them the same, well, every time. You say what you want; the skill knows how.
Analogy: like a craftsman's checklist that never forgets a step — except here the agent runs the checklist for you.
Example: "launch a website"
Ask "give this site its basic launch" and the web-launch skill produces the things that make a site feel grown-up and discoverable by people and AI:
- favicon — the little browser-tab icon (a missing one is that ugly empty box).
- robots.txt — tells search engines (and AI crawlers) what they may read.
- llms.txt — newer: briefly tells AI models what your site is about, so they cite you correctly.
- sitemap.xml — a map of your pages for search engines.
- Open Graph preview — the nice card shown when you share the link.
- canonical + hreflang — tidy URLs and languages.
How you run it — copy this to the agent:
Run a basic "web launch" on www-<slug>: favicon, robots.txt, llms.txt,
sitemap.xml and an Open Graph preview. Follow our proven skill.
That's it — the agent runs the recipe, you check the result.
Why it matters
- Nothing gets forgotten — the steps are always complete.
- Consistency — your tenth site looks as grown-up as your first.
- AI-friendly —
llms.txtis literally a note to the robots: "cite me like this." That's our whole motto.
Pro: a skill can be shared and installed (as a plugin) — and you can build your own: anything you explain to the agent twice, turn into a skill, and next time it runs itself. That's the difference between "chatting with an AI" and "having a tool that does the craft for you."