Why This Matters More Than AGI
I'm going to say something controversial.
Skills matter more than model improvements.
Here's why.
Model improvements are logarithmic. Each generation gets marginally better at general tasks. The difference between GPT-3 and GPT-4 is smaller than the difference between having a workflow and not having one.
Skills are multiplicative. A 10% better model running a mediocre workflow produces mediocre results. An 80% as good model running an optimized workflow produces better results.
I've tested this. Extensively.
A Claude 2.1 skill I built for technical documentation outperforms Claude 3.5 Sonnet used ad-hoc. By a significant margin. Not because the model is better—it's objectively worse—but because the skill encodes everything that makes documentation good:
- Structure that readers expect
- Terminology consistency
- Examples at the right density
- Progressive disclosure of complexity
The model follows the rails. The rails do the work.
The Anatomy of a Skill That Works
Most skills fail. I've reviewed hundreds from the community. Here's what separates the ones that transform workflows from the ones that get abandoned after a week.
Layer 1: Context Loading
The skill starts with context injection—not just "what to do" but who you are, what you've tried, what failed before.
---
name: strategic-planner
description: Strategic planning with OKR methodology
---
## Context
- Company stage: Series B, 47 employees
- Previous frameworks tried: V2MOM (too rigid), Rocks (too vague)
- CEO preference: Quantifiable outcomes, quarterly cadence
- Team weakness: Execution tracking, not ideation
This isn't configuration. This is institutional memory.
Layer 2: Methodology Encoding
Here's where most skills die. They describe what to produce. Good skills encode how to think.
## Methodology
### Step 1: Constraint Identification
Before generating objectives, identify constraints that make
generic advice dangerous:
- Budget boundaries
- Regulatory requirements
- Technical debt limitations
- Team capability gaps
### Step 2: Objective Generation
Generate 3-5 objectives that satisfy the constraint filter.
Each objective must answer: "If we achieve nothing else this
quarter, achieving THIS would make the quarter successful."
Do NOT generate objectives that:
- Cannot be measured
- Depend on external factors we don't control
- Conflict with existing commitments
See the difference? This isn't "create objectives." This is a decision tree that produces objectives worth having.
Layer 3: Output Templating
Consistency matters more than creativity for operational tasks.
## Output Format
### Objective Template
**[O1]: [Objective Name]**
*Why this matters:* [1-sentence justification]
*Success looks like:* [Observable outcome]
*Risk if we fail:* [Specific consequence]
**Key Results:**
| KR | Target | Current | Gap | Owner |
|----|--------|---------|-----|-------|
Every output looks the same. Every output can be compared. Every output feeds the same downstream processes.
The Skill Stack Architecture
Here's what nobody's building yet, but will become standard within 18 months.
Skills don't exist in isolation. They stack.
Base Layer Skills:
- Context loaders (company info, team structure, technical stack)
- Format enforcers (brand voice, document templates)
- Validation checks (compliance, accuracy, consistency)
Domain Layer Skills:
- Industry-specific analysis frameworks
- Regulatory requirement checkers
- Competitive intelligence templates
Execution Layer Skills:
- Meeting summarizers that feed OKR skills
- Email writers that reference strategy documents
- Report generators that pull from multiple base skills
When I run my "Quarterly Planning" skill, it automatically:
- Loads company context from the context skill
- Pulls in current OKRs from the OKR skill
- Applies my planning methodology from the strategy skill
- Outputs in my preferred format from the template skill
- Validates against my constraints from the compliance skill
Five skills. One command. Fifteen minutes of work that used to take three days.
The Operational Breakthrough
Let me show you something I built that changed how I think about work.
The Scenario Planner Skill
Most scenario planning is garbage. You brainstorm possibilities, rank them by likelihood, then forget about them until reality picks the one you ranked least likely.
I built a skill that actually works:
## Scenario Generation Protocol
### Phase 1: Driver Identification
Identify the 2-3 factors that would MOST change our situation:
- What external force could 2x our growth or kill it?
- What competitor action would force immediate response?
- What regulatory change would reshape the market?
### Phase 2: Extreme Scenario Construction
For each driver, construct the MOST EXTREME plausible version:
- Don't model "regulation might tighten"
- Model "regulation bans our primary revenue stream in 90 days"
Why extreme? Because extreme reveals dependencies. Moderate
scenarios feel like the present with minor adjustments.
Extreme scenarios reveal which assumptions you're not
questioning.
### Phase 3: The Survivability Test
For each extreme scenario, answer:
- How long could we survive in this scenario?
- What would we need to do in week 1?
- What capability don't we have that we'd need?
### Phase 4: Pre-Commitment Extraction
The insight isn't the scenario. It's the PRE-COMMITMENT.
A pre-commitment is: "If we observe [early signal], we will
[specific action] within [timeframe]."
Most planning fails because decisions happen after the signal,
when emotions are high and time is short. Pre-commitments
move the decision to right now, when we're calm and have context.
This skill doesn't just generate scenarios. It generates decisions made in advance.
That's the difference between planning and preparation.
What This Means for Builders
If you're building AI products, you're probably doing it wrong.
The pattern I see: companies building monolithic AI applications. One interface. One workflow. One way to use it.
That's the old model. That's building a restaurant where every dish uses the same recipe.
The new model: build skill libraries.
Your AI product isn't a product. It's a platform for skills.
The marketplace opportunity:
- Industry-specific skill packs ($500-5000/year)
- Integration skills (connect Salesforce + HubSpot + your CRM)
- Compliance skill libraries (HIPAA, SOC2, GDPR workflows)
- Vertical skill stacks (entire operational systems for specific industries)
The companies that figure this out first will own the operational AI market.
The 30-Day Skill Building Protocol
Here's how to start. Tomorrow. Not next quarter.
Week 1: Audit
- What do you do repeatedly that requires context transfer?
- What tasks produce inconsistent outputs?
- Where do you explain the same thing multiple times?
Week 2: Document
- Write down your actual methodology (not the official one—the real one)
- Capture the implicit knowledge you don't think to share
- Note the constraints that make generic approaches fail
Week 3: Encode
- Build your first skill using the three-layer architecture
- Test it against real work, not toy examples
- Iterate based on what's missing
Week 4: Stack
- Identify which skills could feed others
- Build the context layer that multiple skills share
- Create your first multi-skill workflow
By day 30, you'll have a system that didn't exist 30 days ago. You'll wonder how you worked without it.
The Question That Should Haunt You
Here's what I keep thinking about.
The best skills aren't the ones that automate what you do now. They're the ones that let you do what you couldn't do before.
I couldn't do real scenario planning. Not because I lacked the intelligence—because I lacked the time. Now I can.
I couldn't maintain strategic context across dozens of decisions. Now I can.
I couldn't ensure consistent methodology across my team. Now I can.
The question isn't "what tasks can I automate?"
The question is "what became possible that wasn't before?"
That's where the leverage lives.
That's where the future is being built.
And most people are still trying to make the chatbot write better emails.
The Skills documentation is decent. The community skills are hit-or-miss. But the architecture is sound. Start building.
Comments · 0
Beta: comments are stored locally on your device and not visible to other readers.
No comments yet. Be the first to share your thoughts.