write-docs

Generate BrowserOS feature MDX docs from source code and screenshots.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Srajangpt1/dataeye --skill write-docs-srajangpt1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-docs
Source: https://github.com/Srajangpt1/dataeye/tree/main/.claude/skills/write-docs
Command: npx skills add https://github.com/Srajangpt1/dataeye --skill write-docs-srajangpt1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of creating clear, one-page Mintlify MDX documentation for BrowserOS features by guiding code exploration, screenshot capture, file creation, and navigation updates so engineers and writers can ship docs quickly and consistently.

Core Features & Use Cases

  • Code-driven discovery: Search the sibling ../browseros-server codebase to identify feature entry points, configuration, and usage patterns.
  • Screenshot collection: Guide users to capture UI screenshots and persist them into docs/images for visual documentation.
  • MDX authoring with template: Produce concise docs/features/<feature>.mdx pages following a strict one-page template and style guide.
  • Navigation and preview: Update docs/docs.json navigation and instruct how to preview changes with the Mintlify dev server.
  • Use case: Documenting the MCP server, agent integrations, or scheduled tasks by combining source references and UI captures into a single helpful page.

Quick Start

Write a one-page Mintlify MDX feature doc for "Ad Blocking" by scanning ../browseros-server for implementation files, saving two screenshots to docs/images/ad-blocking.png, creating docs/features/ad-blocking.mdx using the provided template, and updating docs/docs.json so you can preview with mint dev.

Frequently Asked Questions about write-docs

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

FAQPage Schema
How do I generate Mintlify MDX documentation from source code?▼

Write concise MDX feature docs by performing code search on ../browseros-server, gathering UI screenshots into docs/images, creating docs/features/<feature>.mdx files, and updating docs/docs.json navigation for mint dev previewing.

What is the best way to document BrowserOS features like MCP server or scheduled tasks?▼

Document BrowserOS components by scanning source code for implementation details, capturing screenshots, and producing one-page Mintlify MDX files that consistently explain feature intent and usage for MCP servers or agent integrations.

How do I update Mintlify navigation to preview new feature docs with mint dev?▼

Preview new feature docs by updating docs/docs.json navigation entries to include the generated MDX file, then run the Mintlify dev server to validate the page renders correctly within the site structure.

Do I need UI screenshots to write BrowserOS feature documentation?▼

You need UI screenshots to write BrowserOS feature documentation because the workflow requires capturing visual elements and saving them to docs/images to supplement code-driven discovery in the final MDX page.

Can I use this approach to document any component in the browseros-server codebase?▼

This approach applies to any BrowserOS component with source code under ../browseros-server, allowing you to document MCP servers, agent integrations, and scheduled tasks by extracting implementation details into a concise MDX page.

Why does my Mintlify MDX feature doc need a strict one-page template?▼

The strict one-page template ensures feature documentation stays concise and consistent across different BrowserOS components, preventing formatting drift and helping readers find implementation details and usage patterns quickly.