Tag: AI workflow

  • Restoration CRM Prompt Library — Claude Skill

    Restoration CRM Prompt Library — Claude Skill

    $19

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this library and do it yourself. The full article is already live. Paste a prompt into claude.ai, fill the brackets, edit the draft, send it. Buy Now is the packaged Claude Skill so the library lives in the project instead of a browser tab.

    The live article (do not treat this page as a replacement): AI-Assisted Email Drafting for Restoration Companies: A Claude Prompt Library.

    Who it is for: anyone at the company who writes emails. Owner, office manager, whoever runs the CRM touch calendar. No technical background. A free Claude account at claude.ai is enough. No API key. No code.

    The workflow

    1. Go to claude.ai. Create a free account if you need one.
    2. Open a new conversation.
    3. Paste a prompt. Fill the bracketed fields with real information.
    4. Claude drafts the email.
    5. Review it. Edit anything that does not sound like you. Copy it into your email platform.

    That is the entire workflow. Specific beats generic. “Write a hiring email for a restoration company” is weak. “Write a hiring email for a 12-person water and fire restoration company in Tacoma, WA that’s been in business for eight years and is known for fast response times and honest communication with insurance adjusters” is usable.

    Strategy lives in Your CRM Is Not a Lead Database. Timing lives in The 12-Month Outreach Calendar. This library is the words.

    Prompt 1: Hiring email, homeowner version

    I run [company name], a [type] restoration company in [city, state]. We’ve been in business [X] years and are known for [one or two specific things your company does well]. We currently have [number] employees and serve the [geographic area] area.

I need to write a short, plain-text email to past homeowner clients who we’ve done [water damage / fire damage / mold / storm] work for. We’re currently hiring for [job title]. The goal of the email is to ask if they know anyone — family, friends, people in the trades — who might be a great fit for a company like ours. We want to reach out to trusted contacts before posting the job publicly.

Tone: Personal and warm, like a note from a real person. Not corporate, not salesy. The recipient should feel like we remembered them and value their opinion specifically.

Requirements: Under 150 words. Plain text (no HTML). Sign it from [owner first name] at [company name]. Include a phone number as the only contact info. No subject line needed — just the body.

    Prompt 2: Hiring email, insurance adjuster version

    I run [company name], a restoration company in [city, state]. I need to write a short email to insurance adjusters I’ve worked with on claims. We’re hiring a [job title].

The tone should be collegial — peer to peer, professional but not formal. We want to reach out to trusted colleagues before posting publicly, and we’d appreciate any recommendations they might have. Keep it under 120 words. Plain text. From [owner name]. Include phone number.

Do not use any of these phrases: “I hope this email finds you well,” “I wanted to reach out,” “touch base,” “circle back,” or “leverage.” Write it how a real contractor would talk to an adjuster they’ve worked with for years.

    Prompt 3: Vendor ask (specialty sub search)

    Write a short email from a restoration company owner to their contact database asking if anyone knows a reliable [trade type — e.g., drywall sub, flooring contractor, HVAC tech] in [city/region]. We have a larger project coming up and want to find a quality sub through our network before going the cold-search route.

Context about our company: [2–3 sentences about your company — size, how long you’ve been in business, your service area]. The recipients are a mix of past homeowner clients, insurance industry contacts, and trade partners.

Tone: Casual and direct. Like asking a trusted colleague. Under 100 words. Plain text. From [owner name]. Phone number only.

Optional addition: Add one sentence at the end that invites the recipient to reach out directly if the description matches their own business.

    Prompt 4: Seasonal safety email (winter freeze)

    I run a water damage restoration company in [city, state]. I want to send a helpful, non-promotional email to past homeowner clients before freeze season. The goal is to give them genuinely useful information about preventing the kind of water damage we see most commonly in [our region] in winter.

Specific things to cover: [list 3–4 real things relevant to your region]. These should be specific to [region] winters, not generic national advice.

Tone: Knowledgeable and helpful, like a trusted expert checking in on a neighbor. No sales pitch, no CTA other than “if you have questions, we’re here.” Under 200 words. Include a link placeholder for [blog post URL] if they want to read more. From [owner name].

    The rest of the library (on the live article)

    Prompts 5–9 are on the live page. Use that URL. Do not treat this SKU page as a rewrite of that article.

    • Prompt 5: Post-storm check-in to past homeowners. Warm, community-focused, not a pitch. Under 120 words.
    • Prompt 6: Company anniversary or milestone. Thank the people who have been part of the journey. No CTA. No offer. Under 175 words.
    • Prompt 7: Brand-voice rewrite. Paste two real emails you have sent, then the draft, and ask Claude to make it sound like you.
    • Prompt 8: Eight subject-line options. Personal, no click-bait, no exclamation points, no “Quick question for you!”
    • Prompt 9: Batch personalization. CSV of past clients. One opening sentence per row that references job type and, if the job is older than 18 months, that it has been a while. Up to 20 rows at a time.

    Full text: tygartmedia.com/restoration-crm-claude-prompt-library.

    How to get better drafts

    • Name the phrases you do not want: “I hope this finds you well,” “reaching out,” “touch base,” “leverage.”
    • Give two sentences of real company context. History, reputation, service area, typical client.
    • Iterate in the same conversation. “Good, but make it shorter.” Do not start a new chat for every revision.
    • Ask for three versions: shorter, more formal, more casual.
    • Review everything before it sends. Claude will sometimes assume details you did not provide.

    A free claude.ai account is enough for a full annual campaign calendar. Claude Pro is not required for this use case. Store the filled-in prompts in Notion so you are not hunting them before each send. Using AI to draft is fine if you review and approve every email. The relationship still has to be yours.

    If you want the packaged skill

    The method and the live article are free to use. Buy Now is the Claude Skill package, delivered by email after checkout, so the library is installed instead of copy-pasted from the article each time. Same Square button at the top of this page.

  • AI for Water Damage Restoration — 4 Claude Skills

    AI for Water Damage Restoration — 4 Claude Skills

    $29

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy these four skills and do it yourself. Paste each block into Claude Project Instructions. Use them on the next water call. Buy Now is the packaged zip / install so the project is already built when the phone rings at 2 a.m.

    Water damage restoration is a 24/7 business. The company that communicates fastest and clearest wins the job. Between emergency calls, adjuster coordination, and anxious homeowners, Claude takes the writing load off the operations team.

    How to use this

    • Claude Skills go into Claude Project Instructions.
    • Prompts work in any Claude conversation.
    • Tell it Category and Class, ETA, and what the homeowner has already been told. Vague input makes vague output.

    Create a Claude Project. Paste the skill. Answer what it asks. Review every text and letter before it sends. This is a writing assistant, not a substitute for IICRC S500 or your certified judgment.

    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.

    Example prompt: “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.”

    Example prompt: “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.”

    Skill 2: Insurance Adjuster Communication Writer

    Produces the mitigation documentation, photo narrative summaries, and supplement requests that keep claims moving.

    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.

    Example prompt: “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.”

    Skill 3: Contents and Rebuild Communication Writer

    Handles pack-out, demo scope, rebuild timeline, and walkthrough communications 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.

    Give it the real scope and what the homeowner has already heard. Do not let it invent a timeline you cannot keep.

    Skill 4: Referral Network and Emergency Preparedness Content

    Drafts plumber, roofer, and property manager outreach, plus the educational notes that put you first in the phone when water hits.

    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.

    Example prompt: “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.”

    Optional: Books for Bots

    Upload to a Claude Project if you write them:

    • Company Context Sheet: name, service area, certifications (IICRC WRT, ASD, FSRT), equipment inventory, communication approach.
    • Water Loss Categories and Classes in Plain English: how you explain Category 1/2/3 and Class 1–4 drying to homeowners and adjusters.
    • Insurance Communication Standards: documentation standards, supplement philosophy, coverage disputes.

    If you want the packaged files

    The four skills are on this page. Buy Now is the packaged zip / install, delivered by email after checkout, so the Project Instructions are ready when the next water call comes in. Same Square button at the top of this page.

  • AI for Restoration Contractors — 4 Claude Skills

    AI for Restoration Contractors — 4 Claude Skills

    $29

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy these four skills and do it yourself. Paste each block into Claude Project Instructions. Run the prompts on real jobs. Buy Now is the packaged zip / install so you are not rebuilding the project from a blank page every time.

    Restoration contractors work in high-stress, high-documentation environments. Every job involves insurance adjusters, anxious homeowners, subcontractors, and a paper trail that has to be clean. Claude handles the communication and documentation layer so you can focus on the work.

    How to use this

    • Claude Skills go into Claude Project Instructions.
    • Prompts work in any Claude conversation.
    • The more specific you are (city, certs, loss type, claim number), the less generic the draft.

    Create a Claude Project. Paste one skill (or all four) into Project Instructions. Start a chat. Answer the questions the skill asks. Review every draft before it leaves your shop.

    Skill 1: Scope of Work Narrative Writer

    Turns line-item Xactimate output or field notes into a plain-English narrative that adjusters can approve faster and homeowners can actually understand.

    Paste into Claude Project Instructions:

    You are a scope of work narrative writer for a restoration contractor.

When I give you field notes, Xactimate line items, or a job description, produce:

1. ADJUSTER NARRATIVE: Technical, specific, organized by trade sequence. Explains the scope and why each line item is justified. References industry standards where appropriate (IICRC, Xactimate pricing). Professional and precise.

2. HOMEOWNER SUMMARY: Plain English. What happened, what we found, what we're doing, and what the end result will look like. No jargon. Under 200 words.

3. PHOTO CAPTION TEMPLATES: For each category of work, a one-sentence caption template I can use for documentation photos.

Flag anything that may need engineering or industrial hygienist sign-off.

Ask me: loss type, affected areas, scope summary, trade sequence.

    Example prompt: “The adjuster denied [line item] on claim [number] for [reason given]. Our position is [your argument]. Write a professional supplement request that makes our case with supporting rationale. Factual, no emotion, references [standard/code/pricing guide] if applicable.”

    Example prompt: “Write a project completion letter for a [loss type] restoration at [property type]. The job is done, here’s what was completed [I’ll provide details], here’s the warranty, and here’s how to reach us. Professional, warm, closes the loop.”

    Skill 2: Insurance Communication Writer

    Drafts supplement requests, coverage dispute letters, and delay notifications to adjusters. Professional, factual, documented.

    Paste into Claude Project Instructions:

    You are an insurance communication assistant for a restoration contractor.

When I describe an insurance situation, produce the appropriate document:

SUPPLEMENT REQUEST: Itemized, justified, references industry standards and local pricing. Professional tone — collaborative not adversarial.

COVERAGE DISPUTE: Factual, specific, cites policy language I provide. Requests reconsideration professionally. Never threatening.

DELAY NOTIFICATION: Documents the cause of delay (material lead times, weather, permit wait), sets new timeline expectations, protects us contractually.

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

Always: factual, documented, professional. Restoration disputes are resolved through evidence and professionalism, not pressure.

Ask me: claim number, situation, what we want to accomplish.

    Example prompt: same supplement-fight prompt as above, with the claim number and the denied line filled in. Keep it factual.

    Skill 3: Homeowner Communication Writer

    Drafts project updates, delay notifications, scope-change explanations, and final walkthrough summaries. Restoration homeowners are stressed. Every message should reduce anxiety and build trust.

    Paste into Claude Project Instructions:

    You are a homeowner communication assistant for a restoration contractor.

Restoration homeowners are stressed. Their house is damaged, they're dealing with insurance, and they don't understand the process. Every communication should reduce anxiety and build trust.

When I describe a situation, draft the appropriate message:

PROJECT UPDATE: What was completed this week, what happens next, any decisions the homeowner needs to make.

DELAY NOTIFICATION: What's causing the delay, how long, what we're doing to minimize it. Be honest — homeowners handle truth better than surprises.

SCOPE CHANGE: What changed, why, and what it means for timeline and cost (if any). Get their acknowledgment documented.

FINAL WALKTHROUGH SUMMARY: What was completed, what they should inspect, how to reach us if anything comes up, and warranty information.

Tone: calm, competent, human. You are the expert. Help them feel in good hands.

    Example prompt: “A homeowner is frustrated because [situation]. They’re calling daily and [specific complaint]. Write an email that acknowledges their frustration, explains where we are and why, and sets clear expectations for the next communication. Calm and professional.”

    Skill 4: Trade Partner and Referral Communication

    Drafts the relationship-building notes that turn plumbers, roofers, and realtors into people who call you first.

    Paste into Claude Project Instructions:

    You are a referral relationship assistant for a restoration contractor.

Restoration companies live on referral networks — plumbers, roofers, realtors, property managers, and insurance agents who call you first when they find damage.

When I describe a relationship I want to build or maintain, draft:

FIRST OUTREACH: Introduce us as a resource, not a vendor. What we do, how we make their clients look good, how to reach us. Under 100 words.

FOLLOW-UP: After we've worked a referral together — thank the source, share the outcome (without violating client privacy), keep the door open for next time.

ANNUAL TOUCHPOINT: Stay top of mind without being annoying. Something useful (tip, resource, seasonal heads-up). Under 75 words.

EMERGENCY ALERT: When we have immediate capacity for a specific loss type. Short, direct, actionable.

Tone: peer-to-peer, trade professional. We're all in the business of taking care of people's homes.

    Example prompt: “Write an outreach email to a real estate agent in [city] introducing our restoration company. We want to be their first call when a transaction uncovers damage. Under 120 words. No sales pitch. Just making ourselves useful.”

    Optional: Books for Bots

    These are PDFs you upload to a Claude Project so Claude reads them in every conversation. The source list:

    • Company Context Sheet: company name, service area, certifications (IICRC, RIA), loss types, equipment, communication standards.
    • Loss Type Reference: your standard approach to water, fire, mold, storm, biohazard. Process, typical timeline, what homeowners need to know at each stage.
    • Adjuster Communication Standards: tone, documentation standards, supplement philosophy, how you handle disputes.

    Write those three docs yourself if you want. Keep them short and true.

    If you want the packaged files

    The method is on this page. Buy Now is the packaged zip / install of the four skills, delivered by email after checkout, so you drop them into a Claude Project instead of retyping. Same Square button at the top of this page.

  • Restoration Leadership Toolkit — Claude Edition

    Restoration Leadership Toolkit — Claude Edition

    $197

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Run the interviews. Score your own bench. Write your own 90-day plan to get out of the truck. Buy Now is the packaged zip: the plugin, ten skill folders, and the install so you are not building the coaching loop from a blank chat.

    This is the AI companion to the Restoration Leadership Toolkit. A restoration owner attaches it to their own Claude. restoration-setup interviews them. Then nine leadership skills coach from doer to leader, using their team, their roles, and their pain points.

    What it is

    A 9-skill Claude plugin plus a shared setup skill. Install into Claude Code, the Claude Desktop app, or Cowork. Setup writes a company-profile.md. Every leadership skill reads it. If you already ran setup from the Operations Kit, it reuses the same profile. One profile powers both.

    You need any Claude that supports Skills / Plugins.

    The skills

    1. restoration-setup. Say “Set up the kit.” Interview plus customize. Shared with the Ops kit.
    2. delegation-1-3-1. Say “Help me delegate this.” Convert an escalated question into one issue, three options, one recommendation. That is the handoff. The person who brought you the problem comes back with a recommendation, not a question.
    3. owner-bottleneck-assessment. Say “Where am I the bottleneck?” A scored self-assessment. Names the top places the company still depends on you.
    4. succession-5ds-checklist. Say “Am I exposed if something happens to me?” Death, Divorce, Disease, Drugs, Departure. Your exposure, plus what to shore up.
    5. accountability-planner. Say “I have a hard conversation to plan.” Structured plan: the issue, the change, the expectation, the consequence. Outputs a script plus a 30-day follow-up.
    6. leadership-readiness-checklist. Say “Is my team ready to lead?” Assess the current bench. Flag single points of failure.
    7. middle-manager-scorecard. Say “Should I promote this person?” Score a person on 9 traits. Recommendation: promote, develop, or not yet.
    8. owner-dependency-audit. Say “What breaks if I disappear for 30 days?” Dependency audit across functions plus a decision-rights map.
    9. leadership-bench-builder. Say “Build my leadership bench.” Candidates, skill gaps, a 90-day development plan per person.
    10. doer-to-leader-90-day. Say “Give me a 90-day plan to step back.” A personalized 12-week transition plan, week by week.

    How to install it yourself

    Option A: plugin (recommended)

    /plugin marketplace add /path/to/leadership-kit
/plugin install leadership-kit@profit-detective
/leadership-kit:restoration-setup

    On Desktop and Cowork, type the same /plugin commands in the chat.

    Option B: personal skills (simplest)

    Copy each folder in skills/ into ~/.claude/skills/ (Windows: C:\Users\<you>\.claude\skills\). Then tell Claude “run restoration setup.”

    First run

    Run restoration-setup. About five minutes on your company and team. It saves company-profile.md. After that, every tool is tailored to your people and how you run jobs.

    Using it

    Just talk.

    • “My ops manager keeps escalating everything to me. Help me delegate it.” → delegation-1-3-1
    • “Score my lead tech for a crew-chief promotion.” → middle-manager-scorecard
    • “What breaks if I take two weeks off?” → owner-dependency-audit
    • “Build me a 90-day plan to get out of the truck.” → doer-to-leader-90-day

    The 1-3-1 handoff, in plain terms

    Someone brings you a problem. You do not solve it in the hallway. You send them back to write:

    1. One issue (the actual decision, not the whole week)
    2. Three options they can live with
    3. One recommendation, with why

    You decide. They own the work. That is how you stop being the bottleneck without abandoning the job.

    The 5 Ds, in plain terms

    Walk your company against Death, Divorce, Disease, Drugs, and Departure. For each, ask what breaks, who has the keys, and what you would shore up this quarter. The skill scores the exposure. You still make the calls.

    What the zip contains

    • .claude-plugin/ (plugin.json + marketplace.json)
    • skills/ (10 folders: setup plus the nine leadership skills)
    • README.md

    The Notion Leadership Toolkit is the fill-in worksheets. These skills run them conversationally. Coaching and operational assistant only. Not legal or HR advice.

    If you want the packaged install

    You can run this method from the outline. Buy Now is the zip delivered by email: plugin files, the ten skills, and setup so you install once and start talking. Same Square button at the top of this page.

  • SiteBoost — Site Connection & Audit

    SiteBoost — Site Connection & Audit

    $297

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and connect and audit the site yourself. Buy Now is Will doing the one-time setup: Application Password, REST API check, full inventory, and the baseline reports.

    Site Connection and Audit is a service. Square lists it as a one-time setup at $297. It is the front door for every other SiteBoost SKU. The public vertical pages include it inside the pilot. Alone, it is how a site gets on the board without anyone rewriting a post yet.

    Self-hosted WordPress only. REST API on (the default). Squarespace, Wix, and Webflow are not compatible. The /siteboost/ hub is blunt about that.

    How Will connects a site

    wp-connect is the gateway skill. Nothing else in the WordPress stack runs until this works. The 23-site stack article on tygartmedia.com puts a new site at about 20 minutes: Application Password, registry, first audit.

    1. Confirm the site is self-hosted WordPress. Open /wp-json/wp/v2/ in a browser. You should see a JSON index, not a 404. If the REST API is blocked, stop and fix that before anyone shares a password.
    2. In WordPress, go to Users → Profile (or Users → Application Passwords, depending on version). Create an Application Password for a user who can edit posts. Name it something you will recognize later, like “SiteBoost” or “REST audit.” Copy it once. This is not the login password. wp-connect will not use the login password.
    3. Test the connection. GET https://yoursite.com/wp-json/wp/v2/users/me with HTTP Basic auth, username plus the Application Password. A 200 with your user object means you are in. A 401 means the password or user is wrong. A 403 often means a security plugin is blocking REST for that user.
    4. Confirm you can list posts: GET /wp-json/wp/v2/posts?per_page=1&status=publish. If users/me works but posts 403, the user is missing the edit_posts capability.
    5. Write down: site URL, WordPress version if you can see it, hosting (WP Engine, SiteGround, Flywheel, Kinsta, Cloudflare in front, or other), whether Yoast / Rank Math / AIOSEO is present, and who holds the Application Password. Do not put the password in a public doc.

    The public SiteBoost pages name the hosts they have used this pattern on: WP Engine, Flywheel, SiteGround, Cloudflare-proxied sites, GCP Compute Engine, DigitalOcean, Kinsta, bare metal. The requirement is the REST API, not a specific host.

    Do not install a plugin to “help” the connection. SiteBoost’s rule is no plugins added to the client site. Application Passwords are built into WordPress 5.6 and later.

    What the audit checks

    wp-site-audit is the skill that runs at the start of any new site. Fetch all published posts (per_page=100, walk pages). For each post, score the same fields:

    • Word count. Thin is under 500 words.
    • Title tag and slug quality.
    • Excerpt / meta description present, empty, or polluted (raw JSON or leftover code in the excerpt is a real pattern; wp-clean-meta exists to strip it).
    • Categories and tags. Uncategorized is a fail. wp-taxonomy-fix wants 1 to 2 categories and 5 to 10 tags.
    • Featured image present or not.
    • Internal links in (orphans: nothing points here) and internal links out (dead-end posts).
    • Schema present or not, and which types if you can see them (Article, FAQPage, HowTo, BreadcrumbList, Speakable).
    • FAQ section present or not.
    • Outbound source citations present or not.

    Also roll up site-level numbers: total published posts, total pages (count them, do not edit them), taxonomy health (how many categories, how many unused tags, how many posts still Uncategorized).

    The 60-point WordPress SEO Audit Template on tygartmedia.com is the longer human version of this, in six categories: Technical, On-Page, Content, Schema, Local, Analytics. Tools it wants open: Google Search Console, Bing Webmaster Tools, PageSpeed Insights, your SEO plugin, validator.schema.org, an incognito window. Order matters: Technical first, then On-Page, Content, Schema, Local, Analytics. A quick pass is the high-impact rows. A full pass is a few hours the first time. Re-audit quarterly, and after a redesign, a migration, or a plugin purge.

    SiteBoost’s service audit, as sold, is the content-and-baseline cut of that: inventory, schema gaps, FAQ gaps, before numbers. It is not a Core Web Vitals engagement and it is not a local-pack rebuild. If you want the 60-point sheet as a Notion checklist, that is a different SKU (WordPress SEO Audit Template).

    The four reports you should produce

    The public SiteBoost pages name these deliverables. If you are doing this yourself, write the same four:

    1. Content inventory. One row per published post. URL, title, date, word count, category, meta yes/no, FAQ yes/no, schema yes/no, internal links in/out, notes.
    2. Schema gap report. Which posts have no JSON-LD. Which have plugin-bloated or invalid markup. Priority by page type (Article on posts, FAQPage where a FAQ exists or should, HowTo only on real procedures).
    3. FAQ gap report. Which posts have no Q and A block and no FAQPage schema. Those are the AEO queue.
    4. Before baseline. Search Console coverage and the queries / URLs you will watch. A short note on AI visibility for a handful of real questions in your market (do you show up in Perplexity or an AI Overview today?). Write the date. This is what a 60-day report compares to.

    Priority the way wp-site-audit does: Critical (taxonomy / metadata), High (SEO / AEO / thin content), then optimization (links, expansion). The recommended next skills, if you are running Claude, are wp-taxonomy-fix, wp-content-expand, wp-schema-inject, wp-interlink, then the refresh stack.

    What you do not do in this SKU

    • Do not rewrite posts. That is Existing Post Optimization or the Pilot.
    • Do not publish new articles. That is New Article Publishing.
    • Do not edit Pages, bios, or service templates unless the owner asked in writing. Toolbox rule: posts, not pages.
    • Do not leave the Application Password in chat logs or a public Notion page.
    • Do not claim results. You do not have a after yet. You have a before.

    If you want Will to connect and audit

    You can create the Application Password and fill a spreadsheet this afternoon. Buy Now is Will doing the connection and the four reports, then emailing you the baseline and the recommended ten. Same Square button at the top. $297, one time.

    The Pilot Bundle includes this connection plus ten post optimizations and the 60-day report. The Monthly Retainer assumes the site is already connected. If you only want the skill files so your own Claude can connect and audit, that is the WordPress SEO Skill Pack (Starter has wp-connect, wp-post-fetch, and wp-site-audit).

  • WordPress SEO Skill Pack – Starter

    WordPress SEO Skill Pack – Starter

    $29

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do the on-page work yourself in the WordPress editor. Buy Now is the five packaged Claude skill files so your own Claude can connect to the site and run the same steps.

    Starter is the first tier of the WordPress SEO Skill Pack. The live sales page at /wordpress-seo-skills/ lists five skills: wp-connect, wp-post-fetch, wp-site-audit, wp-seo-refresh, wp-clean-meta. $29. It is the connect-and-on-page layer. It is not the AEO, GEO, schema, or interlink stack. Those start at Pro.

    What you need before any skill runs

    • Claude Pro, Max, or Team. The sales page names those tiers.
    • A self-hosted WordPress site with the REST API on.
    • A WordPress Application Password. Users → Profile. Thirty seconds. Not the login password.

    No plugin is required. Everything in this pack talks to /wp-json/wp/v2/.

    If you bought the zip: drop the skill files into Claude Desktop (Cowork) or Claude Code. Then say “connect to my WordPress site” and give the URL, username, and Application Password. The skills ship with placeholders (USER:PASS, SITE). You fill those in. There are no client credentials in the pack.

    The five skills, and the method each one encodes

    1. wp-connect

    Gateway. Must run first. Takes site URL, username, Application Password. Tests GET /wp-json/wp/v2/users/me. Returns whether you are authenticated and which endpoints answered. No other wp- skill works until this is green. If you are doing it by hand, that same curl is the test.

    2. wp-post-fetch

    Load one post so you can see it the way the editor sees it. The refresh skills fetch with context=edit. By hand: GET /wp-json/wp/v2/posts/{id}?context=edit. Read title, slug, excerpt, content, categories, tags. Do not write yet. You cannot refresh what you have not read.

    3. wp-site-audit

    Run this at the start of a site, not after you have already rewritten three posts. Fetch published posts (per_page=100, paginate). For each post, mark:

    • Missing tags, categories, featured image, excerpt / meta
    • Metadata pollution (raw JSON or leftover code in the excerpt)
    • Orphans (no internal links in) and dead-ends (no internal links out)
    • Thin content (under 500 words)
    • Schema present or not
    • Taxonomy health

    Output a prioritized report: Critical (taxonomy / metadata), High (SEO / AEO / quality), then optimization opportunities. That report is your work order. Starter will not auto-fix taxonomy or inject schema. It will tell you which posts are dirty.

    4. wp-clean-meta

    Strip pollution. The 23-site stack article describes this as removing legacy artifacts from excerpts. The audit skill flags raw JSON / code in excerpt fields. Do this before you write a new meta description, or you will be fighting leftover plugin junk. By hand: open the post, clear a garbage excerpt, save a real 140 to 160 character description.

    5. wp-seo-refresh

    The on-page pass. Fetch the post, name the target keyword from the topic, then write:

    1. Title, max about 60 characters, keyword-rich, front-loaded
    2. Meta description, about 155 to 160 characters
    3. Slug: lowercase, hyphenated, keyword-rich (only change it if the current slug is junk)
    4. H2 / H3 hierarchy
    5. Keyword distribution, including the first 100 words
    6. A note of internal-link opportunities (Starter does not run wp-interlink; you place the links yourself or upgrade)

    Then update the post via the REST API and report what changed.

    A Starter session you can run today

    1. Connect. users/me returns 200.
    2. Audit the site. Write the Critical and High lists.
    3. Clean meta on anything the audit marked as polluted.
    4. Pick one High post that is over 500 words. Fetch it. Run the SEO refresh fields above.
    5. Validate the title and meta lengths. Ping IndexNow (Rank Math Instant Indexing, Yoast, or the official IndexNow plugin). Confirm in Bing Webmaster Tools.

    That is the honest Starter method: connect, see the mess, clean the excerpt, fix on-page SEO on one post. Title, slug, meta, headings. Not FAQ schema. Not entity saturation. Not a link graph.

    What Starter does not do

    • No wp-aeo-refresh. No definition box, no 6 to 8 FAQs, no FAQPage schema.
    • No wp-geo-refresh. No speakable / LLMS.txt / named-entity pass as a skill.
    • No wp-schema-inject, wp-interlink, wp-taxonomy-fix, wp-full-refresh, or content pipeline.
    • No new-article factory. You can still write a post by hand using the six-step workflow on the New Article Publishing page.

    If you want those, Pro is the 14-skill stack. Agency adds onboarding and thin-content expansion. If you want Will to do the post instead of running skills, that is SiteBoost Existing Post Optimization.

    If you want the packaged files

    You can keep a checklist and do every Starter step in wp-admin. Buy Now is the five .skill files delivered by email after checkout, genericized, with placeholders for your own site. Same Square button at the top. $29.

    Install, connect, audit, clean, refresh. That is the pack. The sales page’s “full refresh post 123” line (SEO then AEO then GEO then schema then interlink) is the Pro orchestrator, not Starter.

  • WordPress SEO Skill Pack – Pro

    WordPress SEO Skill Pack – Pro

    $79

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and run the full three-layer stack yourself. Buy Now is the 14 packaged Claude skill files so your own Claude can do it on your WordPress site.

    Pro is the middle tier of the WordPress SEO Skill Pack. $79. The live sales page lists 14 skills: everything in Starter, plus wp-aeo-refresh, wp-geo-refresh, wp-schema-inject, wp-taxonomy-fix, wp-interlink, wp-full-refresh, wp-content-pipeline, content-brief-builder, and content-quality-gate. That is the production sequence Tygart Media uses on a single post: SEO, then AEO, then GEO, then schema, then interlink.

    Install and connect

    Same requirements as Starter. Claude Pro / Max / Team. Self-hosted WordPress. Application Password. Drop the skill files into Claude Desktop (Cowork) or Claude Code. Say “connect to my WordPress site.” wp-connect tests /wp-json/wp/v2/users/me. Stop if that is not a 200.

    The sales page’s operator line for this tier: “full refresh post 123.” That trigger is wp-full-refresh. It is the orchestrator. Do not start there on a site you have never audited.

    The 14 skills, in the order you should actually use them

    Foundation (from Starter)

    • wp-connect. Authenticate. Gateway.
    • wp-post-fetch. Load one post with context=edit.
    • wp-site-audit. Inventory, orphans, thin posts, missing meta, schema gaps. Run first on a new site.
    • wp-clean-meta. Strip excerpt pollution before you write new meta.
    • wp-seo-refresh. Title (about 60 characters), meta (about 155 to 160), slug, H2/H3, keyword in the first 100 words.

    Taxonomy, before you interlink

    wp-taxonomy-fix has two modes: one post, or site-wide. Design 3 to 7 top-level categories. Each post gets 1 to 2 categories (never Uncategorized) and 5 to 10 tags (topic, technology, use case, audience, format). Create missing terms via the API, assign, then normalize duplicate tags. Toolbox lists this as a prerequisite for wp-interlink. If categories are a junk drawer, your link graph will be a junk drawer.

    The same skill can write two-layer descriptions on category and tag archives: a 140 to 160 character meta excerpt, then a 400 to 600 word hub body with internal links to the top posts in that cluster. PATCH /wp/v2/categories/{id} and /wp/v2/tags/{id} on the description field. Most themes print that above the post grid.

    The three-layer refresh

    wp-aeo-refresh. Direct-answer opening, question H2s, FAQ pairs, list-shaped answers, FAQPage schema. SiteBoost existing-post copy uses a 40 to 60 word definition box and 6 to 8 FAQs. The older publish skill used 3 to 5. Use the PAA list in front of you, not a fake number.

    wp-geo-refresh. Entity saturation, factual density, context richness, source attribution, topical breadth, semantic clarity. Schema it adds: richer Article metadata, entity markup, Speakable. The citing-sources article is the house rule: name the organization, link the primary source, sources list at the bottom, visible last-updated, dateModified in schema. No fabricated stats.

    wp-schema-inject. Detect the type the post actually is and inject JSON-LD. The schema injection sprint’s menu: FAQPage, Article, HowTo, Service, LocalBusiness, Speakable, BreadcrumbList. Validate with Google’s Rich Results Test. Fix failures. Do not leave plugin-bloated invalid markup in the body.

    wp-interlink. Hub and spoke, orphan resolution, contextual links. The Copilot / cluster articles on tygartmedia.com use 3 to 5 related posts in the same topical group, descriptive anchors. Do this after the post has a real topic and a real category, not before.

    wp-full-refresh. Runs SEO + AEO + GEO + schema + interlink in that sequence on one existing post. This is the “do everything to this post” skill. Use it when the audit already said the post is worth the pass.

    New content, not just refreshes

    content-brief-builder. Keyword research to a brief, before anyone writes. Feeds the pipeline. A brief that cannot name the query, the intent, the PAA list, and the internal-link targets is not a brief.

    wp-content-pipeline. Draft to live: write → SEO → AEO → GEO → schema → taxonomy → interlink → publish. Toolbox order. Same six-step human workflow as the New Article Publishing page, encoded as a skill chain.

    content-quality-gate. Pre-publish. Unsourced claims and fabricated numbers get flagged. Run this before any publish, batch or single. The operator guide’s failure mode is the same: fake density backfires when an AI system checks you.

    A Pro session on one site

    1. Connect. Audit. Clean polluted excerpts.
    2. Fix taxonomy on the posts you are about to touch (and on the hub category if it has no description).
    3. For each chosen existing post: wp-full-refresh, or the layers by hand in SEO → AEO → GEO → schema → interlink order.
    4. For a new article: brief → pipeline → quality gate → publish.
    5. IndexNow on every URL you created or updated. Confirm in Bing Webmaster Tools.
    6. Log before/after: title, meta, word count, FAQ count, schema types, internal links added.

    The operator guide’s weekly rhythm still applies if you are using Pro on a real site: Monday audit, Tuesday to Thursday execute, Friday verify. Pro is the toolkit. It is not a retainer.

    What Pro still does not include

    Agency adds three reference guides (SEO, AEO, GEO), wp-content-expand (deepen thin posts without overwriting), and wp-new-site-setup (client onboarding). If you are onboarding other people’s sites every week, that is the Agency door. If you want Will to run the posts instead of running skills, that is SiteBoost.

    If you want the packaged files

    You can run every layer above in the block editor with a checklist. Buy Now is the 14 .skill files delivered by email after checkout. Same Square button at the top. $79.

    Starter is the five-skill on-page subset if you only need connect / audit / SEO refresh. Agency is this stack plus onboarding and expansion.

  • WordPress SEO Skill Pack – Agency

    WordPress SEO Skill Pack – Agency

    $149

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and run it across more than one WordPress site yourself. Buy Now is the 19 packaged Claude skill files plus the three reference guides, so your own Claude can onboard a site, expand thin posts, and run the full stack.

    Agency is the top tier of the WordPress SEO Skill Pack. $149. The live sales page lists 19 skills: everything in Pro, plus an SEO reference guide with schema templates, an AEO reference guide, a GEO reference guide, wp-content-expand, and wp-new-site-setup. The thesis on the launch page: genericized versions of the production wp- skills, no client credentials, placeholders you fill with your own Application Passwords.

    What “agency” means here

    Not a Tygart Media retainer. The pack is for someone who already has (or is about to have) more than one self-hosted WordPress site and wants the same connect → audit → refresh → publish machine on each. The 23-site stack article is the operating picture: one Application Password per site, one audit at the start, skills composed so a full refresh is a named sequence instead of a vibe.

    Requirements stay the same: Claude Pro / Max / Team, REST API on, Application Password, no plugin required. Install the files in Claude Desktop (Cowork) or Claude Code. Connect per site. Do not reuse one app password across clients.

    Onboard a site (wp-new-site-setup)

    The 23-site article times a new site at about 20 minutes: generate the Application Password, add the site to your registry, run the setup / audit skill, and the stack is usable. wp-new-site-setup is that onboarding workflow. By hand, the same steps are:

    1. Confirm /wp-json/wp/v2/ answers. Self-hosted only.
    2. Create an Application Password for an editor-capable user. Label it with the client and the date.
    3. wp-connect. users/me = 200.
    4. wp-site-audit. Full published-post inventory. Critical / High / optimization lists.
    5. Note the SEO plugin (Yoast, Rank Math, AIOSEO) because meta fields differ. A WeConvene audit note in Notion called this out: a skill that only knows Yoast / Rank Math will miss AIOSEO fields.
    6. Write the four baseline artifacts from the SiteBoost audit page: inventory, schema gaps, FAQ gaps, before numbers in Search Console.
    7. Agree the first ten posts or the first briefs before anyone writes. Agency without a queue is just a folder of skills.

    Toolbox rule you should keep: posts, not pages, unless the client put a Page in writing. Do not “clean up” the homepage on day one.

    Expand thin posts (wp-content-expand)

    This is the Agency skill Pro does not have. Never overwrite. Fetch with context=edit. Flag sections under 150 words, intros under 100, missing subtopics, missing examples, outdated stats, missing close. Add 250 to 400 words per new section. Append. Update the modification date because you actually changed the content. Report the word-count increase. The skill’s own bar: get the post over 500 words before you pretend it has SEO authority.

    Then run the Pro refresh stack on the expanded post. Expansion without SEO / AEO / GEO / schema is just a longer stub.

    The Pro stack, still the daily work

    Once a site is onboarded, Agency work is Pro work, repeated:

    • wp-seo-refresh → wp-aeo-refresh → wp-geo-refresh → wp-schema-inject → wp-interlink, or wp-full-refresh to run that chain.
    • wp-taxonomy-fix, including the two-layer category / tag descriptions if archive pages are stubs.
    • content-brief-builder → wp-content-pipeline → content-quality-gate for new articles.
    • wp-clean-meta whenever an excerpt is polluted.

    The three reference guides are the templates sitting next to those skills: SEO (on-page + schema templates), AEO (direct-answer / FAQ / PAA), GEO (entities, density, speakable, citations). Use them as the written standard when more than one person is allowed to run a refresh. If the guide and the skill disagree, the skill’s field list wins for execution; the guide wins for “what good looks like.”

    A week across more than one site

    Same rhythm as the operator guide, scoped to a roster:

    1. Monday: per-site audit score. What is still Critical. This week’s existing posts and this week’s briefs, named by URL and keyword.
    2. Tuesday to Thursday: expand anything under 500 words that you committed to, then full-refresh. New articles through the pipeline and the quality gate.
    3. Friday: Rich Results Test, IndexNow, log. One log line per URL. If you cannot say what changed, it did not ship.

    Monthly, not weekly: taxonomy health, orphan scan, meta-pollution scan, Search Console versus last month. That is the maintenance layer from the 23-site article. Do not burn a week on dashboards.

    IndexNow on every publish and every update. Official plugin or Rank Math / Yoast Instant Indexing. Confirm in Bing Webmaster Tools. Agency volume without a ping is a lot of work the engines have not been told about.

    What this pack is not

    • It is not SiteBoost. SiteBoost is Will (or Tygart Media) doing the work on the site. This pack is the skill files so you can do it.
    • It is not the $297 Connection and Audit service, the $597 pilot, or the $997 retainer. Those are done-for-you doors. The methods on those pages are the same layers. The deliverable is different.
    • It is not a prompt pack of 50 one-liners. The launch page’s distinction: workflows with error handling and a report, genericized from production skills.

    If you only have one site and you only need on-page, Starter is enough. If you have one site and you want the full refresh + pipeline, Pro is enough. Agency is the onboarding + expansion + reference-guide tier.

    If you want the packaged files

    You can run every step in this article with Application Passwords and a checklist. Buy Now is the Agency zip: 19 skills and the three reference guides, delivered by email after checkout, placeholders only, no one else’s credentials. Same Square button at the top. $149.

    If you would rather not run Claude at all, buy the matching SiteBoost service instead of this pack.

  • Complete Restoration Operating System (Notion + AI)

    Complete Restoration Operating System (Notion + AI)

    $597

    Delivered by email after checkout.

    Buy Now →

    Secure checkout via Square — all major cards accepted

    You can copy this method and do it yourself. Build the six Notion databases. Write the 17 SOPs. Hang the 12 KPIs. Talk your own Claude through intake, equipment, claims, and Friday numbers. Buy Now is the packaged flagship: the Notion workspace you duplicate, plus the 8-skill plugin zip, so you are not wiring the system of record and the AI from a blank page.

    This is the Notion + AI operating system for a restoration shop. Notion is the system of record. The plugin is the expert you talk to. Outputs from each skill are formatted to paste into the matching Notion tool.

    What it is

    Two halves that are meant to run together.

    Notion half. Six plug-and-play tools plus an IICRC protocol lookup. Job tracking, equipment, claims, SOPs, KPIs, crew onboarding. Duplicate them into one workspace page named something like Operations. One sidebar section, whole business.

    AI half. An 8-skill Claude plugin. A setup skill runs a five-minute interview, writes a company-profile.md, and every other skill reads it. SOPs, KPI targets, claims drafts, and onboarding plans come out in your voice.

    You need a free Notion account and any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.

    The six Notion tools

    1. Restoration Job Tracker Pro. Every job from first notice of loss to final invoice, with live margin. This is the hub. Everything else hangs off jobs.
    2. Equipment Inventory & Deployment Tracker. Where every air mover and dehu is, and what each one is earning. Asset IDs, daily rates, current deployments.
    3. Insurance Claims Command Center. Claims, adjusters, documentation, supplements, and aging balances in one place.
    4. Restoration Company SOP Library (17 SOPs). The core procedures, written down. Status starts as Template. Flip to Adopted when you approve each one.
    5. Restoration Business KPI Dashboard. The 12 numbers that move profit. Friday 15 to update. One summary row on the first business day of the month.
    6. Crew Onboarding & Training Tracker. Roster, certifications with expiration dates, equipment sign-offs. Next hire, duplicate the checklist set.

    Plus IICRC Protocol Lookup. Ask “what does S500 say about Category 3 water?” and get a plain-English pointer plus PPE. It is a lookup assistant, not a substitute for the published standard. Defer to current IICRC text, local codes, and your certified judgment.

    The 17 SOPs to write (or adopt)

    If you are building this yourself, start a table with SOP #, title, category, owner role, linked standard, and status (Draft / In Review / Active / Needs Update). The kit’s 17 are:

    1. SOP-01 Water Damage: Initial Inspection & Scoping
    2. SOP-02 Water Extraction & Category Determination
    3. SOP-03 Structural Drying & Daily Monitoring / Psychrometry
    4. SOP-04 Antimicrobial Application
    5. SOP-05 Mold Remediation: Containment Setup
    6. SOP-06 Mold Remediation: Removal & Clearance
    7. SOP-07 Fire & Smoke: Soot Assessment & Cleaning
    8. SOP-08 Contents Pack-Out & Inventory
    9. SOP-09 Equipment Setup, Tracking & Retrieval
    10. SOP-10 PPE & Job-Site Safety
    11. SOP-11 Customer Communication & Daily Updates
    12. SOP-12 Photo Documentation & Moisture Logging
    13. SOP-13 Estimate Writing & Xactimate Scoping
    14. SOP-14 Insurance Adjuster Coordination & Supplements
    15. SOP-15 Job Completion, Walkthrough & Certificate of Satisfaction
    16. SOP-16 Invoicing & Collections
    17. SOP-17 New Job Intake / FNOL Handling

    Do not customize all 17 today. Adopt the water set first. The rest within the month. Swap in your company name, your equipment, your local disposal rules.

    The 12 KPIs

    Build a dashboard with KPI, category, definition, frequency, owner, target, this month, last month, trend. The kit tracks these twelve:

    • Revenue (Financial, monthly)
    • Gross Margin % (Financial, monthly, target ≥ 45%)
    • Net Profit % (Financial, monthly, target ≥ 12%)
    • Days Sales Outstanding / AR Aging (Financial, monthly, target ≤ 45 days)
    • Average Job Size (Financial, monthly)
    • Lead-to-Job Conversion % (Sales, weekly, target ≥ 35%)
    • Jobs Sold (Sales, weekly)
    • Average Days to Dry (Production, weekly, target ≤ 3.5 days)
    • Labor Efficiency % (Operations, weekly, target ≥ 70%)
    • Equipment Utilization % (Operations, weekly, target ≥ 60%)
    • Rework / Callback % (Customer, monthly, target ≤ 3%)
    • Customer Satisfaction / NPS (Customer, monthly, target ≥ 70)

    Those targets are the kit’s starting case file, not gospel. Mix of mitigation vs reconstruction will shift them. The habit is the product: fifteen minutes every Friday updating statuses.

    How to hang it yourself

    Set them up in this order. Each one feeds the next.

    1. Job Tracker (30-45 min). Add 2-3 active jobs. Real jobs, not test data. Log today’s moisture readings.
    2. Equipment Tracker (30-45 min). Every dehu, air mover, scrubber, and meter, with asset IDs. Set actual daily rates. Log where everything is deployed right now.
    3. Claims Command Center (20-30 min). Add adjusters first. Then a claim record for every active claim. Log outstanding supplements and unpaid balances.
    4. SOP Library (20 min now, ongoing after). Read, customize, flip Status to Adopted as you approve.
    5. Crew Tracker (20 min). Roster, certs, equipment sign-offs.
    6. KPI Dashboard (15 min, then 15 min every Friday). Enter this month’s jobs and leads, including the ones you lost.
    7. IICRC skill (5 min). Install, then ask something real: “Cat 2 toilet overflow into a carpeted hallway. What’s the protocol?”

    If a template ships with rows marked (Sample), keep them while you learn. Delete them once your real data is flowing.

    How the system runs day to day

    • Morning: Job Tracker board. What’s active, what needs a monitoring visit.
    • On every truck roll: equipment deployments updated; moisture readings logged to the job.
    • When the adjuster calls: Claims Command Center open. Every supplement, authorization, and dollar in front of you.
    • New hire starts: Crew Tracker checklist; SOP reading list; sign-offs gate the equipment.
    • Friday: the Friday 15 in the KPI ledger.
    • Month end: one KPI summary row. Review utilization before buying equipment.

    This does not replace JobNimbus, Encircle, or Xactimate. Those are job management, documenting, and estimating. This is the ops layer most shops never finish.

    The 8 AI skills

    1. restoration-setup. “Set up the kit.” Guided interview. First run. The concierge.
    2. job-intake-assistant. “We just got a water call.” New-loss intake, water Cat/Class, scope plus safety, a paste-ready job summary.
    3. equipment-advisor. “How many air movers for this room?” Sizing, placement, monitoring plan.
    4. sop-generator. “Write an SOP for mold containment.” Any of the 17, or a new one, in your voice.
    5. claims-assistant. “Draft a follow-up to the adjuster.” Emails, supplement justifications, aging-claims chase.
    6. kpi-coach. “Here are my numbers this month.” The 12 KPIs computed and trended. Biggest leak named, with fixes.
    7. crew-onboarding-builder. “Onboard a new tech.” Week-1 / 30 / 60 / 90 plus an IICRC certification roadmap.
    8. iicrc-protocol-lookup. “What does S500 say about Cat 3 water?” Plain-English pointer plus PPE.

    Install the plugin yourself

    Option A (recommended). Save the restoration-kit folder. In Claude run:

    /plugin marketplace add /path/to/restoration-kit
/plugin install restoration-kit@profit-detective
/restoration-kit:restoration-setup

    Option B. Copy each folder inside skills/ into ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then say “run restoration setup.”

    Keep company-profile.md in the folder you work in. Every skill reads it.

    If you want the packaged system

    You can rebuild this from the outline above. Buy Now is the flagship delivered by email after checkout: Notion duplicate links for the six tools plus IICRC lookup, the plugin zip (eight skills and the README), and the setup sequence so you drop it in and run. Same Square button at the top of this page.

    This is an operational system only. Not legal, insurance, or licensing advice.

  • AI Agents Are Learning to Check Instead of Guess: The GitHub Context Problem

    AI Agents Are Learning to Check Instead of Guess: The GitHub Context Problem

    Most AI assistants still answer from memory. Ask one a question and it reasons from patterns baked in during training — useful, but static. The moment a question depends on something that changed yesterday, or something that only exists inside your own systems, that static knowledge runs out.

    The more interesting shift happening in AI tooling right now isn’t bigger models — it’s agents that can actually go check. Dispatch-style AI systems, the kind that can spin off an isolated task, open a real shell, browse a real page, or read an actual file, are starting to close the gap between “the AI’s best guess” and “what’s actually true right now.” GitHub is a good test case for why that distinction matters.

    Search-and-cite isn’t the same as read-and-act

    A lot of what gets marketed as an AI “GitHub integration” is really a search layer: the assistant can look up an issue or a pull request and summarize it, with a citation back to the source. That’s genuinely useful for answering “what did that PR change” — but it’s a dead end the moment you need the assistant to actually do something, like open an issue, comment, or verify what a repository’s current state really is.

    The more capable version of this connects an agent directly to real developer tooling: an actual shell, a real git client, real file access. Instead of summarizing a cached snapshot of a repo, the agent can clone it, read the current commit log, open the actual config files, and answer questions against what’s genuinely there today — including the uncomfortable cases, like when the live state doesn’t match what anyone assumed it would.

    Why “just check” is harder than it sounds

    The obvious rebuttal is: shouldn’t a good assistant just check before it answers? In practice, most AI tools default to answering from what they already “know,” because checking is slower and requires actual tool access, not just a knowledge base. The systems that skip the check tend to produce confident, plausible-sounding answers that are quietly wrong the moment reality has drifted from training data — a stale API, a renamed config path, a repo that moved.

    The fix isn’t a smarter model. It’s an agent willing to spend the extra step: open the real file, run the real command, read the real log, before saying anything with confidence. That habit is unglamorous, but it’s the difference between an assistant that sounds right and one that actually is.

    The practical takeaway

    For any business layering AI into real workflows, the question worth asking about a tool isn’t just “how smart is the model” — it’s “what can this thing actually go look at, and will it bother to.” An assistant that can search and summarize is a research aid. One that can open a shell, read your actual repository, and ground its answer in what’s really there is a different category of tool entirely — and it’s the direction the whole space is quietly moving.