Anthropic dropped a 33-page guide on Skills. Most people at your office have no idea it exists. Here's how to use it before they do — with 10 ready-to-use Skills for your 9–5.
A Skill is a reusable instruction set you upload to Claude once. After that, Claude automatically loads it whenever your task matches — no re-explaining, no re-prompting, same output every time.
If your company is on Claude's Team or Enterprise plan, an admin can deploy a Skill across the entire organization at once — everyone gets it automatically.
Available on free, Pro, Max, Team, and Enterprise plans.
Build a Skill for something your whole team does repeatedly
Pick one workflow everyone runs — weekly reports, meeting recaps, client emails. Build the Skill once. Takes less than 15 minutes.
Bring it to your manager and say:
"I built this Skill in Claude — everyone on the team can use it now."
Keep a list of every Skill you built and what it saved
Time saved. Errors reduced. Hours reclaimed. Track it as you go.
Walk into your annual review with receipts
You didn't just do your job. You made everyone around you better at theirs. That's the kind of thing that gets people promoted.
Teach Claude this — then save it as a skill
"When I say 'weekly status', I'll give you my notes from the week. Write a status report with: (1) Overall RAG status — Red, Amber, or Green, with a one-line reason. (2) Accomplishments this week — 3–5 bullets, specific. (3) Priorities for next week — top 3. (4) Blockers or decisions needed — what I need from others and by when. Lead with what changed and what matters. Never pad length. Save this as a skill called 'weekly status'."
Teach Claude this — then save it as a skill
"When I say 'recap for [meeting]', I'll give you my rough notes. Build a meeting recap with: (1) Key decisions made — numbered, specific. (2) Action items — each with owner name, specific task, and due date. (3) Open questions still unresolved, with a suggested next step for each. Format it ready to copy directly into an email or Slack. Save this as a skill called 'meeting recap'."
Teach Claude this — then save it as a skill
"When I say 'draft email to [person] about [topic]', write a professional email that gets to the point in the first sentence, is calibrated to the relationship (internal vs. external, peer vs. senior), and ends with a single clear ask or next step. No filler openers like 'Hope this finds you well.' Under 150 words unless the situation requires more. Give me 2 versions — one direct, one slightly warmer. Save this as a skill called 'email draft'."
Teach Claude this — then save it as a skill
"When I say 'summarize this data', I'll paste numbers, a spreadsheet export, or a metrics dump. Give me: (1) The 3 most important insights — what the data is actually saying. (2) The biggest change or trend vs. prior period. (3) One recommended action based on what you see. Lead with the insight, not the numbers. Format as an executive summary I can paste into a report or email. Save this as a skill called 'data summary'."
Teach Claude this — then save it as a skill
"When I say 'polish this slack', I'll paste a draft. Rewrite it to be clear, professional, and the right length — no filler words, nothing that could be misread, no excessive formatting. If it's asking for something, make the ask obvious. If it's informing, make the key point land in the first sentence. Keep my voice — just sharpen it. Save this as a skill called 'slack polish'."
Teach Claude this — then save it as a skill
"When I say 'project update for [project]', I'll give you where things stand. Write a stakeholder update with: (1) Current status — one sentence. (2) What's been completed since the last update. (3) What's coming next and when. (4) Any risks or blockers, and what's being done about them. (5) What I need from stakeholders, if anything. Clear and scannable — stakeholders should be able to read it in 30 seconds. Save this as a skill called 'project update'."
Teach Claude this — then save it as a skill
"When I say 'review prep', I'll give you a list of things I've done this year. Transform them into compelling self-review language: quantify every impact where possible, frame each item in terms of what it meant for the team or business (not just what I did), and highlight any moments where I went beyond my role. Structure: wins with impact, skills demonstrated, how I made people around me better. This is for my annual review. Save this as a skill called 'review prep'."
Teach Claude this — then save it as a skill
"When I say 'agenda for [meeting]', build a structured agenda with: pre-read materials listed at top, meeting objective in one sentence, time-boxed agenda items (each with an owner, time allocation, and whether it's a decision, discussion, or update), and a parking lot section at the bottom. Total time should match the meeting length. Every item needs a clear purpose — no vague topics. Save this as a skill called 'meeting agenda'."
Teach Claude this — then save it as a skill
"When I say 'summarize this doc', I'll paste or upload a document. Give me: (1) What this document is and why it matters — 2 sentences. (2) The 3–5 most important points. (3) Any decisions, commitments, or action items in it. (4) Anything I need to respond to or follow up on. Format as a scannable brief I can reference in a meeting without having read the full document. Save this as a skill called 'doc summary'."
Teach Claude this — then save it as a skill
"When I say 'help me write this', I'll describe a difficult communication — pushing back, delivering bad news, declining a request, a sensitive ask. Write 2 versions: one that's direct and clear, one that's slightly softer in tone. Both should be professional, specific, and avoid being passive-aggressive or over-apologetic. Tell me which one you recommend and why. Save this as a skill called 'difficult message'."
STEP 1
Enable Skills in Settings
Go to Settings → Capabilities and turn on Code execution and file creation. Then go to Customize → Skills. Works on all plans — free, Pro, Max, Team, and Enterprise.
STEP 2
Enable the "skill-creator" skill
Anthropic built a skill specifically to help you build skills. Find it in your Skills list, enable it, then start a conversation. Claude will interview you about your workflow and generate the skill file automatically — no manual editing required.
STEP 3
Download, ZIP, and upload
Claude creates the skill as a folder. Download it, ZIP it, then go to Customize → Skills, click the "+" button → Upload a skill, and upload the ZIP. Your skill appears in your Skills list.
STEP 4
Toggle it on — Claude does the rest
Claude detects when your task matches the skill and loads it automatically. You'll see it activate in Claude's thinking as it works. No trigger phrase required — though you can describe the task and it activates.
Team & Enterprise
Admins can push skills to the entire org from Organization Settings → Skills. Once deployed, every team member gets it automatically — no individual setup. This is the career play.
Full 33-page guide: resources.anthropic.com/hubfs/The-Complete-Guide-to-Building-Skill-for-Claude.pdf
© 2026 Mariah Brunner. All rights reserved.