Claude Skills, explained.
Real sustainability work. Real patterns. And how to start using them this week.
A free guide from Sustained Futures · 12 minute read
Sustainability work is repeat work at scale.
The same disclosure paragraph gets rewritten four times a year for four frameworks. The same supplier data gets cleaned three times for three reports. The same change message gets reframed for six audiences for one rollout. AI should be making this lighter. For most teams, it is not.
Claude Skills change that. A Skill is a small set of instructions, examples and reference files that teaches Claude how your sustainability function actually operates. Once it is in place, the same recurring jobs draft themselves, in your house voice, against your frameworks, with your refusal list applied.
This guide shows how Claude Skills work in practice across the audiences a sustainability leader writes for, and the practical jobs that absorb the most of the working week. The result is a personal automation layer that gives hours back, without writing a line of code.
Read it end-to-end. Then pick the single most painful repeating task in your week, and try a Skill on it before Friday.
Two traps everyone falls into. There is a third option.
“I keep doing the same things over and over. Reformatting steerco notes, cleaning supplier data, redrafting the same disclosure paragraph for the fourth framework this year. I know AI should be helping more than it is, but I do not know how to make it actually stick.”
Head of Sustainability, UK retail
Fair. Most people use Claude like a search engine. Ask a question, get an answer, close the tab. The context vanishes and the work repeats. Worse, most people who try to push past that fall into one of two traps.
Prompt every time.
You re-explain the same context, the same tone, the same framework rules, the same banned phrases, over and over. Every task starts from zero. Outputs stay frustratingly generic. The promise of AI quietly evaporates.
Try to code it.
Inaccessible for most. Writing scripts needs developer skills the vast majority of sustainability leaders do not have. And the brittle scripts break the moment anything upstream changes, which in disclosure-land, it always does.
Claude Skills.
Small instruction files that teach Claude your patterns. So it handles recurring sustainability tasks on your behalf going forward. You can even schedule them, if you are feeling fancy.
A Skill is a folder of instructions Claude loads on demand.
The technical definition, from Anthropic, is that a Skill is a folder containing a SKILL.md instructions file plus any supporting reference documents. Claude reads the description, decides whether it is relevant to the job in front of it, and loads the rest only when it needs to. Skills work across claude.ai, the Claude desktop app, Claude Code and the Claude Agent SDK.
A one-line summary of when to fire.
The first line of every Skill. Tells Claude when to reach for this Skill versus another. The clearer it is, the more reliably the right Skill fires when you ask a question.
The recipe in plain English.
What to do, in what order, in what format, with what to avoid. House style, framework rules, your refusal list, your tone. Written the way you would brief a smart new hire.
Two or three worked outputs to imitate.
A prior-year disclosure paragraph. An approved manager FAQ. A board chart caption. Skills learn from examples more than from prose. Examples are the single biggest reliability lever.
Anything Claude should be able to read.
Your materiality matrix. Your emission factor library. Your house style guide. Your CMA Green Claims refusal list. Loaded only when relevant, so a Skill stays light.
Claude desktop app. File system access on.
Most sustainability workflows live in folders of files. The Claude desktop app is what gives Claude access to those folders. Set Skills up on the desktop interface the first time. The browser version of Claude can use Skills you have uploaded, but it cannot read your local file system.
Six steps from blank page to working Skill.
Open the Claude desktop app.
Claude Skills run inside the Claude desktop app, not the browser version. The desktop app is what gives Claude access to your file system, which is the unlock that makes recurring workflows possible. Download for Mac or Windows from claude.ai.
Decide which job you want to automate first.
Not the most strategic job. The most frequent and frustrating one. The disclosure paragraph you rewrite four times a year. The supplier survey clean-up you do every quarter. The board update format you reapply every month. Pick repetition over importance.
Write the Skill file in plain English.
A Skill is just a folder with a SKILL.md instructions file inside, plus any reference documents Claude should pull from. The instructions are written like you would brief a smart new hire: what to do, in what order, in what format, with what to avoid.
Add two or three worked examples.
This is the single biggest reliability lift you can give a Skill. Paste a before-and-after pair of real work into the Skill folder. Claude learns the pattern from your examples far faster than from any amount of prose instruction.
Test it on real work, then tighten.
Run the Skill on the next real version of that task. Note where it gets the tone, format or framework wrong. Edit the instructions, not the output. Iteration is part of the process. Most Skills hit usable quality on round three.
Share with your team.
Drop the Skill folder into your shared workspace. The next person who does the same job inherits your judgement, not a blank chat window. This is how a Skill becomes organisational memory rather than a personal hack.
The same data, the same evidence, four registers.
A sustainability leader writes for four audiences in any given week. The board wants decisions. Customers want assurance. Employees want what changes for them. Investors want comparable data. The same evidence base, four tones, four shapes. A Skill per audience is the cleanest way to hold the difference without losing the underlying truth.
Board and ExCo
- Quarterly sustainability board pack, drafted from your shared folder
- One-page CFO brief on the next CSRD or UK SRS S2 deliverable
- ExCo narrative for the next material risk update
- Decision-grade summary of any 40-page assurance report
Customers and prospects
- CDP, EcoVadis and customer RFP responses drawn from your answer library
- Sales enablement note: how to talk about our sustainability position
- Customer-facing sustainability statement, on-brand and on-message
- Tender response language that holds up under procurement scrutiny
Employees and managers
- All-staff email announcing a sustainability programme rollout
- Toolbox-talk script for site teams during audit and assurance weeks
- Manager FAQ for any change touching sustainability KPIs
- Onboarding paragraph on how the sustainability function works here
Investors and ratings agencies
- CDP, MSCI, Sustainalytics and ISS prep narrative pulled from prior cycles
- Investor Q&A briefing for the next earnings or capital markets day
- SBTi progress update letter in your treasury team’s tone
- Annual ESG section narrative, aligned to ISSB S2 with TCFD cross-references
The jobs that absorb most of the week.
Audience matters. Format matters more. These are the practical, repeating jobs that any sustainability leader can turn into a Skill on day one. Each one is built from the same four ingredients in section 02. The difference is how specifically you define the pattern.
Draft a LinkedIn post in your voice.
Loaded with your past posts, your point of view, your refusal list. Output is a draft that reads like you wrote it, not like a generic AI summary of the news.
Write a stakeholder email.
Same data, four registers. One brief becomes the CFO version, the procurement version, the works council version and the customer version. Tone tuned per audience.
Reformat steerco notes.
Rough notes in. House-format minutes out, with decisions, action items, owners, deadlines and any disclosure-impact flags pulled into the right sections.
Summarise a long supplier report.
40 page PDF reduced to a one-paragraph plain-English summary, plus a flag if anything in the document changes a disclosed metric or assurance position.
Tighten a paragraph to house style.
Drop in any draft. Get back the same content rewritten in your house tone, with banned phrases removed and your legal and CMA Green Claims refusal list applied.
Generate a board chart caption.
Paste in the data and the chart. Get back a caption that explains the movement, names the cause, and matches the chair’s preferred level of caveat.
Paste rough notes in. Shareable steerco doc out.
A lot of time gets quietly wasted here. You take rough notes during the sustainability steerco, then spend 30 minutes reformatting them into something shareable with the CFO, the board secretary and assurance. The Skill below handles that automatically. Copy it, save it as your first SKILL.md, and run it on the messiest notes you took last month.
Paste rough notes in.
Claude runs the Skill.
Shareable doc out.
Take the following rough sustainability steerco notes and reformat
them into a structured document with the sections below.
Preserve all names, dates, framework references and specific
figures verbatim. Do not round, do not paraphrase numbers.
Output format:
1. Meeting Summary (2 to 3 sentences max)
2. Decisions Made
- List each decision clearly, with owner if stated.
- Flag any decision that touches a disclosed metric or
assurance position.
3. Action Items
- Owner | Task | Framework or audience | Deadline
- Extract these from any phrase like "Anna to send the
scope 3 v2 file to PwC by Fri".
4. Risks and Open Questions
- Anything unresolved, contested, or flagged for legal,
assurance, or board review.
5. Disclosure Impact (optional)
- Note any item that changes a CSRD, ISSB S2, UK SRS S2
or CDP position. If none, write "None flagged".
Keep language concise. Do not add commentary or filler.
If a section has nothing to report, write "Nothing to flag".Run it on the messiest notes you took last month.
Paste this into Claude as your first Skill. Run it once on the messiest steerco notes you took in the past month. If the output is 80 percent there, tighten the wording and save it. Then run it on next Monday's sustainability standup. Every future meeting note gets formatted the same way.
You define the pattern, not the prompt.
Build once. Use forever.
Go deeper on Claude Skills.
Anthropic has published the technical reference and an end-to-end guide for building Skills. Worth bookmarking alongside this toolkit.
Serious about learning Claude Skills properly?
The Sustained Futures AI Academy covers this end-to-end. Six live sessions over six weeks, taught with sustainability leaders working on real disclosures, real supplier data and real boards. Recordings included. One finished workflow live in your real work by the end.
Six-week
cohort.
One a week,
six in total.
Ninety minutes.
Recordings included.
This is what Future Skills look like.