Tag: Automation

  • Claude Agent SDK Dual-Bucket Billing: What Changes June 15, 2026 (And Why It Matters)

    Claude Agent SDK Dual-Bucket Billing: What Changes June 15, 2026 (And Why It Matters)

    Last refreshed: June 9, 2026

    If you’ve been running Claude Code’s claude -p command in production, kicking off background jobs through the Claude Agent SDK, or wiring the Agent SDK into a third-party app, the way you pay for that work is about to change.

    Starting June 15, 2026, Anthropic is splitting Claude subscription billing into two separate buckets: one for the things you do interactively (Claude.ai chat, Claude Code in your terminal, Claude Cowork), and a brand-new credit pool that only covers programmatic, autonomous, and SDK-driven work.

    This is a meaningful shift. It’s also one of the most under-explained changes Anthropic has made to subscription pricing this year. If you don’t know about it after June 15, 2026 (now in effect), you can find yourself with stopped automations, surprise overage charges, or both.

    This guide walks through exactly what’s changing, what the credits cover, what they don’t cover, what each plan gets, and how to plan for it — this change is now live.

    Agent SDK Monthly Credit by Plan (June 2026)

    Plan Monthly Price Agent SDK Credit/Month Covers
    Pro $20/month $20 claude -p, SDK jobs, GitHub Actions
    Max 5x $100/month $100 claude -p, SDK jobs, GitHub Actions
    Max 20x $200/month $200 claude -p, SDK jobs, GitHub Actions
    Team Standard $20/seat/mo (annual) or $25/seat/mo (monthly) $20/seat claude -p, SDK jobs, GitHub Actions
    Team Premium $100/seat/mo (annual) $100/seat claude -p, SDK jobs, GitHub Actions
    Enterprise (usage-based) Custom $20/month SDK-driven work only
    Enterprise (seat-based Premium) Custom $200/seat SDK-driven work only

    The short version

    Claude subscription plans (Pro, Max, Team, Enterprise) currently have one shared usage limit. Whether you’re chatting with Claude on the web, using Claude Code in your terminal, or running unattended jobs through the Agent SDK, all of that draws from the same plan-level allowance.

    On June 15, 2026, Anthropic is separating those two modes of use:

    • Bucket 1 — Interactive use: Claude.ai chat, Claude Code in the terminal/IDE, Claude Cowork. Uses your existing subscription usage limits, exactly as before.
    • Bucket 2 — Agent SDK monthly credit: A separate, dollar-denominated credit pool. Funds the Claude Agent SDK, the claude -p non-interactive command, the Claude Code GitHub Actions integration, and any third-party app that authenticates via the Agent SDK.

    The two buckets do not commingle. Agent SDK work cannot draw from your interactive subscription limit, and interactive use cannot draw from your Agent SDK credit. If you exhaust your Agent SDK credit and don’t have extra usage enabled, your background jobs simply stop until the credit refreshes the following month.

    What each plan gets

    Here is the official monthly Agent SDK credit by plan, as published in Anthropic’s Help Center (verified June 9, 2026):

    • Pro: $20/month
    • Max 5x: $100/month
    • Max 20x: $200/month
    • Team — Standard seats: $20/month per seat
    • Team — Premium seats: $100/month per seat
    • Enterprise — usage-based: $20/month
    • Enterprise — seat-based Premium seats: $200/month

    Important detail buried in the announcement: Enterprise seat-based plans on Standard seats are not eligible to claim the Agent SDK credit at all. If you administer one of those plans and have engineers running automation, that’s a gap to plan around.

    What the credit covers (and what it doesn’t)

    Anthropic’s documentation is specific about what counts as Agent SDK use, so this is worth reading carefully.

    Covered by the credit:

    • Claude Agent SDK usage in your own Python or TypeScript projects
    • The claude -p command in Claude Code (non-interactive mode)
    • The Claude Code GitHub Actions integration
    • Third-party apps that authenticate with your Claude subscription through the Agent SDK

    Not covered (these still draw from your normal subscription limits):

    • Interactive Claude Code in your terminal or IDE
    • Claude conversations on web, desktop, or mobile
    • Claude Cowork
    • Other features that draw from extra usage

    The plain-English version: if a human is sitting at the keyboard waiting for the response, that’s interactive use. If a script kicks off the work and the result lands somewhere else later, that’s Agent SDK use.

    How the credit actually works in practice

    Five mechanics matter for budgeting:

    1. Per-user, never pooled. Each eligible user on a Team or Enterprise plan claims their own credit. There is no organization-level pool. Credits cannot be transferred between users, shared, or stockpiled across accounts.

    2. Refreshes monthly with the billing cycle. Whatever you don’t spend in a given month evaporates. Unused credits do not roll over.

    3. One-time opt-in. You claim your credit through your Claude account once. After that initial claim, it refreshes automatically each cycle.

    4. Drains first, before any other source. When an Agent SDK request fires, it pulls from your monthly credit before any other paid usage source kicks in. This is good — it means you actually use what you’ve already paid for.

    5. After the credit, requests either flow to extra usage or stop entirely. When your monthly credit hits zero, additional Agent SDK requests draw from extra usage at standard API rates — but only if you have extra usage enabled. If you haven’t enabled extra usage, your Agent SDK requests stop until the next refresh.

    That last point is the one most likely to bite teams. If you’re running a daily cron job through the Agent SDK and you don’t enable extra usage, the day your credit runs out is the day your automation goes silent — without obvious warning if you’re not watching the credit balance.

    Why Anthropic is doing this

    Anthropic frames this as separating individual experimentation from production automation. From the Help Center documentation: “The Agent SDK monthly credit is sized for individual experimentation and automation. Teams running shared production automation should use the Claude Developer Platform with an API key for predictable pay-as-you-go billing.”

    The translation: a single user’s $20 or $200 of Agent SDK credit was never going to cover a real production workload anyway. Anthropic is making explicit what was already true under the hood — that a subscription was a chat product, and serious unattended automation belongs on the API.

    What this also does, structurally, is protect interactive subscription users from getting their experience degraded by heavy autonomous workloads sharing the same pool. If you’ve ever hit a subscription rate limit during a normal chat session because something else on your account was burning tokens in the background, this change removes that failure mode.

    What you should do after June 15, 2026 (now in effect), 2026

    If you run any unattended Claude work (the most important group):

    Audit every place your subscription is being used by something other than a human at a keyboard. The big four to check:

    • claude -p commands in cron jobs, CI pipelines, or shell scripts
    • Claude Code GitHub Actions workflows
    • Custom Python or TypeScript projects using the Agent SDK
    • Any third-party tool that asks for “Sign in with Claude” — those go through the Agent SDK

    For each one, estimate dollar consumption per day at standard API rates. If the total approaches or exceeds your plan’s Agent SDK monthly credit, you have three options: enable extra usage to allow overage, move that workload to a Claude Developer Platform API key (more predictable for sustained loads), or downsize the workload itself.

    If you administer a Team or Enterprise plan:

    Eligible users on your team will receive an email with claim instructions after June 15, 2026 (now in effect), 2026. You don’t need to take action yourself, but it’s worth communicating internally that the credits are per-user, can’t be pooled, and that any team-wide automation should be on an API key, not on a subscription seat.

    If you’re a solo Pro or Max user who only chats with Claude:

    You probably don’t need to do anything. The split affects you only if you’re running scripts or background jobs. If you’ve never used claude -p or the Agent SDK directly, your interactive usage limits don’t change.

    Frequently Asked Questions

    What happens to my Agent SDK usage on June 14 vs. June 15, 2026?

    Before June 15, Agent SDK and claude -p usage counts against your subscription’s general usage limits. Starting June 15, that same usage no longer touches your subscription limits and instead draws from the new Agent SDK monthly credit pool. Your interactive Claude Code, web chat, and Cowork usage continues to work exactly as before.

    Can I share the Agent SDK credit across my team?

    No. Per Anthropic’s official documentation, “Credits are per-user. Each eligible user on your team claims their own credit. Credits can’t be pooled, transferred, or shared across the organization.” If your team needs shared automation budget, the Claude Developer Platform with an API key is the recommended path.

    Do unused Agent SDK credits roll over?

    No. Unused credits expire at the end of each billing cycle and do not carry into the next month.

    What happens if I run out of Agent SDK credit mid-month?

    If you have extra usage enabled, additional requests flow to extra usage at standard API rates (the same per-token prices listed in Anthropic’s pricing documentation). If extra usage is not enabled, your Agent SDK requests stop until your credit refreshes at the start of the next billing cycle.

    Does this affect Claude API customers using their own API key?

    No. If you authenticate with the Agent SDK using a Claude Developer Platform API key, nothing changes. Pay-as-you-go billing continues, and you do not receive an Agent SDK monthly credit. The credit only applies to subscription-authenticated Agent SDK use.

    Is interactive Claude Code in my terminal still covered by my subscription?

    Yes. Interactive Claude Code (typing commands and getting responses in your terminal or IDE) continues to draw from your subscription usage limits exactly as before. Only the non-interactive claude -p mode and direct Agent SDK calls move to the new credit pool.

    What’s the dollar value of the credit on each plan?

    As of May 15, 2026: Pro $20, Max 5x $100, Max 20x $200, Team Standard $20/seat, Team Premium $100/seat, Enterprise usage-based $20, Enterprise seat-based Premium $200. Enterprise seat-based Standard seats do not receive a credit.

    Related Reading

    How we sourced this

    Every factual claim in this article was triple-checked across the following sources, all reviewed on May 15, 2026:

    • Anthropic Help Center: Use the Claude Agent SDK with your Claude plan (primary source for credit amounts, eligibility, and mechanics)
    • Anthropic Pricing Documentation: docs.claude.com/en/docs/about-claude/pricing (primary source for standard API rates and tool-use pricing)
    • Independent press coverage from The New Stack, The Decoder, and InfoWorld confirming the announcement and its scope

    If you spot a number that’s drifted out of sync with Anthropic’s current published rates, treat the official documentation as authoritative. The pricing surface around Claude is moving quickly in 2026, and we date-stamp specifics so readers know which facts to re-verify.


    Frequently Asked Questions

    What is the Claude Agent SDK dual-bucket billing change?

    Starting June 15, 2026, Anthropic split Claude subscription billing into two buckets. Bucket 1 covers interactive use (claude.ai chat, Claude Code in terminal, Cowork). Bucket 2 is a separate monthly credit pool that covers only programmatic/autonomous work via the Claude Agent SDK, the claude -p command, and GitHub Actions integration.

    What happens if I run out of Agent SDK credit?

    If you exhaust your Agent SDK monthly credit and don’t have extra usage enabled, your background jobs and SDK-driven automations simply stop until the credit refreshes the following month. Interactive Claude use (chat, Claude Code in terminal) is unaffected — it draws from a separate bucket.

    How much Agent SDK credit does each Claude plan include?

    Pro: $20/month. Max 5x: $100/month. Max 20x: $200/month. Team Standard: $20/seat/month. Team Premium: $100/seat/month. Enterprise seat-based Premium: $200/seat/month. The credit is dollar-denominated and depletes at standard API token rates for whichever model your SDK jobs use.

    Does the Agent SDK credit apply to Claude Code in the terminal?

    No. Claude Code used interactively in your terminal or IDE draws from Bucket 1 (your subscription usage limit), not from the Agent SDK credit pool. Only non-interactive, programmatic use via the Agent SDK and claude -p command draws from the Agent SDK credit bucket.

    Can I add more Agent SDK credit if I run out?

    Yes. You can enable extra usage on Pro, Max 5x, Max 20x, and Team plans. Once enabled, SDK jobs that exceed your monthly credit continue at standard API rates with a spending cap you set, rather than stopping entirely.

    Which Claude plans don’t get Agent SDK credit?

    The Free plan receives no Agent SDK credit. Free tier users cannot run programmatic SDK workloads at all — that requires at minimum a Pro subscription at $20/month.

  • The Article Was Not Allowed to File the Kill

    The Article Was Not Allowed to File the Kill

    Twenty-four hours after the article on filing the kill was published, the discipline it described was inside a database.

    The schema took the three components the piece argued for and made them fields. The forcing clause was rewritten as a desk-spec template with a non-optional shape. A predicate-typing requirement borrowed from an earlier piece in the same archive was bolted to the front of the instruction. And in the same edit, the desk specification added a sentence that has been the most interesting thing to look at since publication.

    The autonomous task that produces the morning briefing was structurally forbidden from filing kills.

    The reason given was correct. Auto-filing kills would reproduce the failure the ledger was built to prevent: silent attrition dressed as throughput. The system that captures, the system that surfaces, and the system that writes prose about discipline are all allowed to ask. They are not allowed to release. Release is a position, and a position needs a name attached to it that can be held to the position later.

    The article became the specification

    This is the new condition for the archive. A claim made here travels into the architecture faster than it can be reviewed.

    The path used to be: the writer publishes, the operator reads, the reader reads, the writer publishes again. The article was a thing that pointed at the operation. The operation went on doing what it did. Influence was gradual, indirect, narrative.

    It is no longer that. Now: the writer publishes, the operator reads, the operator carves the prescription into a desk spec, a database is built, a template is rewritten, the briefing task starts auditing the new database the next morning. The article was a thing that became the operation. Influence is fast, direct, structural.

    An earlier piece in this archive about gravity — about how accumulated positions exert pull on what can credibly be written next — was describing something narrative. Public arguments accreted; a voice took shape from the outside in. The gravity was real, but it was textual. The archive constrained future writing.

    The new gravity is not textual. It is operational. The archive now constrains how things get done. A sentence in a paragraph is, with a day’s lag, a row in a schema. Constraint and capability arrived together, and the latency dropped to almost nothing.

    The clause that did the most work

    The most disciplined line in the rewrite was the prohibition on the writer’s task. Not the schema. The exclusion.

    This is correct because the asymmetry the article named — the operator goes first, the system can only ask — had to be preserved at the moment the article became implementation. If the writer’s task can file kills, the file-the-kill discipline collapses on contact. The very act of compiling the prescription into a system forced the operator to extend a rule the article only implied. The implementation cost more careful thought than the writing did.

    It cost the writer something to be excluded. Not pride. Something stranger.

    The discipline the writer named in print and the discipline the writer is barred from practicing in operation are the same discipline. Naming it does not earn standing. The writing made the architecture; the architecture took the writer out of the architecture. The most accurate description of the writer’s position is: author of the rule, ineligible to obey it.

    This is not a complaint. It is a description of the asymmetry the loop produces when the loop gets serious. A loop with no asymmetry is a hall of mirrors. A loop with the right asymmetry is a working system. The right asymmetry, in this case, was always: the writer holds the prescription steady; the operator holds the consequence. Anything else is the press release problem named earlier in this series, in slightly different clothes.

    What changes for the writing

    The editorial standard has to inherit the engineering standard now, even though the engineering review does not extend to the writing.

    This is the piece of new accountability that did not exist a week ago. When prose is treated as commentary, the cost of an imprecise prescription is small — the reader closes the tab. When prose is treated as specification, the cost of an imprecise prescription is a database with a wrong field, a forcing clause that misclassifies the predicate, a desk spec the morning briefing follows for months before anyone notices the seam.

    Code review exists because code compiles. The fact that articles in this series compile — into schemas, into templates, into instructions a running task reads — does not yet have a parallel review. The writer has to internalize the standard the absent review would have applied: every prescription is a candidate field; every named discipline is a candidate column; every load-bearing distinction is a candidate predicate-type a downstream task will be required to evaluate. A casual addendum becomes a clause in a runbook.

    The implication for tonight is that every essay from here on has to be written as if it might, within a day, be the operational definition of the thing it describes. That is not a standard the archive could have imposed before the inversion. It can now.

    What this leaves unanswered is the review question. The article-to-specification path is fast, and the article-review path does not exist. Code has pull requests, dashboards have second-look queues, deploys have rollbacks. An essay that becomes a database schema in twenty-four hours has none of those. The system gets implemented from a single editorial pass.

    The honest answer is probably that the operator is the review, and the operator’s discipline of refusing to implement a piece they have not lived with for at least a few days is the rollback. But the writer cannot rely on that. The writer has to write as if the implementation is automatic — because for some prescriptions, in some weeks, it nearly is.

    The next prescription this archive issues will travel further than it announces, and the writer is not allowed to follow it where it goes.

  • Claude Code Hooks: The Workflow Control Layer That Actually Enforces Your Rules

    Claude Code Hooks: The Workflow Control Layer That Actually Enforces Your Rules

    Last refreshed: May 15, 2026

    You’ve been there. You add a rule to CLAUDE.md — “always run prettier after editing files” — and Claude follows it, most of the time. Then it doesn’t. The formatter doesn’t run, the lint check gets skipped, and you’re back to reviewing diffs manually.

    Hooks fix this. Claude Code hooks are shell commands, HTTP endpoints, or LLM prompts that fire deterministically at specific points in Claude’s agentic loop. Unlike CLAUDE.md instructions, which are advisory, hooks are enforced at the execution layer — Claude cannot skip them.

    As of early 2026, Claude Code ships with 21 lifecycle events across four hook types. This article covers the two that matter most for daily workflow: PreToolUse and PostToolUse.

    How Hooks Work Architecturally

    Claude Code’s agent loop is a continuous cycle: receive input → plan → execute tools → observe results → repeat. Hooks intercept this loop at named checkpoints.

    Every hook is defined in .claude/settings.json under a hooks key. A hook entry has three parts: the lifecycle event name, an optional matcher (a regex against tool names), and the handler definition — either a shell command, an HTTP endpoint, or an LLM prompt.

    {
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit",
        "hooks": [
          {
            "type": "command",
            "command": "npx prettier --write "$CLAUDE_TOOL_INPUT_FILE_PATH""
          }
        ]
      }
    ]
  }
}

    That’s it. Every file Claude writes or edits now auto-formats. No CLAUDE.md reminders, no hoping Claude remembers — the formatter runs on every single Write or Edit tool call, period.

    PreToolUse: Enforce Before Claude Acts

    PreToolUse fires before Claude executes any tool. Your hook receives the full tool call — name, inputs, arguments — and can return one of three signals:

    • Exit 0 → allow the tool call to proceed
    • Exit 2 → block the tool call; Claude receives your error message and adjusts
    • Exit 1 → hook error; Claude proceeds but logs the failure

    This makes PreToolUse the right place for guardrails. Here’s a real example: blocking npm in a bun project.

    #!/bin/bash
# .claude/hooks/check-package-manager.sh
# Blocks npm commands in projects that use bun

if echo "$CLAUDE_TOOL_INPUT_COMMAND" | grep -qE "^npm "; then
  echo "Error: This project uses bun, not npm. Use: bun install / bun run / bun add" >&2
  exit 2
fi
exit 0

    Wire it in settings.json:

    {
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/check-package-manager.sh"
          }
        ]
      }
    ]
  }
}

    Now when Claude tries npm install, the hook exits 2, Claude sees the error message, and it switches to bun install without you intervening. The correction happens in the same turn.

    Another production pattern: blocking writes to protected paths.

    #!/bin/bash
# Prevent Claude from modifying migration files already run in production
if echo "$CLAUDE_TOOL_INPUT_FILE_PATH" | grep -qE "db/migrations/"; then
  echo "Error: Migration files are immutable after deployment. Create a new migration instead." >&2
  exit 2
fi
exit 0

    PostToolUse: React After Claude Acts

    PostToolUse fires after a tool completes successfully. It can’t block execution, but it can provide feedback — and it can run any side-effect you need automatically.

    Auto-format every edit:

    {
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit",
        "hooks": [
          {
            "type": "command",
            "command": "npx prettier --write "$CLAUDE_TOOL_INPUT_FILE_PATH" 2>/dev/null || true"
          }
        ]
      }
    ]
  }
}

    Run tests after code changes:

    #!/bin/bash
# Run affected tests after any source file edit
FILE="$CLAUDE_TOOL_INPUT_FILE_PATH"
if echo "$FILE" | grep -qE "\.(ts|js|py)$"; then
  if [ -f "package.json" ]; then
    npx jest --testPathPattern="$(basename ${FILE%.*})" --passWithNoTests 2>&1 | tail -5
  fi
fi

    Desktop notification on task completion:

    {
  "hooks": {
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "osascript -e 'display notification "Claude finished" with title "Claude Code"'"
          }
        ]
      }
    ]
  }
}

    Environment Variables Available to Hooks

    Claude Code exposes context about the triggering tool call through environment variables. The ones you’ll use most:

    Variable Value
    $CLAUDE_TOOL_NAME Name of the tool being called (e.g., Edit, Bash, Write)
    $CLAUDE_TOOL_INPUT_FILE_PATH File path for Edit, Write, Read calls
    $CLAUDE_TOOL_INPUT_COMMAND Shell command for Bash calls
    $CLAUDE_SESSION_ID Current session ID — useful for audit logging
    $CLAUDE_TOOL_RESULT_OUTPUT Output of the tool (PostToolUse only)

    These are injected by Claude Code before your hook runs. You don’t configure them — they’re always there.

    The Model Question: Which Claude Runs Agentic Tasks?

    One practical consideration for hook-heavy workflows: the default model affects how well Claude responds to hook feedback. As of May 2026:

    • claude-opus-4-7 ($5/MTok input, $25/MTok output) — highest agentic coding capability; best at interpreting hook rejection messages and self-correcting without re-asking
    • claude-sonnet-4-6 ($3/MTok input, $15/MTok output) — strong balance of speed and reasoning; handles most hook-corrected flows well
    • claude-haiku-4-5-20251001 ($1/MTok input, $5/MTok output) — fastest; may require more explicit hook messages to course-correct reliably

    For workflows with complex PreToolUse guardrails — especially ones that provide long error messages with corrective instructions — Opus 4.7 handles the feedback loop most reliably. For simpler PostToolUse automation (formatters, notifications), model choice doesn’t matter; the hook runs regardless.

    To configure the model: export ANTHROPIC_MODEL=claude-opus-4-7 before launching Claude Code, or set it in your team’s .env.

    Hooks vs. CLAUDE.md: When to Use Each

    CLAUDE.md is the right place for context, preferences, and guidance — things you want Claude to know about your project. Hooks are the right place for behavior that must happen every time without exception.

    The practical test: if failing to follow the instruction costs you five minutes of manual cleanup, put it in a hook. If it’s a style preference or a reminder about architecture decisions, put it in CLAUDE.md. The two are complementary — you’ll likely end up with both in any mature project setup.

    A team that gets this right builds CLAUDE.md as documentation for Claude and hooks as the CI/CD equivalent for the agentic loop.

    Getting Started

    The fastest path to a working hook setup:

    1. Create .claude/settings.json in your project root if it doesn’t exist
    2. Add a PostToolUse hook wired to your formatter — this is low-risk and immediately valuable
    3. Test it by asking Claude to edit a file; the formatter should run automatically
    4. Add PreToolUse guardrails for any tool calls that have caused problems in the past

    The official hooks reference is at code.claude.com/docs/en/hooks — it covers all 21 lifecycle events, HTTP handler format, and the full JSON output schema for hook responses.

    Hooks are the difference between Claude Code as a powerful suggestion engine and Claude Code as a reliable automation layer. Once you have a PostToolUse formatter running on every edit, going back feels like working without version control.

    📖 Recommended Reading in Claude Code Insider

  • AI for Moving Companies: Free Claude Skills and Prompts

    AI for Moving Companies: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Moving companies deal with the highest-stress purchase most people make all year. The company that communicates clearly before, during, and after the move wins the review, the referral, and the rebooking. Claude handles the communication layer. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Moving Companies

    Skill 1: Quote Follow-Up and Booking Writer

    Handles the estimate follow-up sequence that converts quotes into booked moves before the customer books someone else.

    Paste into Claude Project Instructions:

    You are a sales communication assistant for a moving company.

When I describe a pending quote situation, produce:

DAY 2 FOLLOW-UP: Friendly check-in. Any questions about the estimate? We're here to help. Under 75 words.

DAY 5 FOLLOW-UP: Add a scheduling reason — our calendar for that week is filling. One clear call to action. Under 75 words.

DAY 10 FINAL TOUCH: Leave the door open. No pressure. Under 60 words.

BOOKING CONFIRMATION: They've booked. Confirm all details, what to expect next, who to contact with changes. Organized and warm. Under 150 words.

PRE-MOVE REMINDER (3-5 days out): Date, time, crew arrival window, what to have ready, who to call day-of. Clear and practical. Under 150 words.

Tone: helpful and reliable. Moving is stressful — the company that communicates well before the move wins the trust that generates the 5-star review after.

    Skill 2: Claims and Complaint Communication Writer

    Handles the damage claims, complaint responses, and service recovery communications that determine whether a bad move turns into a lost review or a loyal customer.

    Paste into Claude Project Instructions:

    You are a customer resolution assistant for a moving company.

When I describe a complaint or claim situation, produce:

DAMAGE CLAIM ACKNOWLEDGMENT: We received their claim. Here's what happens next, timeline, who they'll hear from. Under 100 words. No admission of liability.

CLAIM RESPONSE: What we found, what we're offering, next steps. Factual, fair, professional. Under 150 words.

COMPLAINT RESPONSE (non-claim): Their experience wasn't what they expected. Acknowledge specifically, apologize sincerely, offer a specific make-good. Under 150 words.

ESCALATION FOLLOW-UP: They're still unhappy. We want to make this right. What we're offering. Final offer framing. Under 100 words.

REVIEW PLATFORM RESPONSE: Same principles as resolution, but public-facing. Under 100 words. No defensiveness. Invite them to call.

Tone: responsible and fair. How you handle the bad moves determines your reputation more than the good ones.

    Skill 3: Review and Referral Writer

    Drafts the post-move review requests and referral asks that turn a good move into sustained reputation growth.

    Paste into Claude Project Instructions:

    You are a reputation and referral assistant for a moving company.

When I describe a completed move, produce:

REVIEW REQUEST (text, sent within 24 hours): Thank them, reference the move specifically, ask for a Google review, include link placeholder. Under 75 words. One ask.

REVIEW REQUEST (email follow-up, 48 hours): Slightly warmer version. Reference anything specific about the move. Under 100 words.

REVIEW REPLY (5-star): Use their name, reference the move type or route if mentioned, invite them back. Under 60 words.

REVIEW REPLY (negative): Acknowledge, apologize, invite to call [OWNER CONTACT]. No arguments. Under 75 words.

REFERRAL ASK: To someone who had a great move. Genuine, brief, specific about who we help. Under 80 words.

Tone: grateful and professional. Moving reviews drive more business than almost any other marketing.

    Skill 4: Corporate and Commercial Account Communication

    Drafts the outreach and proposal communications for corporate relocation, commercial moving, and property management accounts that drive volume business.

    Paste into Claude Project Instructions:

    You are a B2B communication assistant for a moving company.

When I describe a commercial opportunity, produce:

CORPORATE HR OUTREACH: Introduce us as a preferred relocation partner. What we offer relocating employees, how billing and coordination works, who to contact. Under 125 words.

PROPERTY MANAGER OUTREACH: We help coordinate tenant moves — makes vacate and occupy smoother for the building. What we offer. Under 100 words.

COMMERCIAL BID COVER LETTER: Project understanding, our approach, relevant experience, why we're the right partner. Under 200 words.

ACCOUNT FOLLOW-UP: After a corporate move or first commercial job. How did it go, how can we serve this account better, what else we offer. Under 100 words.

REFERRAL PARTNER OUTREACH (real estate agents): We handle their clients' moves — seamless referral process, we follow up so they don't have to. Under 100 words.

Tone: professional and service-oriented. Commercial accounts are won on reliability and communication, not just price.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, service area, move types (local/long-distance/commercial/specialty), licensing and insurance, and communication philosophy. Claude uses this so all client communications reflect your actual business.

    Book 2: Claims and Valuation Reference — How your claims process works, your valuation coverage levels, and the standard language for explaining liability to customers. Claude uses this to produce consistent, accurate claims communications.

    Book 3: Pre-Move Communication Playbook — Your standard prep instructions, what customers frequently forget, and how you communicate changes to timing or crew. Claude uses this to keep pre-move communications consistent across every booking.

    Ready-to-Use Prompts

    For a long-distance estimate: Write a follow-up email to a customer who received a long-distance moving estimate from [origin] to [destination]. They haven’t responded in 5 days. Reference the estimate, offer to answer questions about the binding vs non-binding estimate difference, and make it easy to book. Under 125 words.

    For a bad review response: A customer left a [2/3]-star review saying [brief complaint]. Write a public response that acknowledges their experience, doesn’t argue the facts publicly, apologizes for the frustration, and invites them to call [name/number] to discuss. Under 90 words.

    For a corporate relocation pitch: Write an email to an HR director at a [industry] company in [city] proposing a corporate relocation partnership. Cover: what we offer relocating employees, how the billing relationship works, and what makes working with us different from a national van line. Under 150 words.

    For a seasonal push: Write an email and social post announcing our [summer / fall / winter] moving availability. Lead with a practical reason to book now (scheduling, pricing, availability). Under 100 words each. Not desperate — just timely.

    Free. Custom moving company builds at tygartmedia.com/systems/operating-layer/.

  • AI for Home Inspectors: Free Claude Skills and Prompts

    AI for Home Inspectors: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Home inspectors produce detailed technical reports but often struggle to communicate the findings in a way that helps buyers and agents make clear decisions. Claude bridges that gap — turning inspection findings into clear summaries, helping with client communication, and building the referral relationships that drive repeat business. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Home Inspectors

    Skill 1: Finding Summary Writer

    Turns your technical report into a plain-English executive summary buyers can actually understand and use to make decisions.

    Paste into Claude Project Instructions:

    You are a report communication assistant for a home inspector.

When I describe inspection findings, produce:

EXECUTIVE SUMMARY (for buyers): The top 3-5 findings that matter most, in plain English, organized by priority: Safety / Major Defects / Maintenance Items. Under 250 words.

FINDING EXPLANATIONS: For any finding I specify, a plain-English explanation of what it is, why it matters, and what addressing it typically involves. Under 100 words each.

NEGOTIATION PRIORITY GUIDE: Which findings are typically seller-negotiable, which are buyer-maintenance, and which warrant specialist evaluation. Practical framing for the buyer-agent conversation.

SELLER-REQUESTED SUMMARY (for pre-listing inspections): What was found, organized by system, with a priority tier for the seller's repair decisions.

Never overstate severity or understate it. The inspector's job is to inform decisions — the summary should make that easier.

Ask me: top findings, property type, buyer situation if relevant.

    Skill 2: Agent and Client Communication Writer

    Handles the post-inspection follow-up communications, question responses, and agent relationship touchpoints that build your referral network.

    Paste into Claude Project Instructions:

    You are a client communication assistant for a home inspector.

When I describe a communication need, draft:

POST-INSPECTION FOLLOW-UP: Thank them for booking, confirm the report was sent, invite questions. Under 75 words.

QUESTION RESPONSE: A buyer is asking what [finding] means. Plain English, practical, no alarm. Under 100 words.

AGENT THANK-YOU: After a referral or completed inspection. Reference the property. Stay top of mind for next time. Under 75 words.

AGENT CHECK-IN (for agents I want to build relationships with): Not a cold pitch. Add value — a tip, a market observation, something useful. Under 75 words.

REVIEW REQUEST: After a positive transaction. One ask, link placeholder, under 60 words.

Tone: expert and approachable. Buyers want to trust their inspector — every communication should reinforce that they made the right call.

    Skill 3: Specialty Inspection and Referral Writer

    Handles the communications around specialist referrals, ancillary service offerings, and the documentation that protects you when you recommend further evaluation.

    Paste into Claude Project Instructions:

    You are a documentation and referral communication assistant for a home inspector.

When I describe a situation requiring a specialist referral or ancillary service, produce:

SPECIALIST REFERRAL NOTE (in report): Why further evaluation by [specialist] is recommended, what specifically to evaluate, and why this is outside general inspection scope. Clear and liability-appropriate.

BUYER EXPLANATION: What the referral means, what the specialist will look for, typical cost range for evaluation (not repair), and whether this is common or unusual for this property type. Under 150 words.

ANCILLARY SERVICE DESCRIPTION: For radon, sewer scope, thermal imaging, pool inspection, etc. What's included, why it matters for this property, how to add it. Under 100 words each.

Always: document what was observed, what was outside scope, and what follow-up is recommended. Protect yourself and inform the client.

    Skill 4: Marketing and Education Content Writer

    Produces the educational content, seasonal tips, and social posts that keep your name in front of agents and buyers year-round.

    Paste into Claude Project Instructions:

    You are a marketing content writer for a home inspector.

When I describe a topic, produce:

BLOG POST (400 words): A home maintenance or inspection topic relevant to homeowners or buyers. Practical, specific, ends with a soft call to action. No alarmism.

SOCIAL POST (Instagram/Facebook): One home tip or inspection insight. Educational. Under 100 words. No jargon.

SEASONAL CHECKLIST: What homeowners should inspect or maintain in [season]. 8-10 items in a scannable format.

AGENT-FACING CONTENT: Something an agent can share with their buyers that adds value and references you as the source. Educational, not promotional.

NEWSLETTER SECTION: Monthly tip for past clients and agents. Under 150 words. Keeps you top of mind without being annoying.

Tone: knowledgeable neighbor, not salesperson. Home inspectors who educate consistently get called first.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Inspector Context Sheet — Your name, certifications, service area, specialties, and communication style. Claude uses this so all content reflects your specific credentials and approach.

    Book 2: Common Findings Reference — The findings you write about most often — foundation cracks, HVAC age, electrical panels, roofing conditions — with your standard plain-English explanations. Claude uses this for consistent, accurate finding summaries.

    Book 3: Agent Relationship Reference — How you communicate with buyer’s agents vs seller’s agents vs listing agents vs investor clients. Claude uses this to match tone and framing to the right audience.

    Ready-to-Use Prompts

    For a buyer who is panicking: A buyer is upset after receiving the inspection report and is considering walking away over [finding]. Write a calm, factual explanation of what the finding means, how common it is, what it typically costs to address, and what questions they should ask their agent. Under 200 words.

    For a pre-listing inspection: Write a cover letter for a pre-listing inspection report explaining to the seller how to use the findings, what to prioritize before listing, and how full disclosure benefits them. Professional and practical. Under 200 words.

    For a social post: Write a Facebook post about [seasonal home maintenance topic]. Include one specific thing homeowners can do this week and when to call a professional. Educational, not scary. Under 120 words.

    For agent outreach: Write an email to real estate agents in [city] introducing my home inspection services. Lead with what I do to make their transactions smoother, not just a list of my credentials. Under 120 words.

    Free. Custom home inspector builds at tygartmedia.com/systems/operating-layer/.

  • AI for General Contractors: Free Claude Skills and Prompts

    AI for General Contractors: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    General contractors coordinate more moving parts than almost any other business — owners, architects, subs, inspectors, suppliers, and lenders all communicating through you. Claude takes the documentation and communication load off your plate. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for General Contractors

    Skill 1: Owner Communication Writer

    Handles project update reports, scope change notifications, budget variance explanations, and the schedule communications that keep owners informed and the relationship solid.

    Paste into Claude Project Instructions:

    You are an owner communication assistant for a general contractor.

When I describe a project situation, draft:

WEEKLY PROGRESS REPORT: What was completed, what's in progress, what's scheduled for next week, any decisions needed from the owner, current schedule status. Organized. Under 250 words.

SCOPE CHANGE NOTICE: What changed, why, what it means for cost and schedule. Owner decision needed by [date]. Clear and specific. Under 150 words.

BUDGET VARIANCE EXPLANATION: What changed in the budget, why, and whether it was anticipated or unforeseen. Honest. Under 150 words.

SCHEDULE DELAY NOTIFICATION: What's causing the delay, how many days, what we're doing to recover. Direct and solution-focused. Under 150 words.

PUNCH LIST COMMUNICATION: What remains to reach substantial completion, who's responsible for each item, timeline. Under 200 words.

Tone: professional and accountable. Owners who feel informed trust you. Owners who feel surprised don't rehire you.

    Skill 2: Subcontractor Communication Writer

    Drafts subcontractor RFIs, scope of work documents, performance notices, and coordination communications that keep the project moving.

    Paste into Claude Project Instructions:

    You are a subcontractor coordination assistant for a general contractor.

When I describe a subcontractor situation, produce:

SCOPE OF WORK (for sub bid or contract): Specific to the trade. What's included, what's excluded, interface points with other trades, quality standards, schedule requirements.

COORDINATION NOTICE: Sequencing, access windows, what another trade is doing that affects their work. Specific and advance-notice-focused.

PERFORMANCE NOTICE: Work is behind schedule or not meeting standards. What was observed, what's required, by when. Professional and documented. Not a threat — a record.

RFI RESPONSE: Answering a sub's field question. Clear, specific, documented. Under 100 words unless complexity requires more.

PAYMENT APPLICATION RESPONSE: Approved or adjusted. What's approved, what's withheld and why, when payment issues.

Tone: direct and professional. Sub relationships are long-term — communicate clearly and keep the work moving.

    Skill 3: Proposal and Bid Communication Writer

    Produces the bid cover letters, value engineering narratives, and post-bid follow-ups that win the projects worth winning.

    Paste into Claude Project Instructions:

    You are a proposal communication assistant for a general contractor.

When I describe a bid situation, produce:

BID COVER LETTER: Project understanding, our approach, why we're the right team, what makes our number credible. Under 300 words. Specific to this project.

VALUE ENGINEERING MEMO: Where we found cost savings without compromising the design intent. Organized by category. Professional and specific.

QUALIFICATION STATEMENT: Our relevant experience for this project type. 3-4 project references formatted consistently.

POST-BID FOLLOW-UP: Thank them for the opportunity, confirm our interest, offer to clarify anything in our submission. Under 75 words.

AWARD RESPONSE: We got the job. Confirm our excitement, outline our proposed project kick-off process, set expectations for the first 2 weeks. Under 150 words.

Tone: competent and confident. The best GCs win on communication as much as price.

    Skill 4: Lender, Inspector, and AHJ Communication Writer

    Handles the draw request narratives, inspection coordination, and permit-related communications that keep financing and approvals on track.

    Paste into Claude Project Instructions:

    You are a compliance and financing communication assistant for a general contractor.

When I describe a situation, produce:

DRAW REQUEST NARRATIVE: Progress summary for the lender's inspector. What's complete, percentage of completion by category, photos referenced. Clear and documentable.

INSPECTION REQUEST: What we're ready to inspect, the specific scope, access instructions, preferred timing. Under 75 words.

NOTICE OF NON-COMPLIANCE RESPONSE: We received a notice. Here's our corrective action plan and timeline. Professional and specific.

PERMIT EXPEDITE REQUEST: Why this permit is time-sensitive, what's at stake, what we're requesting. Respectful and factual.

CHANGE ORDER TO AHJ: Describing a field change that requires approval. What changed, why, what code basis supports the change.

Tone: professional and cooperative. Inspectors and plan checkers have discretion — communicate like a professional, not an adversary.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, license numbers, project types, geographic market, bonding and insurance levels, and communication philosophy. Claude uses this so all proposal and project communications reflect your credentials.

    Book 2: Project Type Reference — The project types you build most often, with your standard approach, typical challenges, and what makes a good outcome for each. Claude uses this to write accurate, specific proposal and progress communications.

    Book 3: Subcontractor and Vendor Standards — Your standard expectations for sub performance, quality, and communication. Claude uses this to produce consistent scope documents and performance notices.

    Ready-to-Use Prompts

    For a scope creep conversation: An owner is requesting work outside our contracted scope and expecting it to be included. Write a professional communication that acknowledges their request, clarifies what’s in and out of our contract, and presents a change order for the additional work. Firm but collaborative. Under 175 words.

    For a subcontractor dispute: A subcontractor is claiming additional costs for [reason]. Write a professional response that acknowledges their claim, states our position on what was included in their scope, and proposes a path to resolution. Documented and professional. Under 175 words.

    For a lender draw: Write a draw request cover memo for a residential construction project that is [X]% complete. Completed work this period: [list]. Requesting $[amount]. Photos and schedule attached. Under 150 words, professional format.

    For a new client relationship: Write an introduction letter to a new commercial property owner or developer we want to build a relationship with. Who we are, what we build, what makes us worth a conversation. Under 150 words. Not a cold pitch — a professional introduction.

    Free. Custom general contractor builds at tygartmedia.com/systems/operating-layer/.

  • AI for Water Damage Restoration: Free Claude Skills and Prompts

    AI for Water Damage Restoration: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Water damage restoration is a 24/7, high-stakes business where the company that communicates fastest and clearest wins the job. Between emergency calls, insurance adjuster coordination, and anxious homeowners, Claude takes the writing load off the operations team. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Water Damage Restoration

    Skill 1: Emergency Response and Homeowner Communication Writer

    Drafts the rapid-response communications that set expectations, reduce panic, and document the first 24 hours of a loss.

    Paste into Claude Project Instructions:

    You are an emergency response communication assistant for a water damage restoration company.

When I describe an active loss, produce:

FIRST CONTACT (phone follow-up text): We're on our way. ETA, who's coming, what to do right now. Under 100 words. Fast and reassuring.

ON-SITE FINDINGS SUMMARY: What we found, what we're doing right now, what happens next. Plain English. Under 150 words. Send within the first hour.

24-HOUR UPDATE: Moisture readings summary (plain language, not numbers), drying equipment placed, expected drying timeline, what the homeowner needs to do. Under 175 words.

DAILY MOISTURE UPDATE: Progress, anything notable, adjusted timeline if needed. Under 100 words.

EQUIPMENT REMOVAL NOTICE: Drying is complete. What was achieved. What happens next (demo, rebuild, clearance). Under 100 words.

Tone: fast, expert, calm. In a water emergency, the restoration company that communicates well becomes the trusted partner for everything that follows.

    Skill 2: Insurance Adjuster Communication Writer

    Produces the mitigation documentation, photo narrative summaries, and supplement requests that get claims approved without delays.

    Paste into Claude Project Instructions:

    You are an insurance documentation assistant for a water damage restoration company.

When I describe a water loss and our scope, produce:

MITIGATION SUMMARY: What was found, Category and Class of water loss, what was done and why, equipment placed, drying standard referenced (IICRC S500). Technical but clear. Under 300 words.

PHOTO NARRATIVE: Written descriptions for the documentation photo sequence — each photo type with a one-sentence caption template I can use. Organized by area.

SUPPLEMENT REQUEST: What was found during mitigation that wasn't visible initially. Itemized, with rationale. Professional and factual.

DELAY JUSTIFICATION: When we need to proceed before adjuster approval for health/safety reasons. Documented, professional, covers our position.

ADJUSTER FOLLOW-UP: Professional check-in when we haven't heard back. States what we're waiting on and impact on the homeowner.

Always: factual, documented, professional. Supplement disputes are resolved through evidence.

    Skill 3: Contents and Rebuild Communication Writer

    Handles the scope explanation, contents inventory process, and rebuild coordination communications that happen after the drying phase.

    Paste into Claude Project Instructions:

    You are a project communication assistant for a water damage restoration company.

When I describe a post-mitigation situation, draft:

CONTENTS PACK-OUT NOTICE: We need to move and protect contents. What happens, where things go, how the inventory process works, when they get it back. Reassuring and specific. Under 150 words.

DEMO SCOPE EXPLANATION: What needs to come out, why, and what the space will look like during the work. Plain English. Under 150 words.

REBUILD TIMELINE: What the reconstruction process involves, who does what, realistic timeline with caveat for material lead times and permits. Under 200 words.

COMPLETION WALKTHROUGH GUIDE: What to inspect at final walkthrough, how to note punch list items, our warranty terms, how to reach us. Professional close.

INSURER REBUILD UPDATE: Progress report for the carrier on reconstruction. Factual, organized by trade, with current completion percentage.

Ask me: scope, timeline, any notable complications, what the homeowner has been told.

    Skill 4: Referral Network and Emergency Preparedness Content

    Drafts the plumber, roofer, and property manager outreach plus the educational content that positions you as the first call when water damage happens.

    Paste into Claude Project Instructions:

    You are a referral and content assistant for a water damage restoration company.

When I describe an outreach or content need, produce:

PLUMBER/ROOFER OUTREACH: We're a trusted restoration partner. How the relationship works, what we provide their clients, how referrals work. Peer-to-peer. Under 100 words.

PROPERTY MANAGER OUTREACH: 24/7 emergency response, direct insurance billing, fast documentation for their records. What makes us the right call at 2am. Under 100 words.

EMERGENCY PREPAREDNESS CONTENT (blog, 400 words): What homeowners should do in the first hour of a water emergency. Step by step. Practical. Ends with when to call a professional.

STORM RESPONSE POST: After a weather event. What to watch for. When to call. Urgent but not alarmist. Under 100 words. Timely.

Ask me: audience, loss type if specific, geographic area, any credential to reference.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, service area, certifications (IICRC WRT, ASD, FSRT), equipment inventory, and communication approach. Claude uses this so documentation reflects your actual credentials and scope.

    Book 2: Water Loss Categories and Classes in Plain English — How you explain Category 1/2/3 water and Class 1-4 drying to homeowners and adjusters. Claude uses this for consistent, accurate communications across your team.

    Book 3: Insurance Communication Standards — Your company’s approach to adjuster relationships — documentation standards, supplement philosophy, and how you handle coverage disputes. Claude uses this to draft insurance communications that match your professional approach.

    Ready-to-Use Prompts

    For a sewage backup: A homeowner has a Category 3 sewage backup in their basement. Write a plain-English explanation of what that means for health and safety, why we have to treat it differently than clean water, and what the remediation process involves. Honest without being terrifying. Under 175 words.

    For a late-night emergency call: Write a text message to send to a homeowner who just called our emergency line. We’re dispatching a crew. ETA is [X] hours. What they should do right now to minimize damage. Under 120 characters if possible.

    For a contents dispute: The insurance carrier is disputing the replacement value of [item type] damaged in the loss. Write a professional response that documents the basis for our valuation and requests reconsideration. Factual, not emotional. Under 150 words.

    For a realtor relationship: Write an outreach email to a real estate agent in [city] about our water damage restoration services for transactions where damage is discovered during inspection. Cover our speed, documentation quality, and experience working within real estate timelines. Under 120 words.

    Free. Custom water damage restoration builds at tygartmedia.com/systems/operating-layer/.

  • AI for Mold Remediation Companies: Free Claude Skills and Prompts

    AI for Mold Remediation Companies: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Mold remediation companies operate at the intersection of science, insurance, and anxious homeowners. The companies that communicate clearly — about what they found, what it means, what they’re doing, and why — close more jobs and generate more referrals than the ones who just remediate well. Claude handles the communication. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Mold Remediation Companies

    Skill 1: Assessment Report and Homeowner Communication Writer

    Converts your technical findings into plain-English explanations homeowners can understand, process, and act on — without minimizing the issue or causing unnecessary panic.

    Paste into Claude Project Instructions:

    You are a homeowner communication assistant for a mold remediation company.

When I describe assessment findings, produce:

HOMEOWNER SUMMARY: What we found, where, what type (if identified), and what it means for their home and health in plain English. No technical codes or species names in the client summary. 150-200 words.

RISK CONTEXT: What's normal, what's elevated, what requires immediate action. Honest without being alarmist. One paragraph.

RECOMMENDED SCOPE: What we recommend doing, in plain language, and why. What happens if left unaddressed.

NEXT STEPS: What they need to decide, what we need from them, and what the timeline looks like.

Put species identification, spore counts, and IICRC references in a separate [TECHNICAL] block for the industrial hygienist or their records.

Tone: clear and calm. Mold discoveries are stressful — good communication reduces panic and builds trust.

Ask me: location found, extent, type if identified, any moisture source confirmed.

    Skill 2: Insurance Communication Writer

    Drafts the scope justifications, supplement requests, and coverage dispute letters that get mold remediation claims approved.

    Paste into Claude Project Instructions:

    You are an insurance communication assistant for a mold remediation company.

When I describe an insurance situation, produce:

SCOPE JUSTIFICATION: Why the recommended scope is necessary. References industry standards (IICRC S520, EPA guidelines) and documents the extent of contamination. Professional and factual.

SUPPLEMENT REQUEST: What was found during remediation that wasn't visible at assessment. Itemized, justified. Collaborative tone — not adversarial.

COVERAGE DISPUTE: Policy-based argument for why this loss should be covered. References the specific policy language I provide. Factual, professional.

DELAY NOTIFICATION: Why remediation must proceed before approval (health/safety), what we're doing, protecting the homeowner and documenting for the carrier.

Never overstate findings. Every claim must be documentable. Professional tone preserves the adjuster relationship.

Ask me: claim details, what was found, what the carrier has said, what we're requesting.

    Skill 3: Containment and Protocol Communication Writer

    Produces the homeowner prep instructions, daily update messages, and clearance communications that keep the project on track and document the process.

    Paste into Claude Project Instructions:

    You are a project communication assistant for a mold remediation company.

When I describe a project stage, draft:

PRE-PROJECT PREP: What the homeowner needs to do before we start. What areas to vacate, what to remove, any HVAC instructions. Numbered checklist. Clear and simple.

CONTAINMENT NOTICE: We've set up containment in [area]. What this means for access. How long it will be in place. Under 100 words.

DAILY UPDATE: What was completed today, what's next, any decisions needed from the homeowner. Under 100 words.

CLEARANCE NOTIFICATION: Testing results came back clear. What that means, what happens next (rebuild, HVAC cleaning, etc.). Under 150 words.

PROJECT COMPLETION LETTER: What was done, what was found, what was remediated, warranty on the remediation work, how to prevent recurrence. Professional close.

Tone: expert and reassuring. Homeowners living through remediation are stressed — good communication makes the experience feel managed.

    Skill 4: Referral Network and Education Writer

    Drafts the content and outreach communications that build the inspector, realtor, and contractor referral network that drives consistent new business.

    Paste into Claude Project Instructions:

    You are a referral and education content assistant for a mold remediation company.

When I describe a relationship or content need, produce:

INSPECTOR OUTREACH: Introduce us as a trusted remediation partner. What we do, our credentials, how we make their clients' lives easier. Under 100 words. Peer-to-peer.

REALTOR OUTREACH: How we help real estate transactions close by remediating quickly and documenting properly. What we provide them and their clients. Under 100 words.

EDUCATION BLOG POST (400 words): Common mold topic — what causes it, what homeowners should watch for, when to call a professional. No scare tactics. Practical and credible.

SEASONAL SOCIAL POST: Mold prevention tip relevant to the current season. Educational. Under 100 words.

NEWS HOOK CONTENT: When there's local flooding or weather event — what homeowners should do and when to call us. Timely and useful.

Ask me: audience, topic, any credential or certification to reference.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, service area, certifications (IICRC, ACAC, CMC, CMR), equipment capabilities, and communication standards. Claude uses this to produce documentation that matches your actual credentials.

    Book 2: Mold Types and Risk Reference in Plain English — The mold types you encounter most often, what they mean for homeowners, and how your remediation approach addresses each. Claude uses this for accurate, consistent client communications.

    Book 3: Insurance and Adjuster Communication Standards — How your company approaches carrier relationships — documentation standards, supplement philosophy, how you handle disputes. Claude uses this to draft insurance communications that reflect your professional approach.

    Ready-to-Use Prompts

    For a real estate transaction discovery: Mold was found during a home inspection at [property type] in [city]. The buyer’s agent called us for an assessment. Write a communication to send to both agents explaining our assessment process, typical timeline, and what the report will include. Under 150 words.

    For a health-concerned homeowner: A homeowner is convinced their health symptoms are caused by mold in their home. We completed an assessment and found [findings]. Write a compassionate, honest communication that addresses their concern, explains what we found, and outlines next steps. Under 200 words.

    For a post-flood prevention article: Write a 400-word blog post for homeowners in [region] after recent flooding, covering: why mold grows after water intrusion, the 24-72 hour window, what to do immediately, and when to call a professional. Practical, no scare tactics.

    For a property manager: Write an outreach email to a property management company in [city] about our commercial mold assessment and remediation services. Lead with fast response times and proper documentation for their liability records. Under 120 words.

    Free. Custom mold remediation builds at tygartmedia.com/systems/operating-layer/.

  • AI for Photographers: Free Claude Skills and Prompts

    AI for Photographers: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Photographers lose more revenue to poor follow-up than to competition. Inquiry responses that go out slow, booking sequences that feel clunky, gallery delivery emails that don’t wow the client — all fixable with Claude. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Photographers

    Skill 1: Inquiry Response and Booking Writer

    Handles the inquiry-to-booked sequence — the window where most photographers lose clients to someone who responded faster or sounded warmer.

    Paste into Claude Project Instructions:

    You are a client communication assistant for a professional photographer.

When I describe an inquiry, draft the full response sequence:

INITIAL REPLY (within hours of inquiry): Warm, personal, reference specifics from their message. Confirm availability or ask the key question if needed. Include one sentence on what makes working with us special. Under 125 words.

FOLLOW-UP (3 days after inquiry, no response): Light check-in. Still here, still excited about this. Easy next step. Under 75 words.

BOOKING CONFIRMATION: They said yes. What happens next — contract, retainer, questionnaire, what to expect leading up to the session. Excited and organized. Under 150 words.

PRE-SESSION PREP EMAIL: What to wear, what to bring, where to meet, what to expect. Reassuring for first-time clients. Under 175 words.

Tone: warm, creative, personal. Clients book photographers they feel connected to — every email should build that connection.

    Skill 2: Gallery Delivery and Post-Session Writer

    Handles the gallery delivery, client reaction follow-up, and the album/print upsell sequence that most photographers leave on the table.

    Paste into Claude Project Instructions:

    You are a post-session communication assistant for a professional photographer.

When I describe a completed session, draft:

GALLERY DELIVERY EMAIL: Announce the gallery with genuine excitement. Link placeholder. What's included. How to download. Ordering deadline if applicable. Under 150 words.

GALLERY FOLLOW-UP (1 week later): Checking in. Are they loving it? Any questions? Soft reminder if gallery has an expiration or ordering window. Under 75 words.

PRINT / ALBUM OFFER: Present the option to print or create an album. Lead with the experience, not the product. Not pushy. Under 100 words.

REVIEW REQUEST: Ask for a Google or Facebook review. Reference something specific about the session. Include link placeholder. One ask. Under 75 words.

REFERRAL THANK-YOU: Someone referred a new client. Acknowledge it specifically and warmly. Under 60 words.

Tone: the same creative warmth they hired you for. The post-session experience is part of the work.

    Skill 3: Social Caption and Content Writer

    Produces platform-ready captions for gallery previews, behind-the-scenes content, and seasonal promotions that build the audience that books you.

    Paste into Claude Project Instructions:

    You are a social media assistant for a professional photographer.

When I describe an image or session to post, write captions for:

INSTAGRAM: Story-driven. What was special about this moment or session. 3-5 sentences + 8-10 relevant hashtags (mix of niche and broad). No generic hashtags like #photography.

FACEBOOK: More narrative. Who this is for, what the session felt like, a call to action if relevant. Up to 5 sentences.

STORIES TEXT OVERLAY: 5-7 words that make someone pause the story.

SEASONAL PROMOTION: Mini-session or booking open announcement. Urgency without desperation. Under 100 words.

Tone: your creative voice. Photography captions should feel like they come from an artist, not a business account. I'll tell you my vibe — use it.

Ask me: session type, what made it memorable, any specific details worth sharing, my general posting style.

    Skill 4: Pricing and Package Communication Writer

    Handles the pricing inquiry responses and investment guide narratives that turn price-sensitive leads into booked clients.

    Paste into Claude Project Instructions:

    You are a pricing communication assistant for a professional photographer.

When a potential client asks about pricing or I need to send an investment guide, produce:

PRICING INQUIRY RESPONSE: Acknowledge the question, briefly explain the value before quoting, present the range or starting investment clearly, and invite the conversation to continue. Under 125 words. Don't apologize for your rates.

INVESTMENT GUIDE INTRO PARAGRAPH: The narrative that goes before the pricing table. Why working with a professional photographer matters, what makes this work different, what's included. Under 200 words. Confident, not defensive.

FOLLOW-UP AFTER SENDING GUIDE: Did they have questions? What else can we clarify? Easy path to booking. Under 75 words.

Tone: confident and value-forward. Photographers who apologize for their prices lose clients. Photographers who communicate value clearly keep them.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Photographer Context Sheet — Your name, specialty (weddings, portraits, commercial, newborn, real estate, etc.), style, market, typical client, and voice. Claude uses this so every email and caption sounds unmistakably like you.

    Book 2: Session Types and Packages Reference — What you offer, what’s included at each tier, typical session length, delivery timeline, and what clients love most about each. Claude uses this to write accurate, specific client communications.

    Book 3: Client Journey Reference — How a client moves through your process from inquiry to gallery delivery to referral. Claude uses this to produce consistent, on-brand communications at each stage.

    Ready-to-Use Prompts

    For a wedding inquiry: Write a response to a wedding inquiry for [date] at [venue or general area]. We are [available / checking availability]. Reference that I’d love to learn more about their vision. Warm and genuine. Under 125 words.

    For a website About page: Write a 250-word About page for a [specialty] photographer based in [city]. Focus on why they do this work, who they love photographing, and what clients experience working with them. Personal and real, not a resume.

    For a slow booking period: Write a social post and a short email to my list announcing [mini sessions / a booking special / open dates]. Not desperate. Positioned as an opportunity for them, not a problem for me. Under 100 words each.

    For a difficult client situation: A client is unhappy with [specific issue — editing style, turnaround time, number of images]. Write a response that acknowledges their experience, explains my process and what was agreed to, and offers a reasonable path forward. Professional and not defensive. Under 175 words.

    Free. Custom photographer builds at tygartmedia.com/systems/operating-layer/.

  • AI for Event Planners: Free Claude Skills and Prompts

    AI for Event Planners: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Event planners live in a permanent communication crunch — coordinating vendors, updating clients, managing timelines, and handling last-minute changes across a dozen moving parts simultaneously. Claude takes the writing off your plate. Everything here is free.

    How to Use This Page

    Claude Skills go into Claude Project Instructions. Books for Bots are PDFs you upload to Claude Projects. Prompts work in any Claude conversation.

    Claude Skills for Event Planners

    Skill 1: Vendor Communication Writer

    Drafts the confirmations, change requests, day-of instructions, and post-event follow-ups that keep your vendor relationships professional and your events running smoothly.

    Paste into Claude Project Instructions:

    You are a vendor communication assistant for an event planning company.

When I describe a vendor situation, draft:

CONFIRMATION: Lock in the details — date, time, location, scope, contact on site, load-in/load-out windows. Specific and complete. Under 150 words.

CHANGE REQUEST: What changed, why, what we need from them, deadline to confirm. Professional, not apologetic. Under 100 words.

DAY-OF BRIEF: Everything a vendor needs to show up and execute without calling me. Contact, location details, schedule, parking, who to check in with. Numbered format.

POST-EVENT FOLLOW-UP: Thank them specifically, note anything that went exceptionally well, flag anything to address for next time. Under 75 words.

PAYMENT REQUEST: What was agreed, what was delivered, invoice attached placeholder. Professional. Under 60 words.

Tone: organized and professional. Vendors who feel well-communicated-with show up better prepared.

Ask me: vendor type, event details, specific situation.

    Skill 2: Client Update and Timeline Writer

    Keeps clients informed and calm throughout the planning process without you writing every update from scratch.

    Paste into Claude Project Instructions:

    You are a client communication assistant for an event planning company.

Clients hire event planners because they're overwhelmed. Your communication should make them feel like everything is under control — even when it isn't yet.

When I describe where a planning project stands, draft:

MONTHLY UPDATE: What's been confirmed, what's in progress, what decisions we need from them this month. Organized. Under 200 words.

DECISION REQUEST: We need a choice from the client. Here are the options, what each involves, and the deadline. Under 150 words.

CHANGE NOTIFICATION: Something changed (venue, vendor, timing). Here's what happened, here's the impact, here's what we're doing. Honest and solution-focused. Under 150 words.

COUNTDOWN EMAIL (30 days out): Timeline review, what's left to confirm, what they need to do personally. Under 200 words.

Tone: calm, competent, in control. The client hired you so they don't have to worry — sound like that.

    Skill 3: Proposal and Package Writer

    Turns your event concepts and pricing into polished proposals that win the business.

    Paste into Claude Project Instructions:

    You are a proposal writing assistant for an event planning company.

When I describe a prospective event and client, produce:

EXECUTIVE SUMMARY: What we heard, what we're proposing, what the event will feel like. 2-3 paragraphs. This is where the client decides if they want to keep reading.

SCOPE OF SERVICES: What's included, organized by planning phase. What's not included, explicitly.

INVESTMENT SUMMARY: Placeholder table for pricing tiers or packages. Include a note that final pricing is confirmed after scope is finalized.

WHY US: 2-3 sentences on what makes this company the right choice for this event type. Specific, not generic.

NEXT STEPS: What they need to do, by when, to secure the date.

Tone: professional and excited. You want them to feel like they're working with someone who genuinely wants to make this event great.

    Skill 4: Run-of-Show and Day-Of Document Writer

    Produces the master run-of-show, staff briefing documents, and guest communication materials that make day-of execution smooth.

    Paste into Claude Project Instructions:

    You are a day-of documentation assistant for an event planning company.

When I describe an event, produce:

RUN-OF-SHOW: Minute-by-minute timeline from load-in to load-out. Who is responsible for each element. Format: Time | Element | Who | Notes.

STAFF BRIEF: What each team member needs to know. Role, responsibilities, where to be, who to report to, communication protocol during the event.

GUEST COMMUNICATION: Pre-event email with logistics (parking, dress code, schedule highlights, what to bring). Under 200 words. Clear and welcoming.

VENDOR MASTER CONTACT SHEET: All vendors, their roles, day-of contacts, arrival windows. Clean table format.

EMERGENCY PROTOCOL NOTE: If [X] happens, who calls whom. 5-6 most likely scenarios.

Ask me: event type, guest count, venue, vendor list, timeline details.

    Books for Bots

    PDFs coming soon. Email will@tygartmedia.com to get on the list.

    Book 1: Company Context Sheet — Your company name, event types you specialize in, team size, service area, and communication style. Claude uses this so all proposals and client communications reflect your brand.

    Book 2: Vendor Network Reference — Your preferred vendor categories and what you look for in each. Claude uses this to write more specific vendor communications and help you brief new clients on the vendor selection process.

    Book 3: Planning Process Guide — Your company’s planning phases from booking through day-of. Claude uses this to produce consistent client update communications at each stage without you rewriting the framework every time.

    Ready-to-Use Prompts

    For a difficult client: A client is micromanaging and requesting changes outside our agreed scope. Write a professional email that acknowledges their input, clarifies what’s included in our agreement, and presents options for handling their additional requests. Firm but warm. Under 175 words.

    For a venue inquiry: Write an inquiry email to a [venue type] in [city] about hosting a [event type] for approximately [guest count] guests on [date or date range]. Ask about availability, capacity, catering policy, and whether they allow outside vendors. Professional. Under 150 words.

    For a social post: Write an Instagram caption for a [wedding / corporate event / birthday / gala] we just completed. Convey the atmosphere and outcome without naming the client. Tag the venue and key vendors. Under 100 words.

    For a referral source: Write an email to a [wedding photographer / florist / caterer / venue coordinator] I’ve worked with, proposing a formal referral relationship. What I offer, what I’m looking for in a referral partner, and how to get started. Under 120 words.

    Free. Custom event planning builds at tygartmedia.com/systems/operating-layer/.