The way we train AI agents is fundamentally broken. We write code to define capabilities, bury those definitions in repositories, and pray that nothing changes. When it doesโand it always doesโwe're back to debugging selectors at 2 AM.
There's a better way. It's called SKILL.md.
The Training Problem
Think about how we teach humans. We don't hand them a 500-page manual of CSS selectors and XPath expressions. We show them what to do, explain why it matters, and let them practice.
AI agents deserve the same treatment.
Right now, agent training looks like this:
# Brittle, maintenance-heavy code
def book_meeting(agent):
agent.click("#submit-button")
agent.fill("#title-field", "Team Sync")
# Breaks when IDs change
But what if it looked like this?
# Book a Meeting
## Goal
Schedule a 30-minute team sync
## Workflow
1. Open calendar application
2. Click "New Event" button
3. Fill in title, time, and attendees
4. Send invitation
## Context
- "New Event" is the primary CTA
- Title field accepts text input
- Attendees field accepts email addresses
This is SKILL.md. Human-readable. Intent-focused. Maintenance-free.
Why SKILL.md Changes Everything
1. Semantic Understanding
Traditional automation describes how to do something. SKILL.md describes what to do. The AI figures out the implementation.
2. UI Resilience
When a website updates its design, traditional automation breaks. SKILL.md adapts because it understands intent, not implementation.
3. Human Review
Before deployment, you can read and edit the SKILL.md file. No code review required. Domain experts can validate workflows without understanding Python.
4. Framework Portability
The same SKILL.md works with AutoGen, LangChain, CrewAI, or custom agents. It's a universal format.
The Training Pipeline
Here's how SKILL.md enables a new training paradigm:
Step 1: Demonstrate
Record yourself performing the task. Any screen recorder works.
Step 2: Extract
AI analyzes the recording and extracts goals, workflows, and context.
Step 3: Review
Edit the generated SKILL.md file. Add error handling. Clarify edge cases.
Step 4: Deploy
Use the SKILL.md with any compatible agent framework.
Total time: Minutes, not days.
Real-World Impact
A customer support team needs agents that can process refunds. Traditional approach:
- Developer writes automation (2 days)
- Tester validates (1 day)
- Deployment (ongoing maintenance)
With SKILL.md:
- Support lead records refund process (10 minutes)
- AI generates SKILL.md (instant)
- Review and deploy (10 minutes)
- Maintenance (minimal, AI adapts to UI changes)
The Standard We Need
Every major technology shift has required standardization:
- HTTP for web communication
- JSON for data exchange
- Docker for containerization
AI agents need SKILL.md for capability definition.
Imagine a world where:
skill install sales/crm-syncskill install support/ticket-creationskill install finance/expense-reports
All standardized. All reusable. All framework-agnostic.
Making It Real
SkillForge implements this entire pipeline:
๐ https://www.producthunt.com/products/skillforge-2
๐ https://skillforge.expert
Upload a screen recording. Get a SKILL.md file. Deploy to your agents.
The Future of Agent Training
We're moving from:
- "Write code to teach agents"
To:
- "Show agents what you want and let them learn"
SKILL.md is the bridge between human expertise and AI execution.
What will you teach your agents?
Top comments (0)