moatmri
Analyze AI disruption pressure across a business, map competitive exposure, and produce a 90-day defensive action plan.
Best use case
moatmri is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze AI disruption pressure across a business, map competitive exposure, and produce a 90-day defensive action plan.
Teams using moatmri should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/moatmri/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How moatmri Compares
| Feature / Agent | moatmri | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze AI disruption pressure across a business, map competitive exposure, and produce a 90-day defensive action plan.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# MoatMRI — AI Disruption Pressure Analysis *Where does intelligence pressure break this system first?* ## When to Use This Skill - "Is my business at risk from AI? Where am I most exposed?" - "How would an AI-native startup take over my market?" - "What should I do in the next 90 days to defend against AI disruption?" - "I'm doing due diligence on [company] — what's their AI displacement risk?" - "Where does my competitive moat actually hold against AI pressure?" ## How It Works ### Step 1 — Gather Inputs Ask if not provided: - **Industry** (e.g., "real estate", "community banking", "retail pharmacy", "law firm") - **Entity type** (e.g., "independent broker", "solo practitioner", "regional franchise") - **Target name** (optional — specific organization for named analysis) ## Limitations - Produces strategic risk analysis, not audited market research or investment advice. - Depends on current company, market, regulatory, and competitive context supplied by the user or gathered from reliable sources. - Treats disruption scenarios as planning tools; scores should be revisited as new evidence appears. ### Step 2 — 10-Vector Pressure Map Score AI disruption pressure across exactly these 10 vectors (0–10): | # | Vector | What to Measure | |---|--------|----------------| | 1 | **labor_substitution** | Which roles/functions are directly automatable | | 2 | **customer_interface** | How AI changes how customers reach this entity | | 3 | **knowledge_commoditization** | Does AI commoditize the expertise this entity sells | | 4 | **pricing_pressure** | Does AI enable lower-cost competitors to undercut | | 5 | **supply_chain_automation** | Does AI change input costs or supplier relationships | | 6 | **data_moat** | Does this entity have proprietary data AI can't replicate | | 7 | **trust_relationship_moat** | How much does customer loyalty protect against displacement | | 8 | **distribution_channel_disruption** | Does AI create new channels that bypass this entity | | 9 | **regulatory_compliance_exposure** | Does AI alter the regulatory or liability landscape | | 10 | **decision_speed_gap** | Does AI accelerate decisions in ways that disadvantage this entity | For each vector produce: **score**, **headline**, **near_term** (12 months), **far_term** (3 years). **Aggregate risk score:** mean of all 10 vectors. Flag any vector ≥ 7 as critical. ### Step 3 — AI Front-Door Takeover Storyboard 6-step narrative of how an AI-native competitor displaces this entity: 1. The entry point 2. The wedge (first 10% of market) 3. The acceleration (what makes it compound) 4. The tipping point (when incumbent can't recover) 5. The aftermath 6. The survivor profile ### Step 4 — 90-Day Counterstrike Plan - **Track A (Days 0–30):** Immediate defense — what to stop, what to protect - **Track B (Days 31–60):** Intelligence-layer build — data/relationships to fortify - **Track C (Days 61–90):** Offensive positioning — use AI pressure as competitive weapon ## Best Practices - ✅ Score all 10 vectors before calculating aggregate — resist stopping at obvious ones - ✅ Keep the storyboard specific to industry/entity, not generic disruption narrative - ✅ Track C should be actionable within 90 days, not aspirational 3-year strategy - ❌ Don't conflate data_moat with trust_relationship_moat — they protect differently ## Additional Resources - Repository: [thebrierfox/moatmri-skill](https://github.com/thebrierfox/moatmri-skill) - Full BYOK tool: [ace-license-server-production.up.railway.app/byok/moatmri](https://ace-license-server-production.up.railway.app/byok/moatmri) - Built by [IntuiTek¹](https://intuitek.ai) (~K¹) — MIT License
Related Skills
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
zipai-optimizer
Ultra-dense token optimizer skill for prompt caching, log pruning, AST-based inspection, and minified JSON payloads.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.
zapier-make-patterns
No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.
youtube-summarizer
Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks
youtube-full
Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.
youtube-automation
Automate YouTube tasks via Rube MCP (Composio): upload videos, manage playlists, search content, get analytics, and handle comments. Always search tools first for current schemas.
yield-intelligence
Passive income portfolio analysis — activate when user asks about dividend yields, Treasury rates, REIT income, monthly passive income goals, or portfolio yield optimization. Scans 4 asset classes, ranks by risk-adjusted return, and builds allocations targeting a specific monthly income.