Skills you can call from Cowork

Searches across email threads tied to a project, person, or subject. Returns a synthesized digest with who said what, when, and what was decided. Useful before drafting a response or stepping back into a conversation you've been away from.

• Catch up on what's been said about a project before a client call.
• Find the email where the architect agreed to the scope change.
• Summarize a thread you got CC'd into late.

Which inbox(es) to search, default time window, signatures to ignore.

Takes a rough description of how a process works (or an existing messy doc) and turns it into a clean SOP that matches your company's template. Flags anywhere the description is incomplete so you can fill it in.

• Document a closeout process the team has been doing verbally.
• Reformat a loose Word doc into a real SOP.
• Capture a new procedure after a process change.

Your SOP template structure, where finished SOPs are stored, who approves them.

Pulls from manufacturer sites, specialty suppliers, and big-box trade desks. Returns options with price, lead time, dimensions, and link, formatted so you can pass them to a selections coordinator or client without reformatting.

• Find three freestanding tub options at a target budget.
• Identify a fixture from a partial product name or photo.
• Get spec data on a specific model before ordering.

Your preferred suppliers, standard markup, delivery lead-time tolerance.

Takes a supplier invoice or selections export, produces labels formatted for your label printer plus a receiving checklist the project coordinator uses on site. Built for the workflow where boxes arrive faster than they can be sorted.

• Print labels for next week's incoming tile and plumbing deliveries.
• Generate a receiving checklist tied to a specific PO.
• Tag boxes by room when material lands in bulk.

Your label printer format (Avery template number, label size), receiving checklist fields, job-site naming conventions.

Reads your draft spec against the bid, the plans, and your internal standards. Flags inconsistencies, missing allowances, vague language, and tone issues. Reduces the back-and-forth caused by sending out a spec with gaps.

• Final pass on a spec doc before sending to client.
• Catch allowance mismatches between spec and bid.
• Surface anywhere the spec contradicts the plan set.

Your standard exclusions list, allowance baselines, standard markup pattern.

Reads multiple bids on the same scope, normalizes the format, returns a side-by-side: price, included scope, excluded scope, schedule, terms. Designed to handle bids that arrive in wildly different formats (PDF, Excel, email body).

• Compare three framing bids on a new project.
• Diff a v1 and v2 bid from the same trade.
• Spot which bidder excluded something the others included.

Your standard exclusions list, allowance practices, preferred terms language.

Reads both PDFs sheet by sheet, extracts text changes (callouts, dimensions, schedules), and uses vision to detect visible drawing changes. Returns a structured per-sheet report with side-by-side image crops as proof. Not vector-precise; flags changes for human verification.

• Architect just issued a revised set, find what changed.
• Verify whether the budget-impacting items moved.
• Catch silent drawing changes the architect didn't call out.

Produces PDF-ready, mobile-friendly checklists with Yes/No items, organized by phase or discipline. Pulls from the project's approved trade proposals, plans, and specs to make the checklist project-specific when a project is named.

• Pre-drywall walkthrough checklist tied to the actual project.
• Framing quality checklist matched to the spec.
• Final walkthrough list for client handoff.

Reads architect plans, bid instructions, and owner-supplied specifications. Outputs the scope-of-work email you send to a trade partner so they can bid the project. Includes inclusions, exclusions, schedule expectations, and your standard insurance/safety language.

• Send out scopes to three framers when a bid package opens.
• Draft an HVAC scope from the plan set and spec.
• Standardize scope language across trades on one project.

Your standard insurance and safety language, inclusion/exclusion defaults.

The keystone skill once it's tuned to your business. Searches across project folder (Dropbox/OneDrive/Google Drive), Outlook or Gmail, and your task tracker (Asana / Linear / Buildertrend). Assembles a chain of logic with sources cited. Built per buyer because folder conventions, project naming, and task structure vary.

• Answer a client challenge about what was originally committed.
• Pull every architect comment about a specific scope item.
• Reconstruct the timeline of how a decision evolved.

Your folder conventions, project naming patterns, task tracker structure, primary email account(s).

Reads state.md, applies the change you describe, shows you a diff before writing. Only authorized users can invoke it. Per-buyer config defines which sections it can edit and what your state schema looks like.

• Weekly state.md refresh by the state keeper.
• Mid-week mark a project stage change without opening the file.
• Update the team roster after a hire or departure.

Your state.md schema, which sections are editable, who's authorized to invoke.

Codifies your colors, type stack, voice rules, letterhead, logo placement. Any document Claude generates (proposals, change orders, client letters) comes out in your brand. Requires your design system as input.

• Generate a client proposal that's already on-brand.
• Produce a change order with company letterhead.
• Draft a thank-you note matching your voice and visual identity.

Your full design system (colors, fonts, logo, letterhead template, voice rules).