01 / 13
LT Skills Workshop · Thursday
Linktree
A working session
Agent
Skills.
Building AI workflows that last past one person and one tool.
Unblocking Ourselves · Linkup 2026
02 / 13
The hook
Agent Skills
For the first time, we have a system that can be used to improve itself.
Agents can now capture how you work and run it for you. The discipline is learning to build that capture.
03 / 13
Quick calibration
Hands up
Where is the room?
Q1
Who has saved a CLAUDE.md or AGENTS.md file?
Hands up
Q2
Who has built or installed a skill?
Hands up
Q3
Who has run a scheduled agent (Cowork or otherwise)?
Hands up
04 / 13
The mechanic underneath
It's all text
It's all just text.
LLMs predict the next word from everything that came before. A "chat" is the whole history re-sent each turn. There's no memory.
Sent to the model · every turn
Context
CLAUDE.md, brand docs, anything pre-loaded about you and your team.
Tools
Definitions of what the agent can call: Slack, Drive, Notion, Gmail.
Skills
SKILL.md content loaded when relevant to the task.
History
Every previous turn of this conversation.
You
What you just said.
Context, Tools, and Skills are just three ways to control what's in that window when the model goes to work.
05 / 13
A skill is a file
Demystify
A skill is just a file.
Markdown, with instructions for one specific task. Loaded into the window when relevant.
---
name: weekly-team-update
description: Draft Friday's team update from Linear and Slack
---
# Weekly Team Update
1. Pull last week's closed Linear tickets
2. Group by team, link the Slack threads
3. Format as bullet list, source-linked
Avoid: speculative status, old dates, anything before Monday.
Same format runs in Claude (claude.ai, Claude Code) and Codex. Open standard.
06 / 13
The spectrum of skill sources
Three ways
Three ways to get a skill. The most useful one is the least common.
Option A
Rip
verbatim.
A skill from the directory, used exactly as published. No edits.
Option B
Mold
to fit.
A pre-built skill you've edited for your team's voice and stack.
Option C · Highest leverage
Tailor
from your work.
Built from a real working session you've already done. Knows your edge cases. Knows what to avoid.
← Generic, fast
Specific, durable →
07 / 13
The stack underneath
Three layers
Skills sit on a stack. Most teams skip the bottom two.
Skills
The captured workflow.
Tools
What the agent can reach.
Context
What the agent knows about you and your team.
One example per layer
Skills
Draft a performance review · Summarise a meeting · Triage a ticket queue · Prepare a deal brief
Tools
Slack · Notion · Drive · Gmail
Context
A P&C team's tone of voice and role rubric
08 / 13
The technique
A recipe
Creating skills as you go.
Step 01
Do the task
with the agent.
Until the output is actually good. Iterate, correct, push back. The session itself is the source material.
Step 02
Run
/skill-creator
Reads your session, asks clarifying questions, writes the SKILL.md including what to avoid.
Step 03
Run the skill
next time.
Repeatable. Shareable. Improves with each run.
/skill-creator is a built-in skill (Anthropic and OpenAI both ship one).
The "what to avoid" part is the piece you can't get from a generic pre-built skill.
09 / 13
Up next · live walkthrough
~15 min
What to watch for
A marketing example.
sem-weekly-report
Pulls Google Ads data · generates charts · classifies campaigns · posts to Slack.
The shape will be familiar. The content won't be. As I demo, point at which layer I'm touching: Context, Tools, or Skill.
10 / 13
The shape of a good task
Examples
Pick something shaped like these.
Small, recurring, leans on tools we have connectors for.
Designer
Brief from a Figma frame.
FigmaNotion
Support
Reply matching our voice.
Gmail
HR / P&C
JD from a role rubric.
NotionDrive
BD
Follow-up from call notes.
DriveGmail
Legal
Doc summary for an exec.
Drive
Product
Triage a Linear issue.
LinearSlack
11 / 13
Group block · ~35 min
Your turn
Build a skill for a real task.
By the end of this block, your group has a working skill they can use Monday. Three steps, in order.
Step 01 · Context
~10 min
Write it
down.
A shared file describing your team. What you do. The language you use. What's off-limits.
CLAUDE.md
tone
rubrics
Step 03 · Skill
~15–20 min
Make
one.
Pick one task you all do. Run it through the agent. Run /skill-creator. Test it on a slightly different version.
/skill-creator
test & refine
12 / 13
Take it back
Monday
What to do Monday.
01
Context
Save the file your group built. Drop it in your team's shared space.
02
Tools
Add one connector you don't have yet.
03
Skill
Build one skill from a task you actually did this week. No hypotheticals.
Ongoing momentum
#learning-ai-winsandwhoopsies
13 / 13
Close
Thanks
Build the stack while you're
doing the work.