docs-writing

Write, edit, and review Unkey technical documentation in Markdown and MDX.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RiemaLabs/unkey --skill docs-writing-riemalabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-writing
Source: https://github.com/RiemaLabs/unkey/tree/main/.agents/skills/writing-documentation
Command: npx skills add https://github.com/RiemaLabs/unkey --skill docs-writing-riemalabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill assists in creating, refining, and ensuring the quality of technical documentation for the Unkey platform, adhering to established style guides and best practices.

Core Features & Use Cases

  • Content Creation: Draft new documentation pages for features, guides, or troubleshooting.
  • Editing & Review: Improve existing content for clarity, accuracy, and adherence to Unkey's voice and tone.
  • Formatting & Structure: Ensure correct Markdown, component usage, and adherence to content patterns.
  • Use Case: You need to write a new guide on deploying Unkey using Docker Compose, ensuring it follows the specified structure and voice.

Quick Start

Use the docs-writing skill to draft a new section for the Unkey product documentation about API key rotation.

Frequently Asked Questions about docs-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write technical documentation for the Unkey platform?

To write Unkey technical documentation, you need to draft content using Markdown and MDX while adhering to established voice, tone, and formatting guidelines for accuracy and structure.

What is the best way to structure a new Unkey product guide using Markdown?

The best way to structure a new Unkey product guide is to follow specific content patterns and component usage guidelines in Markdown, ensuring the documentation maintains clarity and adheres to the platform's voice.

How do I edit existing MDX documentation to match Unkey's voice and tone?

To edit existing MDX documentation for Unkey, you review the content to improve clarity, verify technical accuracy, and adjust the formatting to strictly match the required voice and tone guidelines.

Can I use this approach to draft a deployment guide for Unkey using Docker Compose?

Yes, you can use this documentation approach to draft a deployment guide for Unkey using Docker Compose, as it supports creating new troubleshooting and feature pages that follow specified structures.

Does writing Unkey documentation require understanding of specific content patterns?

Yes, writing Unkey documentation requires an understanding of specific content patterns, Markdown, MDX, and the platform's formatting guidelines to ensure the accuracy and structure of the technical content.