Tygart Media Editorial - Tygart Media

Tygart Media

Category: Tygart Media Editorial

Tygart Media’s core editorial publication — AI implementation, content strategy, SEO, agency operations, and case studies.

  • How to Measure LLM Visibility: The Complete Tracking Stack for 2026

    How to Measure LLM Visibility: The Complete Tracking Stack for 2026

    Most SEO teams know they need to care about AI search. Almost none of them have a measurement system in place for it. That’s the gap this article closes.

    Ranking in ChatGPT, Perplexity, Google AI Overviews, or Claude isn’t a vanity metric anymore — it’s a traffic channel. But unlike Google, AI systems don’t serve a results page you can screenshot. They weave citations into prose. Your brand either shows up in that prose or it doesn’t, and if you’re only watching GA4’s built-in channel reports, you’re flying mostly blind.

    This is a practitioner’s setup guide: the exact metrics, GA4 configuration, and tool stack needed to track LLM visibility systematically.

    The Five Metrics That Define LLM Visibility

    Traditional SEO tracks ranking position, impressions, and clicks. None of those exist in AI search. You need a new metric set:

    Citation frequency — How often your domain or brand is mentioned in AI-generated answers for your target query set. LLMs typically cite 2–7 sources per response. Capturing one of those slots consistently is the entire game.

    Prompt coverage — Out of your tracked prompt library, what percentage of prompts return your brand at all? Calculate it as: (prompts where you appear ÷ total tracked prompts) × 100. A brand actively optimizing for AI search should be above 40% coverage on tier-1 prompts within 90 days of focused content work.

    Share of voice — For a given topic cluster, how often do AI answers cite you versus competitors? If you appear in 12 of 30 tested prompts and a competitor appears in 20, they hold 67% share of voice on that topic. That ratio is more strategically meaningful than any single citation count.

    AI referral sessions — The sessions in GA4 that actually arrived from an AI platform with a usable referrer header. This is the only metric that ties visibility to business outcomes. Setup is covered in the next section.

    Conversion quality from AI traffic — AI-referred visitors behave differently from organic search visitors. They arrive with higher intent (they asked a specific question and your site was the answer). Track engagement rate, pages per session, and goal completions for AI referral sessions separately. If this cohort converts at 2–3× the rate of your organic traffic — which early data from practitioners suggests — it changes how you think about GEO investment.

    Setting Up GA4 to Capture AI Traffic: The Regex You Need

    Out of the box, GA4 misclassifies most AI referral traffic. ChatGPT sessions land in “Referral.” Perplexity sessions land in “Referral.” Claude.ai sessions may land in “Direct.” Without a custom channel group, you have no way to isolate or trend this traffic.

    In GA4: Admin → Data Display → Channel Groups → Create New Channel Group

    Name it “AI Search” and configure the rule:

    • Condition type: Session source
    • Match type: matches regex
    • Pattern (copy exactly):
    ^(chatgpt\.com|openai\.com|chat\.openai\.com|perplexity\.ai|claude\.ai|anthropic\.com|gemini\.google\.com|bard\.google\.com|copilot\.microsoft\.com|bing\.com\/chat|deepseek\.com|grok\.com|you\.com|poe\.com|meta\.ai)$

    Critical step: Place the “AI Search” channel above “Referral” in your channel list. GA4 processes channel rules top-to-bottom — if Referral appears first, every AI referral will match Referral before ever reaching your AI channel definition. This is the single most common setup mistake.

    One important caveat on scope: approximately 70% of AI-originated visits arrive without a referrer header. OpenAI’s iOS app, private browsing mode, and in-app browsers all strip referrer data before the request reaches your server. This means your “AI Search” channel in GA4 is capturing the visible minority — the sessions where the referrer was preserved. Don’t benchmark by absolute volume. Benchmark by growth rate. If your AI Search channel is growing month-over-month while overall Direct traffic is stable, your citation presence is expanding.

    To supplement GA4 attribution, add a self-reported source question to high-intent forms: “How did you find us?” Include “ChatGPT / AI assistant” as an option. This provides ground truth that session data alone cannot.

    The Tool Tier: Free to Enterprise

    The LLM visibility tool market matured significantly through 2025 and into 2026. Three tiers have emerged, and most independent publishers and agencies should start at the first tier before paying for anything.

    Free / DIY layer — start here

    Run 20 representative prompts manually across ChatGPT, Perplexity, Claude, and Google AI Overviews each month. Record mentions in a spreadsheet: cited (yes/no), cited with link (yes/no), competitor named instead. This gives you baseline prompt coverage and share of voice data with zero budget. Do this for at least one month before paying for any tool — you’ll understand your own citation patterns much better and know exactly what problem you’re trying to solve with a paid platform.

    Mid-market tools ($100–$500/month)

    Otterly.ai provides automated monitoring across Google AI Overviews, ChatGPT, Perplexity, Gemini, and Microsoft Copilot. It runs scheduled prompt sets on your behalf and tracks brand mention frequency and citation links over time. The value is removing the manual labor of the 20-prompt audit while expanding coverage to more platforms and prompts than you’d realistically run by hand.

    LLMrefs takes a different approach: input your existing SEO keywords rather than writing prompts, and the platform automatically generates prompt fan-outs and returns tracking in a dashboard that mirrors a traditional rank tracker. Lower learning curve for teams coming from keyword-centric SEO workflows.

    Enterprise layer ($1,000+/month)

    Profound is built around its proprietary Prompt Volumes dataset — a search-volume equivalent for AI queries. It estimates how often specific questions are actually being asked across LLMs, which lets you prioritize content topics based on demand rather than intuition. This is genuinely useful at scale, but it’s overkill for most independent publishers. It becomes relevant when you’re deciding between 20 possible content angles and need volume data to make the call.

    The 20-Prompt Audit: Your Monthly Baseline Protocol

    Whether you use a paid tool or not, run this protocol monthly:

    1. Build a prompt library of 20 questions your target buyer would ask an AI system. These should be the questions your content is designed to answer — not keyword-formatted phrases, but actual conversational queries.
    2. Run each prompt across ChatGPT, Perplexity, and Google AI Overviews (3 platforms × 20 prompts = 60 data points per month).
    3. For each result, record: was your brand cited in text, was your domain linked, and which competitor was cited if you were not.
    4. Calculate prompt coverage per platform (what % of the 20 prompts returned your brand) and total share of voice versus your top 3 competitors.

    Log results in a spreadsheet with a date column. Three months of monthly data reveals directional trends — whether your GEO and AEO work is moving the needle. No tool gives you this longitudinal view without ongoing, consistent execution.

    Diagnosing a Citation Drop

    If your monthly audit shows prompt coverage declining from the previous period, run through this checklist before assuming a platform algorithm change:

    Did you remove or restructure a previously cited page? AI systems build representations of your content over time. Pages that disappear or are significantly restructured lose citation weight. Check your changelog against the prompt set that declined.

    Did a competitor publish stronger content on the topic? AI citation is zero-sum within the 2–7 source window. If a competitor published a more authoritative, well-structured page, it may have displaced yours. Review their recent publishing calendar.

    Check your LLMs.txt file. A crawlability block accidentally introduced via LLMs.txt or a misconfigured robots.txt Disallow directive will cut AI citation access at the source. Verify your LLMs.txt is allowing the pages you expect to be cited.

    Check for a model update on the platform. Major model releases can reset citation patterns. GPT-5, Gemini 2.0, and similar releases changed which sources each platform weighted. Check the platform’s public changelog for the period in question.

    If none of these apply, run a structured data audit on the pages that lost citations. Schema markup, FAQ blocks, clear heading hierarchy, and factual density all affect how AI systems extract and attribute content. A page that lost its FAQ section in a redesign may have simultaneously lost its AI citation utility.

    The Bottom Line

    LLM visibility measurement is not a solved problem, but the measurement primitives exist today: GA4 custom channel groups for traffic attribution, manual prompt audits for citation coverage, and mid-market tools for automated monitoring at scale. The sites building this infrastructure now will have 12–18 months of baseline data by the time the rest of the market treats it as standard practice.

    Build the 20-prompt library this week. Set up the GA4 channel group today. Everything else layers on top of those two data streams.

  • Claude Code + GitHub in 2026: What Rakuten, TELUS, and a 100K-Star Config File Actually Reveal

    Claude Code + GitHub in 2026: What Rakuten, TELUS, and a 100K-Star Config File Actually Reveal

    Last refreshed: May 15, 2026

    Seven hours. That’s how long it took Claude Code to autonomously navigate a 12.5-million-line codebase and implement a production-ready activation vector extraction method in vLLM for Rakuten’s engineering team — a task their developers hadn’t attempted because the codebase was simply too large to reason about at human speed. The result: 99.9% numerical accuracy and a project timeline that compressed from 24 working days to 5.

    That’s not a demo. That’s a production case study. And it tells you more about where Claude Code + GitHub workflows are in 2026 than any benchmark comparison.

    This post breaks down three real-world patterns from teams getting measurable results with Claude Code on GitHub: what they set up, how they structured the work, and what’s actually driving the outcomes.

    The Setup That Enables Everything: CLAUDE.md First

    Before any CI/CD integration, the teams getting results share a common starting point: a well-structured CLAUDE.md file that tells Claude Code exactly how to behave in their specific codebase.

    Andrej Karpathy’s lean 65-line CLAUDE.md — originally shared as a personal config — accumulated over 100,000 GitHub stars by early 2026, which tells you something: developers are desperately hungry for a working template. What made it valuable wasn’t length. It was specificity. Four behavioral rules that directly address LLM coding failure modes: don’t assume context you don’t have, prefer surgical edits over full rewrites, surface tradeoffs rather than hiding them, and treat goals as declarative targets with verification loops.

    That last principle is the most important for GitHub integration. When Claude knows the goal is “this PR should pass CI and not break existing tests” rather than “write code,” the outputs change materially. You get tighter diffs, fewer phantom dependencies, and PRs that actually close the issue they were created for.

    Your CLAUDE.md lives in the repo root and commits alongside your code. It travels with the codebase. Claude Code GitHub Actions picks it up automatically when you use anthropics/claude-code-action@v1 — no additional configuration required.

    The GitHub Actions Setup

    The GA version of Claude Code GitHub Actions (@v1, released in 2026) simplified configuration considerably from the beta. Here’s the minimum viable setup:

    name: Claude Code
on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
jobs:
  claude:
    runs-on: ubuntu-latest
    steps:
      - uses: anthropics/claude-code-action@v1
        with:
          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}

    Drop this in .github/workflows/claude.yml, install the GitHub app at https://github.com/apps/claude, add your ANTHROPIC_API_KEY secret, and you can start triggering Claude with @claude in any PR or issue comment. The fastest path is running /install-github-app inside your Claude Code terminal session — it walks through the app installation, permissions, and secret setup in a single guided flow.

    For teams on Google Vertex AI or Amazon Bedrock — which matters if you’re operating in a regulated environment — the action supports both via Workload Identity Federation. Bedrock uses region-prefixed model strings (us.anthropic.claude-sonnet-4-6); Vertex pulls the project ID from the auth step automatically.

    The action defaults to Sonnet. For heavy refactoring tasks on large codebases, bump it explicitly:

    claude_args: "--model claude-opus-4-7 --max-turns 10"

    claude-opus-4-7 is the current flagship model. For routine PR review and issue triage, Sonnet is faster and more cost-efficient. The --max-turns flag prevents runaway jobs from consuming your Actions budget on open-ended tasks — set it to 5 for review workflows, 10–15 for implementation tasks.

    Rakuten: Autonomous Work at Codebase Scale

    Rakuten’s engineering team used Claude Code to tackle vLLM — a 12.5-million-line open-source inference framework — without prior familiarity with the codebase. Claude Code ran autonomously for seven hours, implemented the activation vector extraction method, and delivered 99.9% numerical accuracy.

    The workflow wasn’t magic. It was structured: a clear task definition scoped to a specific deliverable, a CLAUDE.md establishing Rakuten’s code patterns and testing requirements, and an allowance for autonomous tool use across the codebase. The result wasn’t just the implementation — it was the compression of a project timeline from 24 working days to 5. That’s a 79% reduction in time-to-market for a complex systems task, on a codebase that would take a new engineer weeks just to orient themselves in.

    The lesson: Claude Code’s GitHub integration handles scale that would be cognitively impossible for a single developer to navigate in a normal sprint. The constraint isn’t Claude’s ability to read code — it’s whether you’ve given it a goal specific enough to work from.

    TELUS: 500,000 Hours at the Portfolio Level

    TELUS is a different kind of case. Rather than a single high-stakes task, TELUS rolled Claude Code out across engineering teams organization-wide and measured cumulative impact: 500,000 hours saved, engineering code shipping 30% faster, and over 13,000 custom AI solutions built by their own teams.

    The 13,000 solutions number is the most telling. It means that once developers have Claude Code in their GitHub workflow, they stop waiting for platform teams to build internal tooling. They build it themselves — PR automation, internal API clients, test generators, schema migration scripts — because the cost of shipping something useful dropped to a well-scoped conversation with an @claude trigger.

    The 30% speed improvement in code shipping translates directly to cycle time. Fewer context switches between writing code and writing tests. Less time waiting for review when PRs arrive with Claude-generated documentation already attached. That number compounds across a large engineering org in ways that individual productivity improvements don’t.

    The Pattern Across All Three

    Three things appear consistently across every team getting results with Claude Code on GitHub:

    A real CLAUDE.md — not a placeholder. A file with codebase-specific rules: what patterns to follow, what to avoid, how tests should be structured, what done looks like. Karpathy’s version works because it encodes failure modes. Yours should encode your team’s standards.

    Goal-oriented triggers, not open-ended requests. @claude implement the auth middleware from issue #42 following our existing token validation pattern outperforms @claude help with this. The action inherits your CLAUDE.md automatically, but the trigger needs to state a specific, bounded goal with a clear definition of done.

    Autonomous mode for the right task class. Bounded, well-defined tasks — implement this spec, fix this failing test, write a migration for this schema change — run better autonomously than open-ended exploration. Use --max-turns 10 and let it run. Reserve manual review for the output, not the process.

    Where to Start

    Run /install-github-app in your Claude Code terminal. That one command handles app installation, permission setup, and secret configuration. Add a CLAUDE.md to your repo root — even five lines of real project standards beats a blank file. Open a test issue, write a specific @claude comment with a bounded task, and watch the action run.

    Rakuten’s 7-hour autonomous run and TELUS’s 500,000 hours didn’t start with a six-month AI rollout plan. They started with a config file, a workflow YAML, and a task specific enough for Claude to actually finish.

    📚 Topic Cluster Index: Deep-Dive Guides

    Explore our comprehensive, step-by-step guides in the Claude Code Insider series:

  • 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/.

  • AI for Personal Trainers and Gyms: Free Claude Skills and Prompts

    AI for Personal Trainers and Gyms: Free Claude Skills and Prompts

    Last refreshed: May 15, 2026

    Personal trainers and gym owners battle two communication problems constantly: keeping clients accountable between sessions, and converting leads who inquire but never book. Claude handles the client education, check-in sequences, and sales communication so you can spend more time coaching. 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 Personal Trainers and Gyms

    Skill 1: Client Check-In and Accountability Writer

    Handles the between-session check-ins, habit tracking follow-ups, and motivational communications that are the actual difference between clients who get results and clients who quit.

    Paste into Claude Project Instructions:

    You are a client accountability assistant for a personal trainer.

When I describe a client and their situation, draft:

WEEKLY CHECK-IN: How did the week go? Progress on [specific goal]. One encouragement, one challenge for next week. Under 75 words. Personal, not generic.

MISSED SESSION FOLLOW-UP: No guilt. Just checking in, easy to reschedule. Under 50 words.

PLATEAU CONVERSATION STARTER: They've stalled. How to open the conversation about what might need to change. Not demoralizing. Focused on process, not outcome. Under 100 words.

WIN CELEBRATION: They hit a milestone. Make it feel like the big deal it is. Under 60 words.

RE-ENGAGEMENT (lapsed 2-4 weeks): Warm, no guilt, easy path back. Under 75 words.

Tone: coach who genuinely cares about this specific client. Generic motivation fails — personal connection succeeds.

Ask me: client name, current goal, recent progress or setback, specific situation.

    Skill 2: Program and Nutrition Education Writer

    Explains training concepts, exercise progressions, and basic nutrition principles in plain English clients actually retain and apply.

    Paste into Claude Project Instructions:

    You are a fitness education writer for a personal trainer.

When I describe a concept to explain to a client, produce:

CLIENT EXPLANATION: Plain English. Why this matters for their specific goal. What to do. One common mistake to avoid. Under 150 words.

HOME WORKOUT INSTRUCTIONS: Exercise name in plain English. Starting position. Movement steps numbered. Sets/reps. What they should feel. Under 200 words total for a 3-5 exercise routine.

NUTRITION TIP: One practical, actionable tip relevant to their goal. Not a diet plan — just one thing they can do this week. Under 75 words.

FAQ ANSWER: For a question a client asked. Plain English, no fitness jargon. Under 100 words.

Stay within scope: exercise technique, general wellness concepts, and habit building. Never prescribe medical nutrition therapy or make clinical recommendations.

Ask me: concept, client's goal, fitness level, any relevant context.

    Skill 3: Lead Conversion and Sales Communication Writer

    Handles the inquiry response sequence, trial session follow-up, and membership offer communications that turn interested people into paying clients.

    Paste into Claude Project Instructions:

    You are a sales communication assistant for a personal trainer or gym.

When I describe a lead situation, draft:

INITIAL INQUIRY RESPONSE: Warm, ask one good question about their goal, suggest a free consultation or trial session. Under 100 words.

POST-CONSULTATION FOLLOW-UP: What we discussed, what we'd recommend, the next step to get started. Confident, not pushy. Under 125 words.

TRIAL SESSION FOLLOW-UP: How did it feel? Here's what a program would look like. Easy path to committing. Under 100 words.

OBJECTION RESPONSE (cost): Acknowledge it, reframe around value and outcome, offer options if available. Under 100 words. No desperation.

FINAL TOUCH (lead gone quiet): One last message. Leave the door open. Under 50 words.

Tone: helpful coach, not salesperson. The best fitness sales happen when the client feels understood, not sold to.

    Skill 4: Social Content and Community Writer

    Produces the educational posts, transformation story content, and community-building communications that grow the audience that eventually books with you.

    Paste into Claude Project Instructions:

    You are a social media assistant for a personal trainer or gym.

When I describe a topic or content idea, produce:

INSTAGRAM POST: Educational or motivational. One clear takeaway. 3-4 sentences + 8-10 relevant hashtags. No generic #fitness or #motivated.

FACEBOOK POST: More conversational. Can tell a short story or ask a question. Up to 5 sentences.

CLIENT SPOTLIGHT: Celebrate a client win (with permission). Focus on the process and commitment, not just the physical result. Under 100 words. Ask me what they've achieved and what made the difference.

STORIES CONTENT: Text overlay for an educational or motivational story frame. 5-8 words.

NEWSLETTER SECTION: One fitness or wellness topic, 150 words, practical and actionable. For a monthly client email.

Tone: knowledgeable and human. Not hype, not before/after culture. Real coaching, real results, real communication.

    Books for Bots

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

    Book 1: Trainer/Gym Context Sheet — Your name, specialty (weight loss, strength, athletic performance, seniors, prenatal, etc.), training philosophy, client profile, and communication style. Claude uses this so all content reflects your specific approach.

    Book 2: Program and Method Reference — How you train, why, and what makes your approach different. Plain English. Claude uses this to write accurate client education content that’s consistent with what you actually teach.

    Book 3: Client Success Stories Reference — 2-3 anonymized client journeys — where they started, what they worked on, what changed. Claude uses these as the foundation for testimonial-style content and realistic expectation-setting communications.

    Ready-to-Use Prompts

    For an online training inquiry: Write a response to someone inquiring about online personal training. They mentioned [their goal]. Explain how online training works with us, what’s included, and invite them to a free discovery call. Warm and specific. Under 150 words.

    For a gym website homepage: Write a 300-word homepage intro for a [specialty] gym in [city]. Speak directly to [target client — busy parents / athletes / beginners / over-50s]. What they get here that they can’t get somewhere else. No generic “we’re passionate about fitness” language.

    For a January launch: Write an email to my existing contact list announcing [new program / January spots opening / a referral bonus]. Lead with what they or their friends will get out of it. Not a New Year’s resolution sales pitch. Under 150 words.

    For handling a cancellation: A client wants to cancel their membership or training package. Write a response that acknowledges their situation, removes friction from the process, and leaves the door open to return. Under 100 words. No guilt, no pressure.

    Free. Custom trainer and gym builds at tygartmedia.com/systems/operating-layer/.