A skill is how you want one kind of job done, written down — your house style, your invoice format, your review checklist. The AI picks the right one up by itself when a request matches, and tells you which it used.
Most people end up with a notes file of prompts and preambles they paste in. A skill is that file, made part of the account — and applied without being pasted.
A custom instruction applies to everything you say. A skill applies to one kind of task and stays silent otherwise, so ten skills do not contradict each other.
The same invoice format, the same tone, the same checklist — in a new conversation, on another device, and inside a background task.
Export a skill as a file, publish it to the site library for review, or scope it to one project so everybody working in that project gets it.
This is the part that makes skills cheap to keep: almost nothing is sent until one is needed.
/skill-name to load one deliberately, disable one you do not want considered, or scope it to a single project.Write the description as a trigger, not a title. “Drafts clear, polite email replies. Use when the user pastes an email and asks for a reply” gets picked up correctly. “Email helper” does not — the model has nothing to match against.
One click each to install, then edit them as your own — they are ordinary skills once installed, not locked presets. The second column is the description the model reads, which is also the clearest statement of when each one applies.
| Skill | Used when |
|---|---|
/data-analysis |
Analyses tables, CSV data and spreadsheets to find trends, summaries and insights with clear charts suggestions. Use when the user shares data and asks for analysis, insights, trends or a summary of numbers. |
/spreadsheet-formula |
Writes and explains spreadsheet formulas for Excel and Google Sheets. Use when the user asks for a formula, a VLOOKUP, a pivot, or how to calculate something in a spreadsheet. |
| Skill | Used when |
|---|---|
/invoice-writer |
Creates professional invoices and quotes with line items, tax and totals. Use when the user asks for an invoice, bill, quotation or estimate. |
/customer-support-reply |
Writes empathetic, solution-focused customer support responses and ticket replies. Use when the user pastes a customer complaint, support ticket or help request to answer. |
/business-proposal |
Drafts business proposals and project pitches with scope, timeline, pricing and next steps. Use when the user asks for a proposal, pitch, statement of work or project offer for a client. |
/decision-brief |
Turns a messy discussion into a one-page decision brief with options and a recommendation. Use when the user needs to decide something, asks to compare options, or wants a recommendation written up. |
| Skill | Used when |
|---|---|
/code-review |
Reviews code for bugs, security issues and maintainability with prioritised, actionable findings. Use when the user shares code and asks for a review, feedback, audit or "what is wrong with this". |
/sql-helper |
Writes and explains SQL queries for MySQL, PostgreSQL and SQLite, including joins, aggregates and indexes. Use when the user asks for a SQL query, database query help or query optimisation. |
/bug-report |
Turns a vague complaint into a reproducible bug report. Use when the user pastes a user complaint, error message or support ticket about something not working and wants it written up as a bug. |
/test-cases |
Writes test cases from a feature description or user story, including the edge cases. Use when the user asks for tests, test cases, QA steps or a test plan. |
| Skill | Used when |
|---|---|
/seo-article |
Writes search-optimised blog articles with a keyword plan, headings and meta tags. Use when the user asks for an SEO article, blog post for search, or content targeting a keyword. |
/social-media-post |
Writes platform-specific social media posts for LinkedIn, X/Twitter, Facebook and Instagram with hooks and hashtags. Use when the user asks for a social post, caption, tweet or LinkedIn update. |
/product-description |
Writes persuasive e-commerce product descriptions with benefits, specs and SEO keywords. Use for product listings, store descriptions, Amazon/Shopify copy or catalogue text. |
| Skill | Used when |
|---|---|
/meeting-notes |
Turns raw meeting transcripts or rough notes into structured minutes with decisions and action items. Use for meeting notes, call summaries, minutes or transcript clean-up. |
/interview-questions |
Builds a structured interview guide for a role, with scoring. Use when the user asks for interview questions, an interview guide or how to assess a candidate. |
/study-notes |
Turns material into study notes with a summary, key terms and self-test questions. Use when the user wants to learn, revise or memorise something, or asks for notes, a summary to study from, or flashcards. |
| Skill | Used when |
|---|---|
/email-reply |
Drafts clear, polite email replies. Use when the user pastes an email or message and asks for a reply, response or answer to send back. |
/translate-localise |
Translates and localises text naturally while keeping meaning, tone and formatting. Use when the user asks to translate text into another language or adapt copy for a region. |
/grammar-proofread |
Proofreads text for grammar, spelling and punctuation without changing the voice. Use when the user asks to proofread, check, correct or fix the grammar of something. |
/plain-english |
Rewrites jargon-heavy or legal text into plain English a general reader can follow. Use when the user asks to simplify, explain simply, remove jargon or make something easier to read. |
The common mistake is writing an essay. A skill works better as rules the model can check itself against.
quote-reply · Description: “Writes a price quote. Use when the user asks for a quote, estimate or price for work.”Write it in a form with a live preview, or switch to raw SKILL.md if you would
rather edit the file directly. Both produce the same thing.
A skill can carry files it may read — a rate card, a template, a style guide, a checklist — so the rules and the reference material stay together.
Every save keeps the previous version. If an edit makes replies worse, roll back — you do not have to remember what the good version said.
Skills follow the open Agent Skills shape — a name, a description and a body — so they move between tools rather than being locked in here.
20 starters, installed in a click and yours to edit afterwards.
Point at a repository or upload an archive; each skill is read, shown to you, and installed only after you confirm what it contains.
Any skill — built-in, written or imported — exports as a real SKILL.md, so
nothing you write here is trapped.
A skill you cannot measure is a guess. Test answers the same request twice and puts the two side by side.
The same prompt answered with your skill loaded and without it, in two columns, with the credits each one used. Most skills earn their keep in the first test; a few turn out to be doing nothing, and it is better to know.
When a skill is not loading by itself, the description is almost always the reason rather than
the body. Test with /skill-name to confirm the body is right, then sharpen the
description until the model reaches for it on its own.
Writing, importing, editing and storing skills costs nothing. Only the request that actually loads one is slightly larger, and the Test view shows by how much.
Your plan sets how many personal skills you can keep. The Skills page shows the number and what is left, and built-in installs count towards it like any other.
A skill shapes how the AI answers. It cannot send an email, spend credits on its own or change your settings — everything with a real-world effect still goes through the same confirmation as any other action.
A skill is a short set of instructions for one kind of job — how you want an email reply structured, what your invoices must contain, the checklist a code review has to follow. It is written once and stored on your account, and the AI applies it whenever a request matches.
From the skill's one-line description, which says when it applies. Only those one-liners are sent with a normal message, so having fifty skills does not make every request more expensive. The full instructions are loaded only for the skill that is actually used, and the reply tells you which one it was.
Yes. A persona or a custom instruction applies to everything you say. A skill applies to one kind of task and stays out of the way the rest of the time — which is why you can keep many skills without them fighting each other.
20 are built in across 6 categories and install with one click. You can also write your own in a form, paste one in, import from a GitHub repository or a zip, and attach files a skill may read.
Press Test on any skill. The same request is answered twice — once with the skill and once without — side by side, with the cost of each, so you can see the difference rather than assume it.
Writing, importing and storing them is free. A skill adds its instructions to the request that uses it, so that one request is slightly larger — the Test view shows exactly how much. Skills often reduce cost overall, because the first answer is closer to what you wanted.
Type /skill-name and it loads for that message whether or not the AI would have picked it. You can also disable one, scope it to a single project, or roll back to an earlier version.
Install /email-reply from the library, then edit it until the replies sound like
you. That is the whole learning curve.