vrio
Skill1 starsChanged 5 months agoMITView on GitHub
Use when analyzing whether a company's or project's resources and capabilities generate sustained competitive advantage — running a VRIO breakdown. Triggers on "VRIO", "competitive advantage", "sustained advantage", "resource analysis", "can competitors copy this", or assessing why a firm wins or loses in its market.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- teodstr/boardroomtheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- teodstr/boardroom★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Own project: read repo (README, docs, commits) and propose a candidate resource list by category.
- Distinctive: line 23
If no repo exists (e.g. a business idea), treat as external.
- Distinctive: line 24
External company: ask what the user knows. Do NOT invent financials or facts — flag all assumptions explicitly.
- Distinctive: line 26
User-supplied list: if the user has already provided resources/capabilities, skip to Step 3.
- Distinctive: line 46
Every cell must have "Yes — <rationale>" or "No — <rationale>".
- Distinctive: line 109
Keep it concise — this is an explainer, not a full mapping.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
VRIO Analysis
REQUIRED FIRST OUTPUT — no exceptions: Your very first words to the user must be: "Using the VRIO skill." Say this before any analysis, research, or tool calls produce visible output.
Apply the VRIO framework (Barney, 1991) to determine which resources and capabilities generate competitive advantage — for an external company or one of the user's own software/product projects.
Complements porters-value-chain: Value Chain maps where activities create
value; VRIO assesses which resources drive advantage.
How to run an analysis
Step 1 — Identify the target
- Own project: read repo (README, docs, commits) and propose a candidate resource list by category. Confirm with the user before scoring. If no repo exists (e.g. a business idea), treat as external.
- External company: ask what the user knows. Do NOT invent financials or facts — flag all assumptions explicitly.
- User-supplied list: if the user has already provided resources/capabilities, skip to Step 3.
Step 2 — Elicit resources/capabilities
Work through the four resource types one at a time, asking 1-2 prompting
questions each. See references/resource-categories.md for the full question
bank.
Resource types: Physical, Human, Financial, Organizational/Intangible
Confirm the final list with the user before scoring.
Step 3 — VRIO table
Produce a Markdown table with one row per resource/capability:
| Resource/Capability | Valuable? | Rare? | Costly to Imitate? | Organized? | Competitive Implication |
- Every cell must have "Yes —
<rationale>" or "No —<rationale>". - For "Costly to Imitate?", consult
references/imitation-barriers.mdand name the applicable condition (path dependency, causal ambiguity, or social complexity). - Derive competitive implication from this filter — use these exact labels:
| V | R | I | O | Implication |
| No | — | — | — | Competitive Disadvantage |
| Yes | No | — | — | Competitive Parity |
| Yes | Yes | No | — | Temporary Competitive Advantage |
| Yes | Yes | Yes | No | Unexploited Competitive Advantage |
| Yes | Yes | Yes | Yes | Sustained Competitive Advantage |
Step 4 — Funnel diagram
Draw the VRIO filter as sequential gates. Annotate each exit with the resource(s) that drop off there.
All Resources/Capabilities
│
┌────▼─────┐
│ Valuable? │──No──→ Competitive Disadvantage [Resource X]
└────┬─────┘
│ Yes
┌────▼──────┐
│ Rare? │──No──→ Competitive Parity [Resource Y]
└────┬──────┘
│ Yes
┌────▼──────────────┐
│ Costly to Imitate? │──No──→ Temporary Competitive Advantage [Resource Z]
└────┬──────────────┘
│ Yes
┌────▼───────────────────┐
│ Organized to Exploit? │──No──→ Unexploited Competitive Advantage [Resource W]
└────┬───────────────────┘
│ Yes
══ Sustained Competitive Advantage ══ [Resource V]Step 5 — Strategic synthesis
Identify the 2-3 resources most worth acting on:
- Sustained/Unexploited advantages → protect or activate them
- Competitive Disadvantage/Parity in important areas → close the gap
For each: one-line rationale + concrete, prioritized next action. Never skip this step — it is the payoff of the analysis.
Deliverable
Print table + diagram + synthesis in chat by default. Then offer to save as
docs/strategy/<target>-vrio.md. Save only if the user agrees.
Teaching mode
Triggered when user asks "explain VRIO", "what is VRIO", or similar — not requesting an analysis:
- Explain the four dimensions (V, R, I, O) and the competitive implication ladder
- Walk one short worked example through 2-3 resources of a real company
- Offer to run a full analysis next
Keep it concise — this is an explainer, not a full mapping.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

