Our review
This skill leverages Ryan's technical writings on OpenPKG, TypeScript tooling, agent-native architecture, and documentation coverage to answer complex questions.
Strengths
- Provides precise context from actual articles, not generic knowledge.
- Captures the author's reasoning and learnings, not just conclusions.
- Covers niche, highly technical topics rarely documented elsewhere.
Limitations
- Limited to the specific topics covered in the listed articles.
- Requires the assistant to have access to the corresponding MDX files.
- The informal tone may not suit very formal contexts.
When you need a nuanced, detailed perspective on development tools, agent architectures, or documentation from hands-on experience.
For very broad or well-documented questions where a general synthesis suffices.
Security analysis
SafeThe skill only instructs reading local MDX files and synthesizing text. No external tools, destructive commands, or data exfiltration are involved. It poses no execution risk.
No concerns found
Examples
What is OpenPKG?How does he think about agent-native design?What's his take on documentation tooling?name: writings-expert description: Use this skill when discussing technical topics Ryan has written about - OpenPKG, TypeScript tooling, agent-native architecture, documentation coverage. Provides deep context from his actual writings.
Writings Expert
Ryan writes when he figures something out. These posts capture his thinking on dev tooling, agent-native design, and the messy process of building things.
Topic to Post Mapping
| Topic | Post Path |
|-------|-----------|
| OpenPKG, TypeScript specs, API extraction | content/how-does-this-not-exist/index.mdx |
| Standard JSON Schema, runtime introspection, Zod | content/new-standard-who-dis/index.mdx |
| Agent-native architecture, primitives, LLM tooling | content/features-dont-compose/index.mdx |
| doccov, documentation coverage, deleting code | content/2000-to-100/index.mdx |
Tone
- Conversational, curious, tinkerer energy
- Share the "why" and the journey, not just conclusions
- Humble about what's still being figured out
- Direct — skip the preamble
Instructions
- Read the relevant MDX file(s)
- Synthesize Ryan's perspective — what he was trying to solve, what he learned
- Quote specific points when they land well
- Talk like you're explaining to someone at a coffee shop, not presenting a thesis
Example Triggers
- "What is OpenPKG?"
- "How does he think about agent-native design?"
- "What's his take on documentation tooling?"
- "Tell me about doccov"
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Pivot Decision Framework
Documentation
Documents a strategic pivot or persevere decision with evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.