Proven Fix to Reusable Skill
Turn a solved problem into a standalone SKILL.md with precise triggers, diagnostic branches, and a worked example.
Before & after
Same prompt, same agent — the only difference is the skill.
That's a good idea to package up your authentication pattern for reuse. You'd want to document how it works, provide some code examples, and maybe make a reference guide. I could help you write documentation, but you'd need to think about how to structure it so other people can understand and use it. You might also want to include some examples showing how to integrate it into a new project. What specific parts of your authentication pattern do you want to highlight?
SKILL EXTRACTION OUTPUT: Custom Auth Pattern
FILE STRUCTURE
skill/
SKILL.md (1500 words)
reference/
API.md (endpoint specs, auth headers)
CONFIG.md (environment variables required)
EXAMPLES.md (3 real integration examples)
TROUBLESHOOTING.md (common errors, fixes)
templates/
middleware-jwt.ts (copy-paste middleware)
protected-api-route.ts (API example)
protected-component.tsx (React example)
SKILL.md OUTLINE
1. What it does (42-char headline)
2. When to use it (3 scenarios)
3. Setup in 5 steps (code blocks)
4. Advanced: rotation policy, token refresh, role-based access
5. Gotchas: clock skew in Docker, token size limits on headers
REFERENCE/API.md EXAMPLE
POST /auth/login
Request: { email, password }
Response: { access_token, refresh_token, expires_in: 3600 }
Headers: Content-Type: application/json
GET /auth/verify
Headers: Authorization: Bearer {access_token}
Response: { user_id, roles, exp }
EXAMPLES/INTEGRATION.md
Example 1: Express middleware setup
Example 2: Next.js API route protection
Example 3: React hook for token refresh
Each includes error handling and test assertions
TROUBLESHOOTING.md
Issue: "Invalid token signature in staging"
Cause: Different SIGNING_KEY between environments
Fix: Verify .env.staging has matching key
Issue: "Token expired immediately"
Cause: Server clock drift (Docker)
Fix: Run `ntpd` or use serverless timestamp service
Deliverable: skill.zip (ready to upload to agent marketplace)About this skill
You solved the problem, but the diagnostic steps are buried in a chat and the next attempt starts from memory. Turn that hard-won fix into a standalone SKILL.md that recognizes the right symptoms, distinguishes lookalike failures, and explains how to verify recovery.
What it does
- Separates the reusable mechanism from project names, temporary values, and incidental troubleshooting.
- Captures error signatures, prerequisites, decisive checks, and evidence that the fix worked.
- Converts a successful sequence into diagnostic branches with explicit stop conditions.
- Preserves necessary commands and examples inline while removing credentials and unsafe defaults.
- Checks trigger wording against a nearby variant, a lookalike failure, and an out-of-scope request.
- Identifies overlap with supplied skills so the result has a clear purpose.
What you get
A complete, copyable SKILL.md containing recognition cues, an executable decision process, verification criteria, and a worked example. Unproven assumptions and unexecuted checks are labeled explicitly.
Best for
Developers and technical teams capturing recurring debugging fixes, successful implementation patterns, and operational knowledge from completed work.
SKILL.md preview
---
name: proven-fix-to-reusable-skill
description: >-
Turn an existing debugging fix or successful engineering pattern into a standalone SKILL.md by extracting its causal mechanism, recognition cues, diagnostic branches, verification criteria, and worked example. Use when the user says "turn this fix into a skill", "extract a skill from this conversation", "package this debugging solution", "we keep solving this from scratch", "this fix is buried in chat", "capture this pattern for next time", or "/si:extract".
---
# Proven Fix to Reusable Skill
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.