Our review
Provides deep context from Ryan's actual writings on technical topics such as OpenPKG, agent-native architecture, and documentation coverage.
Strengths
- Synthesizes Ryan's perspective across multiple posts
- Quotes specific points to add credibility
- Uses a conversational and accessible tone
- Covers targeted technical topics with depth
Limitations
- Only works for topics Ryan has written about
- Requires the MDX files to be present for reading
- May not reflect recent developments if posts are outdated
When you need to discuss or explain technical concepts that Ryan has covered in his blog posts.
For topics outside Ryan's writings or when you need up-to-date information not covered in his posts.
Security analysis
SafeThe skill only reads local MDX files and synthesizes information; it does not perform any code execution, network activity, or destructive operations. No risk of exfiltration or system compromise.
No concerns found
Examples
What is OpenPKG based on Ryan's writings? Summarize his perspective and key insights.How does Ryan think about agent-native design? Synthesize his views from the relevant post.Tell me about doccov and what Ryan found about documentation coverage in his post.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.