← Client success

Implemented · Claude skills

Claude skills for weekly workflows

Reusable skills for real jobs. No engineering degree required.

2h/wk Time saved
15% Efficiency up
~$5K Future $ / yr

What we built

We shipped Claude skills for the tasks people already repeat: first drafts, follow-ups, cleanup, and summaries. Each skill is a clear playbook anyone on the team can run.

Result

About 2 hours saved per person per week on routine work. People spend more time on high-ROI activity instead of rewriting the same emails and notes.

Demo

See it in action.

Claude ✦ Skills

follow_up.skill loaded

Live demo

Repeat work,
written once.

A skill is a playbook Claude runs the same way every time.

Drafts Follow-ups Cleanup Summaries

01 · The playbook

follow_up.skill Skill

01 Pull names, dates, and asks from the visit notes

02 Short sentences. No jargon.

03 One clear ask at the end

04 Close in our voice, not template-speak

Plain English. Anyone on the team can read it — or fix it.

02 · Run it

Account manager
You
Draft the follow-up for the Henderson site visit
Claude · follow_up.skill
follow_up.skill visit_notes.txt
To · R. Henderson Subject · Thursday's walkthrough — next step

Good speaking Thursday. Per your note, the loading-dock retrofit fits your Q3 window. Can we hold March 4 for the site survey?

Ready to paste, straight from your notes.

03 · Before / after

Raw notes

hendersn thurs — dock retrofit?? q3 maybe. wants survey date. march?? f/u asap

Ready to send

Good speaking Thursday. The retrofit fits your Q3 window — can we hold March 4 for the survey?

04 · The team library

SK
follow_up.skill After every site visit
Shared
SK
weekly_notes.skill Monday summaries
Shared
SK
crm_cleanup.skill Pipeline hygiene
Shared

One person writes the play. The whole team runs it.

Two hours back.
Per person.

Friday afternoon reads like Monday morning.

2h/wk Saved
15% Efficiency
~$5K $ / yr

Claude skills · Team playbooks

Workflow skills

Reusable skills for the work people repeat every week: first drafts, follow-ups, cleanup, and summaries. Written in plain English, shared with the whole team.

  • First drafts
  • Follow-ups
  • Cleanup
  • Shared library

How it works

Straight to the point.

  1. Pick a repeat task Anything repeated more than 3 times a week
  2. Write the skill Inputs, rules, and what good looks like
  3. Run on real work Fix wording until the output is useful
  4. Share it Team reuses the same skill next week