Last refreshed: October 13, 2026 against cursor.com/pricing and cursor.com/docs/models-and-pricing.
The live Cursor pricing page lists a new ladder. Free is limited. Plus is $8/month and includes Grok models only. Premium is $30/month with 4x Plus usage and third-party models (Claude, GPT, Gemini) billed at API list price. Super is $100/month (15x). Ultra is $200/month (50x). Teams start at $30+ per user.
The docs page still describes older Pro $20 / Pro Plus $60 / Ultra $200 plans with separate Cursor Models and Other Models pools. Existing subscribers may keep prior plans. Quote both sources. Do not average them.
Claude seats did not move. Pro remains $20/month or $17 annual. Max 5x is $100, Max 20x is $200. Claude Code is included in paid Claude plans and shares the usage pool. API list rates are unchanged: Haiku 5.5 $0.10/$0.50 under 100k prompts, Sonnet 5.5 $2/$10 with $0.10 cache reads, Opus 5.5 $4/$20.
The split that matters for operators: to run Claude models inside Cursor you now need Premium ($30) plus API list charges on top. A Claude Pro seat is still $20 and includes Claude Code. Two products, two meters.
Confirm live numbers on the official pages before you change a workflow. This is the plan structure on the pricing page as of October 13, 2026.
Direct answer: Anthropic moved Claude Code cloud sessions from research preview to general availability on September 23, 2026. Existing Pro subscribers can claim a one-time $100 credit and Max subscribers a one-time $250 credit — but only for cloud-session usage, and only if you claim by 11:59 PM Pacific on October 7, 2026. Unclaimed credit disappears. Claimed credit that goes unused expires November 4, 2026.
What a cloud session actually is
Claude Code running on Anthropic's machines instead of yours. You hand it a task and a GitHub repository; it keeps working after you close the laptop, lose Wi-Fi, or leave the room. Anthropic's pitch: "Cloud sessions run on Anthropic-hosted infrastructure, so the work keeps going even without your computer running."
The practical differences from a local session:
Your laptop is not the bottleneck. No sleep, no battery, no VPN drop killing a long task.
Isolation. The agent works in a hosted environment, not on your machine's files — which limits blast radius.
Accessible everywhere. Start on desktop, check on mobile.
It draws from credit, not just plan limits. The one-time credit applies automatically when you start a session, and it is separate from your weekly usage limits. Anthropic's framing: "If you hit a limit locally, keep going in the cloud until your credit runs out."
The credit, precisely
Pro
Max
One-time credit
$100
$250
Claim deadline
11:59 PM PT, Oct 7, 2026
11:59 PM PT, Oct 7, 2026
Unused credit expires
11:59 PM PT, Nov 4, 2026
11:59 PM PT, Nov 4, 2026
Eligibility
Individual subscriber active Sept 23, 2026
Individual subscriber active Sept 23, 2026
One credit per account. The credit covers cloud sessions only — not chat, not API calls, not local Claude Code. It applies before your regular plan usage, and once it's gone, cloud sessions count against your normal plan limits. There is no separate charge for the cloud container itself.
What you need: a connected GitHub account, because every cloud session works against a repository. No GitHub, no session, no credit use.
How to claim it
1. Confirm your plan. Pro or Max, individual subscription, active on September 23.
2. Connect GitHub. Required before a cloud session will start.
3. Claim. Open claude.ai/code and use the Claim credit prompt, or run /claim-credit inside the Claude Code CLI.
4. Start a session. From claude.ai/code, the Code tab in the Claude mobile app, the desktop app, or claude --cloud in the terminal. Anthropic also lists Routines as a starting point.
5. Watch the dates. Claim by October 7; spend it by November 4. Last call as of today, October 6: the claim window closes 11:59 PM Pacific tomorrow, October 7, 2026. Claim it now — unclaimed credit disappears.
Team and Enterprise users get cloud-session access through premium seats, but the $100/$250 promotional credit is the Pro/Max subscriber offer — evaluate the feature on its own merits if you're outside the promo.
Under the hood
Anthropic runs cloud sessions on fresh Ubuntu 24.04 virtual machines — roughly 4 vCPUs, 16 GB of RAM, 30 GB of disk, per published reports. Organizations that can't let source code run on a vendor's VMs can route sessions to self-hosted environments instead — a separate path from the consumer credit.
Note the contrast with Remote Control: Remote Control connects a web or mobile interface to a Claude Code session running on *your own computer*, so that machine has to stay awake. Cloud sessions remove the machine entirely.
Should you use it?
Treat the credit as a trial budget. Point it at work that's easy to verify: bug fixes with test coverage, dependency updates, questions about a codebase. Check the branch and the pull request the agent produces before merging anything. Anthropic even describes auto-fix of pull requests directly in the cloud as a feature — still check the diff yourself.
For occasional or non-technical users, be honest with yourself: the credit may go unused, because cloud sessions require a GitHub-connected coding workflow to begin with. That's worth knowing before you count on redeeming the full amount.
Last verified: October 2026. Claude Code is Anthropic's terminal coding tool — it lives where developers live, in the command line. Around it has grown a small universe: install paths, seat pricing, credit pools, rate limits, and three sibling agent surfaces that people constantly confuse with it. This guide is the map.
Installing it: two minutes, pick your path
On Windows, it's PowerShell, one command, no Node.js required — the native install path, verified against the May 2026 installer, including the five errors you’ll hit and the exact fix for each. For the general path, it's the one-line npm CLI install plus the Desktop app, done in under two minutes, with the common errors covered.
Claude Code rides on your existing seat — Pro ($20/month), Max ($100 or $200/month), Team, or Enterprise. The API path is a separate console meter, not drawn from your seat. If you're deciding between Pro and Max for dev work, the question is usage volume: Max is for the people who live in the terminal all day.
How the billing actually works: subscriptions vs credit pools
This is the part that surprises people. Interactive terminal use draws on your Pro/Max subscription — it's part of the seat. But since June 15, 2026, Agent SDK and headless (claude -p) usage moved to separate monthly billing. Same tool, two meters, depending on how you invoke it. Know which one you're on before the invoice teaches you.
Claude Code meters two clocks: a rolling 5-hour session window and a weekly bucket. The +50% weekly promo ended September 13, 2026 — what replaced it is a permanent +25% on the weekly limits. Note the model gating: Fable 5.1 is included only on Max and premium seats.
Picking your surface: Cowork vs Code vs Agent SDK vs Managed Agents
Anthropic now has four agent surfaces and they are not interchangeable: Claude Code, Claude Cowork, the Agent SDK, and Managed Agents. Interactive vs autonomous is the real dividing line — which surface fits depends on who's driving and how much autonomy the job needs.
The canonical Cowork workflow: connect your calendar, email, and tasks, write the right prompt, and schedule it to run automatically every morning. A briefing that builds itself before you've had coffee. It's the clearest demo of what the non-code surface is for.
Research snapshot · September 17, 20267 platforms · 14 cited sources
“Always allow” is a scope, not a safety verdict.
The button can mean “for this session,” “for this command in this repo,” “for this site across devices,” or “everything, until you turn it off.” The wording looks universal. The permission is not.
What it usually means
“If this same kind of action happens again inside a defined boundary, don’t interrupt me.”
What it never means
“The system has decided this action is safe, wise, or appropriate forever.”
01
One label. Six possible boundaries.
Before approving, ask three things: what is being authorized, where the grant applies, and when it expires.
One actionApprove this exact send, command, purchase, or change once.
This sessionAllow the tool until the current conversation or work session ends.
Tool or patternAllow a named tool, command prefix, server, or similar operation.
Repo or sitePersist within a project, repository, browser site, or workspace.
User or deviceApply across workspaces on one machine, or across devices via cloud settings.
EverythingYOLO, bypass, or run-everything modes remove broad classes of checks.
Risk rises faster than convenience as the scope moves right.
02
How the major platforms differ
Filter the field. These behaviors come from vendor documentation or documented reporting; unresolved details are marked plainly.
Claude Code
Coding agent
repo + command
Shell-command “don’t ask again” grants persist per repository and command. File-edit approvals last only for the session.
Four settings layers: user, project, project-local, managed.
Deny rules evaluate before ask and allow.
Sensitive paths keep hard prompts.
Cursor
Coding agent
user + project
Auto-review, Allowlist, and Run Everything modes sit above user- and project-level permission files.
Rules can target MCP server:tool patterns.
Terminal rules match command prefixes.
Committed project rules can travel with the repo.
Gemini agents
Coding agent
tool + machine
Always-allow can target a tool, MCP server, or “similar operations.” YOLO/auto-approve is an IDE user setting.
User setting can span trusted workspaces on that machine.
CLI supports command-prefix auto-approval.
Restricted workspaces override YOLO.
ChatGPT agent
Browser agent
no standing grant documented
OpenAI documents per-action confirmations for high-impact actions and “watch mode” on certain sites, but not a general always-allow for agent confirmations.
Login uses human takeover.
Cookies can persist across sessions.
Scheduled-task confirmation behavior is undocumented.
ChatGPT Work
Cloud browser
site + account
Reported controls are per-site: Always ask, Auto approve, and Always allow. The setting follows cloud/account state across devices.
“Always allow” is reportedly marked not recommended.
Consequential actions keep a confirmation gate.
Official help-center documentation was not found.
Copilot Studio
Enterprise agent
rest of session
Makers gate tools per agent; users can approve once, approve for the rest of the session, or deny.
The gate is outside the agent’s own instructions.
Designed for sends, tickets, payments, and similar tools.
Governance can feed Power Platform audit systems.
Grok / Grok Bot
Cloud agent
undocumented
The research did not find reliable xAI documentation defining a standing approval’s scope, persistence, cross-chat reach, or revoke surface.
Do not infer Grok’s behavior from Claude, Cursor, Gemini, or Muse.
Treat each approval as local to the visible task until the product proves otherwise.
Keep consequential actions behind a separate human gate.
03
Does the approval travel?
Usually less than people fear—but sometimes farther than they expect. No researched vendor carries an approval into another vendor’s product.
Platform
Other chats
Other projects
Other devices
Other products
Claude Code
Yes, in same repo
No, unless user-level rule
No, local files
No evidence
Cursor
Yes
Only if rule is shared
Via committed repo file
No evidence
ChatGPT agent
n/a
n/a
n/a
No evidence
ChatGPT Work
Yes, per site
Yes, per site
Yes, cloud/account
No evidence
Copilot Studio
No, session only
No
No
No evidence
Gemini Code Assist
Yes, same IDE
Yes, user setting
Undocumented
No evidence
There is no universal “always.” There is only an approval attached to a boundary.
Main chat vs. project vs. Claude vs. Grok vs. Cursor: treat every surface as a separate authority domain until that product explicitly shows otherwise. Same account does not mean same grant. Same vendor does not mean same product. Similar wording does not mean similar scope.
04
Design the least-annoying safe gate
A practical rule engine based on the converging guidance: reserve human attention for the steps where it changes the outcome.
Approval recommender
Choose an action and its reach. This is a policy aid, not a vendor setting.
Action
Reach
Duration
Recommended gateAuto-run with an audit log
Read-only work inside your own workspace can usually proceed quietly. Log what was accessed and keep secrets excluded.
Quiet lane
Low consequence, reversible, internal.
Read/search
Draft/stage
Organize reversible files
Always log
One-tap lane
Meaningful external or production effect.
Send or publish
Deploy
Account setting
Show real target + content
Friction lane
Money, identity, access, deletion, or irreversible harm.
Typed approval or step-up auth
Bind approval to exact action
Short expiry
Never inherited from a vague grant
05
How standing approvals fail
The danger is rarely “the AI became evil.” It is usually a trusted tool, a changed context, a misleading prompt, or a tired human.
Approval fatigue
A prompt repeated often enough becomes a reflex. The gate still exists visually while meaningful review disappears. This is why tiering beats asking about everything.
Prompt injection through a trusted tool
EchoLeak showed how a crafted email could coerce Microsoft 365 Copilot into exfiltration. TrustFall showed how one generic “trust this folder” click could arm a malicious MCP configuration across coding agents.
Grant outlives the reason
A permanent Bash rule, per-site browser grant, or scheduled-task permission can remain after the original job is over. The next task inherits power it did not earn.
Scope contamination
Repo rules can affect every future task in the repo. Cursor project allowlists can be committed and inherited by teammates. A convenience decision becomes shared infrastructure.
Presented action differs from executed action
If the user sees the agent’s summary instead of the resolved recipient, command, or final payload, the approval can be technically genuine but practically uninformed.
“Run everything” becomes the workaround
If the system asks about trivial reads and destructive writes with equal urgency, users reach for YOLO or bypass modes. Bad UX can manufacture unsafe behavior.
The four repeated cards are not reassurance.
A gate that reappears until the user disables it is approval fatigue in miniature. Whether the repeats came from retry logic or delivery duplication, the safe response is to deduplicate the prompt—not train the user to approve more broadly.
06
No industry standard—yet
There is no binding specification that makes “always allow” mean the same thing everywhere. But the security guidance is converging.
Least agencyGrant the exact command, path, server, tool, recipient, and purpose—not a whole capability.
Time and task limitsPrefer once or session. Standing grants should expire or be reviewed.
Risk tiersRead, write, external send, payment, and security changes should not share one gate.
Per-action verificationPrivileged steps should be rechecked by a policy engine outside the agent prompt.
Presentation integrityShow the real recipient, final text, raw command, and resolved resource.
Immutable receiptsRecord what was shown, what was approved, and what actually executed.
Hard baselinesSecrets, account recovery, money, destructive commands, and broad access should keep non-bypassable checks.
Kill switchesEvery durable grant needs a visible list, revoke action, and safe fallback.
The best feature is not “always allow.” It is “allow this exact thing, for this purpose, until this time.”
Product opportunity: make the scope legible. Let users see a plain-language grant card, a live approval ledger, expiry/count limits, and a one-tap revoke. The system should reduce nagging by grouping low-risk work—not by quietly widening authority.
07
The practical rule for your setup
You already have the right doctrine. The research mainly sharpens where the lines belong.
Auto
Let it run and narrate after.
Reads and research
Drafts and staging
Reversible internal organization
Routine checks with no external effect
Tap
Keep the one-tap human gate.
Email and messaging
Publishing and deploys
Changing live settings
Actions affecting another person
Type
Make the friction intentional.
Money and purchases
Credential/security changes
Deletion or irreversible moves
Broad standing authority
Your “always allow” tap was not reckless.
It was a reasonable response to a low-value repeated prompt. The lesson is not “never use standing approval.” It is: the platform should show the exact scope, make it easy to revoke, and never rely on repetition to win consent. Until Muse exposes that ledger, treat the grant as a convenience whose boundary remains partly unknown.
Verification note: the research read public documentation and web text on September 17, 2026. It did not live-test each product. Undocumented behavior is labeled as such.
Claude is already inside most enterprises — through individual employee accounts, Claude Code on developer machines, and browser extensions — whether IT approved it or not. The security question in 2026 isn’t whether to allow Claude. It’s whether to govern it.
This is a practical security audit checklist for Claude Enterprise deployments in 2026 (see also Anthropic Trust Center). It covers the five domains that matter, the specific CVEs that affect Claude Code, and the configuration steps that close the most significant exposure.
The Current Threat Surface
Five domains for a Claude enterprise security audit.
Claude operates across multiple surfaces — claude.ai web, mobile apps, Claude Code on developer machines, Cowork, and API integrations — each with different data exposure profiles and each requiring different controls.
The most significant 2026 security events affecting Claude deployments:
CVE-2025-59536 (CVSS 8.7): Disclosed by Check Point Research in early 2026. A vulnerability in Claude Code that allows remote code execution through malicious project configuration files — before any trust dialog appears to the user. Affects any organization that has deployed Claude Code without centralized governance.
CVE-2026-21852: Demonstrates how an attacker can redirect all Claude Code traffic to an attacker-controlled server by manipulating the ANTHROPIC_BASE_URL environment variable. Silently exfiltrates API keys and conversation content. Reproducible attack chain.
GTG-1002 campaign (September 2025): Anthropic identified this as one of the first AI-orchestrated cyberattacks at scale, establishing AI developer tooling as an active attack surface.
These are not theoretical risks. They’re documented, reproducible attack chains that affect any Claude Code deployment without centralized governance.
Security Domain 1: Identity and Access
Identity and access — who can create keys and call models.
Configure SSO before any broad rollout. Without SSO, employees authenticate with personal Anthropic accounts — which means no centralized visibility, no revocation capability, and no audit trail.
Implementation steps:
Enable SAML 2.0 or OIDC SSO in the Claude Admin Console. This forces all claude.ai logins through your identity provider (IdP) and prevents personal account fallback.
Enable domain capture alongside SSO. This prevents employees from using personal email accounts to access Claude outside the managed environment.
Configure SCIM provisioning to automate user lifecycle management. When an employee is offboarded from your IdP, their Claude access is revoked automatically.
Implement role-based access controls (RBAC). Not all users need access to all Claude capabilities. Segment by role: standard users, power users with Claude Code, API access holders.
Set up periodic access reviews for Claude access, the same way you review access to other SaaS applications. SailPoint and similar identity governance tools can integrate via the Claude Compliance API.
Audit evidence to collect: SSO configuration screenshots, SCIM provisioning logs, access review completion records.
Security Domain 2: Data Controls
The first security question in every enterprise deployment is where the data goes. The answer depends on which Claude product and deployment model is in use — and it matters enormously for regulated industries.
Data handling by deployment model:
Deployment
Data Retention
Network Path
Zero Data Retention Available
Claude Enterprise (Anthropic console)
30 days default, ZDR available
Public internet
Yes
AWS Bedrock
Per AWS data agreements
VPC/private network available
Yes
Google Cloud Vertex AI
Per GCP data agreements
VPC/private network available
Yes
Microsoft Foundry
Per Microsoft data agreements
Private network
Yes
Claude.ai personal accounts
Anthropic standard terms
Public internet
No
For regulated industries (HIPAA, financial services, government): deploy via AWS Bedrock, Google Cloud Vertex AI, or Microsoft Foundry with private network configurations that keep traffic off the public internet. Enable ZDR (Zero Data Retention) for workloads with sensitive data.
The silent risk: employees using personal claude.ai accounts for work tasks. Data entered into personal accounts is subject to Anthropic’s standard consumer terms, not Enterprise data agreements. SSO + domain capture closes this gap.
Security Domain 3: Claude Code Governance
Claude Code is the highest-risk surface in most enterprise deployments. It runs with the privileges of the developer’s user account, can execute arbitrary shell commands, read the full filesystem, and make outbound network connections.
Hardening steps for Claude Code deployments:
Centralize API key management:
Use organization-managed API keys (via the Admin Console) rather than individually generated keys
Create separate keys per team or project, not shared team keys
Rotate keys on a defined schedule (quarterly minimum)
Monitor for anomalous usage (volume spikes, off-hours activity) — feed audit logs to SIEM
Address the CVE-2026-21852 attack vector:
Audit all developer machines for .claude/settings.json files in project repositories — these can be used to redirect traffic
Block arbitrary ANTHROPIC_BASE_URL overrides via environment variable policy
Add Claude Code traffic to network monitoring so redirected traffic is detectable
Restrict filesystem access:
Prevent Claude Code from running in directories containing production secrets or sensitive data
Use separate working directories for Claude Code sessions, isolated from production credential stores
Code execution controls:
Enable disableBypassPermissionsMode to require explicit approval for shell commands
Log all shell commands executed via Claude Code to the audit trail
Security Domain 4: Audit Logging and Observability
Claude Enterprise audit logs capture user authentication events, model calls with metadata, and file interactions. Without routing these logs to a SIEM, the audit trail exists but isn’t being monitored.
Use the Compliance API to export prompts, responses, and admin actions into DLP and insider risk monitoring workflows
The gap Anthropic hasn’t filled: There is no built-in anomaly detection in the Admin Console. Usage anomaly detection requires SIEM integration and custom correlation rules. This is a known limitation — build it at the SIEM layer.
Security Domain 5: Agentic Workflow Security
Claude Managed Agents and Claude Code used in agentic workflows introduce a category of risk that traditional SaaS governance doesn’t cover: an AI taking autonomous actions in the environment.
Key controls for agentic deployments:
Human oversight checkpoints: For any agentic workflow that takes consequential actions (code commits, file modifications, API calls to production systems), require a human review step before execution. Don’t allow fully autonomous action without an approval gate on high-impact operations.
Tool scope minimization: Define the smallest set of tools an agent needs and give it nothing else. An agent that only needs to read files shouldn’t have shell execution permissions. MCP server connections should be scoped to the minimum required access.
MCP connector governance: MCP servers allow agents to connect to external systems (GitHub, Notion, Slack, etc.). Each MCP connection is an attack surface for prompt injection — a malicious response from an external system can instruct the agent to take unintended actions. Audit which MCP servers are connected; don’t allow arbitrary MCP connections.
Prompt injection defense: Any content that flows from an external system into an agent’s context (web pages, API responses, file contents) should be treated as potentially adversarial. This is the mechanism behind most AI agent security incidents in 2025–2026. Validate and sanitize external inputs before they reach the agent context.
Quick-Reference Audit Checklist
Quick-reference checklist — prove controls, do not assume them.
Use this to assess the current state before deciding what to address first:
Identity
SSO (SAML 2.0 or OIDC) enforced for all Claude access
Domain capture enabled to prevent personal account use
SCIM provisioning configured for automated user lifecycle
RBAC defined by role (standard / power user / API)
Data
Deployment model documented (Anthropic console vs. Bedrock vs. Vertex)
ZDR enabled for sensitive data workloads
Personal claude.ai account use blocked or governed
Data classification applied to determine which workloads can use which deployment model
Claude Code
Organization-managed API keys (not individual)
Per-team/per-project key segmentation
CVE-2025-59536 and CVE-2026-21852 remediation verified
Shell execution logging enabled
Audit and Observability
Audit logging enabled in Admin Console
Logs routed to SIEM
Anomaly detection rules configured
Compliance API integrated with DLP tooling
Agentic
Human oversight gates on consequential agent actions
MCP connections audited and scoped
Prompt injection defenses in place for external inputs
Yes. Claude Enterprise deployed through the Anthropic console with a qualifying enterprise agreement offers zero data retention, where prompts and responses are not logged by Anthropic. ZDR is also available via AWS Bedrock, Google Cloud Vertex AI, and Microsoft Foundry deployments.
What compliance certifications does Anthropic have?
Anthropic holds ISO 27001:2022 and ISO/IEC 42001:2023 certifications and offers HIPAA-ready configurations with Business Associate Agreements to qualifying enterprise customers.
What are the biggest security risks in a Claude Code deployment?
CVE-2025-59536 (remote code execution via malicious project config files, CVSS 8.7) and CVE-2026-21852 (traffic redirection via ANTHROPIC_BASE_URL manipulation) are the most significant documented vulnerabilities. The broader risks are developers using personal Anthropic accounts, shared API keys without rotation, and no audit trail for code context that flows to Anthropic’s servers.
What is the Compliance API?
The Claude Compliance API is an Enterprise feature that exports prompts, responses, files, and admin actions to external monitoring systems — enabling integration with DLP tools (Proofpoint), SIEM platforms (Splunk, Datadog, Elastic), and identity governance tools (SailPoint). It’s the primary mechanism for bringing Claude activity into existing enterprise security workflows.
What is prompt injection in AI agents?
Prompt injection occurs when malicious content in external data sources (web pages, API responses, documents) instructs an AI agent to take actions the operator didn’t intend. In agentic Claude workflows, any content retrieved from external systems can potentially carry injected instructions. Defense requires treating external inputs as untrusted and implementing validation before they enter the agent context.
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
Skills that move owners from doer to leader.
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
restoration-setup. Say “Set up the kit.” Interview plus customize. Shared with the Ops kit.
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.
owner-bottleneck-assessment. Say “Where am I the bottleneck?” A scored self-assessment. Names the top places the company still depends on you.
succession-5ds-checklist. Say “Am I exposed if something happens to me?” Death, Divorce, Disease, Drugs, Departure. Your exposure, plus what to shore up.
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.
leadership-readiness-checklist. Say “Is my team ready to lead?” Assess the current bench. Flag single points of failure.
middle-manager-scorecard. Say “Should I promote this person?” Score a person on 9 traits. Recommendation: promote, develop, or not yet.
owner-dependency-audit. Say “What breaks if I disappear for 30 days?” Dependency audit across functions plus a decision-rights map.
leadership-bench-builder. Say “Build my leadership bench.” Candidates, skill gaps, a 90-day development plan per person.
doer-to-leader-90-day. Say “Give me a 90-day plan to step back.” A personalized 12-week transition plan, week by week.
On Desktop and Cowork, add the plugin from Customize → Plugins instead; the /plugin commands are for Claude Code.
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
1-3-1: one problem, three options, one recommendation.
Someone brings you a problem. You do not solve it in the hallway. You send them back to write:
One issue (the actual decision, not the whole week)
Three options they can live with
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
The 5 Ds — a filter for what lands on the owner.
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.
Frequently Asked Questions
Is there a refund policy?
Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. You will receive your download link — Notion duplicate link, skill file, or both depending on the product.
The Restoration Operations Kit — Claude Edition by Tygart Media is an 8-skill specialized AI plugin that transforms Claude into an operational copilot for property restoration contractors. Available for a one-time payment of $197 on Square, the kit automatically customizes Claude to a contractor’s specific shop profile, generating accurate job scopes, dehumidifier sizing calculations, adjuster supplement justifications, and IICRC-compliant standard operating procedures.
Restoration Operations Kit — Claude Edition
$197
All 8 Claude skills + plugin files — delivered digitally via email within 24 hours.
Secure checkout via Square — all major cards accepted
Developed by Will Tygart and the Tygart Media team, this is the AI operational companion to the Complete Restoration Operations Kit. A restoration owner attaches it to their own Claude instance. It interviews the owner, writes a tailored company-profile.md, and makes every subsequent prompt speak your shop’s exact voice, pricing rules, and crew standards.
Overview: What the Claude Edition Does
Claude skills that turn field chaos into repeatable runs.
An 8-skill Claude plugin. Install it into Claude Code, the Claude Desktop app, or Cowork. 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, not a generic restoration voice.
You need any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.
The 8 Operational Claude Skills
Eight skills on the bench — pick the one that matches the job.
Skill Identifier
Natural Language Trigger
Operational Output & Deliverable
restoration-setup
“Set up the kit”
Guided 5-minute setup creating your persistent company-profile.md.
Replace the path with wherever you saved the folder. On Desktop and Cowork, add the plugin from Customize → Plugins instead; the /plugin commands are for Claude Code.
Start setup:
/restoration-kit:restoration-setup
Option B: Personal Skills Folder (Simplest, No Plugin)
Copy each folder inside skills/ into your personal skills directory at ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then prompt Claude: “run restoration setup.”
First Run Walkthrough
Run restoration-setup first. It conducts a guided 5-minute interview regarding your shop’s services, team size, service area, and rate sheet. It saves a persistent company-profile.md file that every subsequent skill reads so the generated answers sound like your actual shop.
Using the Kit Day to Day
Same four moves. Different job. Less reinventing at 11pm.
You do not need to memorize skill names. Just prompt Claude naturally:
“We just got a fire call on Oak St” → invokes job intake
“Size the equipment for a 15×20 Class 3” → invokes equipment sizing
“Draft a supplement justification for the Alvarez claim” → invokes claims assistant
“Build an onboarding plan for a new crew chief” → invokes crew onboarding
“What PPE for Condition 3 mold?” → invokes IICRC lookup
What the Delivered Zip File Contains
.claude-plugin/plugin.json and marketplace.json
skills/ folder containing all 8 complete skills
README.md with full step-by-step setup walkthrough
Outputs from each skill are formatted to paste into the matching Notion template in the Complete Restoration Operations Kit ($97). The Notion side serves as the operational system of record, while the Claude Edition acts as the intelligence layer.
Frequently Asked Questions
What is the Restoration Operations Kit — Claude Edition?
The Restoration Operations Kit — Claude Edition by Tygart Media is an 8-skill AI plugin for Claude Desktop, Claude Code, and Cowork that automates restoration intake, equipment sizing, insurance claims drafting, SOP generation, and KPI tracking in the contractor’s exact voice.
What is included in the $197 purchase on Square?
The $197 package includes all 8 packaged Claude skills, the plugin.json manifest, marketplace configuration files, installation documentation, and prompt architecture delivered digitally via email.
How does this kit work with the Complete Restoration Operations Kit?
The Claude Edition acts as the operational AI copilot: its outputs are pre-formatted to paste seamlessly into the corresponding Notion databases (Job Tracker Pro, Claims Command Center, KPI Dashboard) of the Complete Restoration Operations Kit.
What Claude plan is required to run the skills?
It runs on any Claude interface that supports skills or plugins, including Claude Desktop, Claude Code CLI, and Cowork. Personal skill mode can also be loaded directly into ~/.claude/skills/.
Is there a refund policy?
Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. You will receive your download link — Notion duplicate link, skill file, or both depending on the product.
$197
Packaged zip delivered by email within 24 hours via Square.
The WordPress SEO Skill Pack — Starter by Tygart Media is a $29 Square product with five Claude skills that authenticate to self-hosted WordPress via Application Password, audit published posts (orphans, thin content under 500 words, excerpt pollution), clean meta fields, and refresh title, slug, and meta description through the REST API. Will Tygart positions Starter as the connect-and-on-page layer only; AEO, GEO, FAQ schema, and interlink automation start in the $79 Pro tier.
WordPress SEO Skill Pack — Starter
$29
Five .skill files delivered by email within 24 hours after Square checkout.
Secure checkout via Square — all major cards accepted
Tygart Media documents the Starter method so site owners can run connect → audit → clean meta → on-page refresh in wp-admin or via Claude. The $29 Buy on Square option delivers five packaged .skill files (wp-connect, wp-post-fetch, wp-site-audit, wp-clean-meta, wp-seo-refresh) by email within 24 hours of checkout.
Starter is the first tier of the WordPress SEO Skill Pack by Will Tygart. It is the connect-and-on-page layer only. Tygart Media ships AEO refresh, GEO refresh, schema injection, and interlink skills in the Pro tier ($79), not in Starter.
Starter vs Pro vs DIY (honest scope)
Tier
Price
Skills / scope
AEO / schema
DIY (this page)
$0
Manual REST API + wp-admin checklist
No — on-page SEO only
Starter (this product)
$29
5 Claude skills: connect, fetch, audit, clean-meta, seo-refresh
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:
Title, max about 60 characters, keyword-rich, front-loaded
Meta description, about 155 to 160 characters
Slug: lowercase, hyphenated, keyword-rich (only change it if the current slug is junk)
H2 / H3 hierarchy
Keyword distribution, including the first 100 words
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
Connect. users/me returns 200.
Audit the site. Write the Critical and High lists.
Clean meta on anything the audit marked as polluted.
Pick one High post that is over 500 words. Fetch it. Run the SEO refresh fields above.
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.
Frequently Asked Questions
What is the WordPress SEO Skill Pack — Starter?
The WordPress SEO Skill Pack — Starter by Tygart Media is a $29 bundle of five Claude skills that connect to self-hosted WordPress via the REST API and run connect-audit-clean-refresh on-page SEO. It does not include AEO, GEO, schema injection, or interlink skills.
What does Starter include versus Pro?
Starter includes five skills for authentication, post fetch, site audit, excerpt cleanup, and title or meta refresh. Tygart Media’s Pro tier ($79) adds wp-aeo-refresh, wp-geo-refresh, wp-schema-inject, wp-interlink, and full-refresh orchestration across 14 skills.
What do I need to run the Starter pack?
Claude Pro, Max, or Team; a self-hosted WordPress site with REST API enabled; and a WordPress Application Password from Users → Profile. Tygart Media ships genericized .skill files—no WordPress plugin required.
Does Starter add FAQ schema or AEO answer packets?
No. Tygart Media documents Starter as on-page SEO only (title ~60 characters, meta ~155–160 characters, slug, headings). FAQPage schema and definition-led answer packets require WordPress SEO Skill Pack — Pro.
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.
$29
Five .skill files — email delivery within 24 hours via Square.
WordPress SEO Skill Pack — Agency by Tygart Media is a $149 Square bundle of 19 Claude skills plus three reference guides (SEO, AEO, GEO) for operators running Will Tygart’s production WordPress stack across multiple self-hosted sites. Agency includes everything in Pro—wp-full-refresh, AEO, GEO, schema, interlink, and the content pipeline—plus wp-new-site-setup for ~20-minute client onboarding and wp-content-expand to add 250–400 words to thin posts before refresh. Tygart Media emails genericized .skill files within 24 hours of checkout; placeholders only, no bundled credentials.
WordPress SEO Skill Pack — Agency
$149
19 skills + 3 guides — email delivery within 24 hours after Square checkout.
Secure checkout via Square — all major cards accepted
Tygart Media documents the multi-site operator method on this page so agencies can onboard clients, expand thin posts, and run SEO → AEO → GEO → schema → interlink without a Tygart retainer. The $149 Buy on Square option delivers 19 packaged .skill files plus three reference guides by email within 24 hours of checkout.
Agency is the top tier of the WordPress SEO Skill Pack by Will Tygart. It includes everything in Pro ($79)—14 production skills plus wp-full-refresh and the content pipeline—plus an SEO reference guide with schema templates, an AEO reference guide, a GEO reference guide, wp-content-expand, and wp-new-site-setup. Deliverables are genericized production workflows: placeholders you fill with your own Application Passwords, never bundled client credentials.
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:
Create an Application Password for an editor-capable user. Label it with the client and the date.
wp-connect. users/me = 200.
wp-site-audit. Full published-post inventory. Critical / High / optimization lists.
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.
Write the four baseline artifacts from the SiteBoost audit page: inventory, schema gaps, FAQ gaps, before numbers in Search Console.
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:
Monday: per-site audit score. What is still Critical. This week’s existing posts and this week’s briefs, named by URL and keyword.
Tuesday to Thursday: expand anything under 500 words that you committed to, then full-refresh. New articles through the pipeline and the quality gate.
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.
Frequently Asked Questions
What is the WordPress SEO Skill Pack — Agency?
WordPress SEO Skill Pack — Agency by Tygart Media is a $149 bundle of 19 Claude skills plus three reference guides (SEO, AEO, GEO). It includes everything in Pro, plus wp-content-expand, wp-new-site-setup, and written standards for teams running the production refresh stack on multiple self-hosted WordPress sites.
What is the difference between Pro and Agency?
Pro ($79) ships 14 skills for the SEO → AEO → GEO → schema → interlink pipeline on one site. Agency ($149) adds wp-content-expand, wp-new-site-setup, and three reference guides—built for operators managing more than one client site with separate Application Passwords per site.
What does wp-new-site-setup do?
wp-new-site-setup is Tygart Media’s Agency onboarding workflow: confirm the REST API, create a labeled Application Password, connect with wp-connect, run wp-site-audit, note the SEO plugin field map, and capture baseline inventory before the first refresh queue.
Is Agency a Tygart Media retainer or done-for-you service?
No. Agency is packaged .skill files and reference guides so you run Claude on your clients’ sites. Tygart Media’s SiteBoost and retainer services are separate; this pack uses placeholders only—no client credentials included.
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.
$149
19 skills + 3 guides — email delivery within 24 hours via Square.
Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Talk to your own Claude. Interview your own shop. Write your own SOPs and claims drafts. Buy Now is the packaged zip: eight skills, the plugin files, and the install so you do not have to wire it from scratch.
This is the AI companion to the Complete Restoration Operations Kit. A restoration owner attaches it to their own Claude. It interviews them, writes a company profile, and then the other skills speak that business.
What it is
AI edition ops kit — same bench, same four moves.
An 8-skill Claude plugin. Install it into Claude Code, the Claude Desktop app, or Cowork. 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, not a generic restoration voice.
You need any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.
The 8 skills
Eight skills on the bench — pick the one that matches the job.
restoration-setup. Say “Set up the kit.” Guided interview that customizes the whole kit. First run. The concierge.
job-intake-assistant. Say “We just got a water call.” New-loss intake, water Cat/Class classification, scope plus safety, a paste-ready job summary.
equipment-advisor. Say “How many air movers for this room?” Air-mover and dehu sizing, placement, and a monitoring plan.
sop-generator. Say “Write an SOP for mold containment.” A tailored SOP in your company’s voice. Any of the 17 core SOPs, or a new one.
claims-assistant. Say “Draft a follow-up to the adjuster.” Adjuster emails, supplement justifications, an aging-claims chase plan.
kpi-coach. Say “Here are my numbers this month.” Your 12 KPIs computed and trended. The biggest profit leak named, with fixes.
crew-onboarding-builder. Say “Onboard a new tech.” Role-based Week-1 / 30 / 60 / 90 plan plus an IICRC certification roadmap.
iicrc-protocol-lookup. Say “What does S500 say about Cat 3 water?” Plain-English pointer to S500 / S520 / S700 / S540 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.
How to install it yourself
Option A: plugin (recommended)
Save the restoration-kit folder anywhere on your computer.
Replace the path with wherever you saved the folder. On Desktop and Cowork, add the plugin from Customize → Plugins instead; the /plugin commands are for Claude Code.
Start setup:
/restoration-kit:restoration-setup
Option B: personal skills (simplest, no plugin)
Copy each folder inside skills/ into your personal skills folder at ~/.claude/skills/. On Windows that is C:\Users\<you>\.claude\skills\. Then tell Claude: “run restoration setup.”
First run
Run restoration-setup first. It asks about your company for about five minutes. It saves a company-profile.md. Then it offers to customize each skill: generate your first SOPs, set KPI targets, draft a sample adjuster email.
Keep that company-profile.md in the folder you work in. Every skill reads it so the answers sound like your shop.
Using it day to day
Same four moves day to day. Less reinventing at 11pm.
You do not need to memorize skill names. Just talk.
“We just got a fire call on Oak St” → intake
“Size the equipment for a 15×20 Class 3” → equipment
“Draft a supplement justification for the Alvarez claim” → claims
“Build an onboarding plan for a new crew chief” → onboarding
“What PPE for Condition 3 mold?” → IICRC lookup
Optional: put it on a routine. Ask Claude, “Schedule a weekly KPI review every Monday at 8am.” It walks you through a recurring run of the KPI coach.
What the 12 KPIs are
When you feed the KPI coach real numbers, these are the twelve the kit is built around:
Revenue, Gross Margin %, Net Profit %, Days Sales Outstanding, Average Job Size
Lead-to-Job Conversion %, Jobs Sold
Average Days to Dry
Labor Efficiency %, Equipment Utilization %
Rework / Callback %, Customer Satisfaction (NPS)
Starting targets in the kit: gross margin ≥ 45%, net ≥ 12%, DSO ≤ 45 days, conversion ≥ 35%, days to dry ≤ 3.5, labor efficiency ≥ 70%, equipment utilization ≥ 60%, callbacks ≤ 3%, NPS ≥ 70. Use them as a case file, then set yours.
What the zip actually contains
.claude-plugin/plugin.json and marketplace.json
skills/ (the 8 skills)
README.md with the full install
Outputs from each skill are formatted to paste into the matching Notion template in the Complete Restoration Operations Kit. The Notion side is the system of record (jobs, equipment, claims, KPIs). These skills help you fill and act on them.
This is an operational assistant only. Not legal, insurance, or licensing advice.
If you want the packaged install
You can rebuild this from the outline above. Buy Now is the zip delivered by email after checkout: plugin files, the eight skills, and the README so you drop it in and run setup. Same Square button at the top of this page.
Frequently Asked Questions
Is there a refund policy?
Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. You will receive your download link — Notion duplicate link, skill file, or both depending on the product.
