Agent skill

API Documentation Writer

by FerroxLabs in FerroxLabs/wayland

API documentation expertise covering OpenAPI specification authoring, endpoint documentation patterns, code examples in multiple languages, authentication guides, quickstart tutorials, SDK…

Apache-2.0Auto-check passedDevelopment

Install API Documentation Writer

skills CLI
$ npx skills add FerroxLabs/wayland --skill api-documentation-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland api-documentation-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/writing/api-documentation-writer .claude/skills/api-documentation-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
api-documentation-writer
GitHub stars
608
Token cost
~4k tokens
SKILL.md length
285 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

API documentation expertise covering OpenAPI specification authoring, endpoint documentation patterns, code examples in multiple languages, authentication guides, quickstart tutorials, SDK…

  • The user asks about api documentation writer
  • SKILL.md covers Overview, Documentation Architecture, OpenAPI Specification and Code Examples, plus 7 more sections
  • Needs INVALID_API_KEY
  • Api documentation writer best practices

What it does

API Documentation Writer is an agent skill from FerroxLabs/wayland. API documentation expertise covering OpenAPI specification authoring, endpoint documentation patterns, code examples in multiple languages, authentication guides, quickstart tutorials, SDK documentation, error reference guides, versioning strategies, interactive documentation portals, and developer experience optimization. Use when the user asks about api documentation writer, api documentation writer best practices, or needs guidance on api documentation writer implementation. Do NOT use when the user needs a…

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Technical documentation and OpenAPI specifications. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about api documentation writer
  • Api documentation writer best practices
  • Needs guidance on api documentation writer implementation
  • The user needs a different specialized skill

Example prompts

  • “/api-documentation-writer”

Requirements

  • Python 3
  • Node.js
  • A credential in INVALID_API_KEY

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, markdown, python and javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • INVALID_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

API Documentation Writer loads about 4k tokens when it runs. Until then it costs about 155 tokens; SKILL.md has 285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~155
When it runs · the whole SKILL.md, loaded when a task matches
~4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 285 words, ~4,008 tokens.

Download SKILL.mdSave it as .claude/skills/api-documentation-writer/SKILL.md (or your agent's skills folder).
name
api-documentation-writer
description
API documentation expertise covering OpenAPI specification authoring, endpoint documentation patterns, code examples in multiple languages, authentication guides, quickstart tutorials, SDK documentation, error reference guides, versioning strategies, interactive documentation portals, and developer experience optimization. Use when the user asks about api documentation writer, api documentation writer best practices, or needs guidance on api documentation writer implementation. Do NOT use when the user needs a different specialized skill or is asking about an unrelated technology domain.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
technical-writing documentation api-design
metadata.category
writing
metadata.subcategory
technical-writing
metadata.disclaimer
none
metadata.difficulty
beginner

API Documentation Writer

Overview

API documentation is the primary interface between your API and its consumers. Great API docs reduce support burden, accelerate integration, and build developer trust. This skill covers writing clear, complete, and developer-friendly API documentation from OpenAPI specifications through quickstart guides, code examples, authentication tutorials, and error references.

Documentation Architecture

API Documentation Site
|
+-- Getting Started
|   +-- Quickstart (5-minute integration)
|   +-- Authentication Guide
|   +-- Rate Limits & Quotas
|   +-- Environments (sandbox, production)
|
+-- API Reference (auto-generated from OpenAPI)
|   +-- Endpoints grouped by resource
|   +-- Request/response schemas
|   +-- Code examples per endpoint
|   +-- Try-it-out console
|
+-- Guides
|   +-- Common Workflows
|   +-- Webhooks Integration
|   +-- Pagination Patterns
|   +-- Error Handling
|   +-- Migration Guides (v1 -> v2)
|
+-- SDKs & Libraries
|   +-- Installation
|   +-- Configuration
|   +-- Usage Examples
|   +-- Changelog
|
+-- Reference
|   +-- Error Codes
|   +-- Status Codes
|   +-- Glossary
|   +-- Changelog / Release Notes

OpenAPI Specification

Well-Documented OpenAPI Spec
yaml
openapi: 3.1.0
info:
  title: Orders API
  version: 2.1.0
  description: |
    The Orders API lets you create, get, update, and manage customer orders.

    ## Authentication
    All endpoints require a Bearer token. See [Authentication Guide](/docs/auth).

    ## Rate Limits
    - Standard: 100 requests/minute
    - Bulk endpoints: 10 requests/minute

    ## Versioning
    Include `API-Version: 2024-01-15` header. See [Versioning](/docs/versioning).
  contact:
    name: API Support
    email: api-support@company.com
    url: [reference URL]

servers:
  - url: [reference URL]
    description: Production
  - url: [reference URL]
    description: Sandbox (test data, no real charges)

tags:
  - name: Orders
    description: |
      Create and manage customer orders. Orders progress through states:
      `pending` -> `confirmed` -> `shipped` -> `delivered`.
      Orders can be `cancelled` before shipping.

paths:
  /orders:
    post:
      operationId: createOrder
      summary: Create an order
      description: |
        Creates a new order for the authenticated customer.

        **Important:** The order is created in `pending` status and must be
        confirmed within 30 minutes or it will be automatically cancelled.

        Requires the `orders:write` scope.
      tags: [Orders]
      security:
        - BearerAuth: [orders:write]
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateOrderRequest'
            examples:
              simple_order:
                summary: Simple single-item order
                value:
                  items:
                    - product_id: "prod_abc123"
                      quantity: 2
                  shipping_address:
                    line1: "123 Main St"
                    city: "San Francisco"
                    state: "CA"
                    postal_code: "94102"
                    country: "US"
              multi_item:
                summary: Multi-item order with discount
                value:
                  items:
                    - product_id: "prod_abc123"
                      quantity: 2
                    - product_id: "prod_def456"
                      quantity: 1
                  discount_code: "SAVE10"
                  shipping_address:
                    line1: "456 Oak Ave"
                    city: "Austin"
                    state: "TX"
                    postal_code: "73301"
                    country: "US"
                  metadata:
                    source: "mobile_app"
                    campaign: "summer_sale"
      responses:
        '201':
          description: Order created successfully
          headers:
            X-Request-Id:
              description: Unique request identifier for support
              schema:
                type: string
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Order'
              examples:
                created:
                  summary: Newly created order
                  value:
                    id: "ord_xyz789"
                    status: "pending"
                    items:
                      - product_id: "prod_abc123"
                        quantity: 2
                        unit_price: 29.99
                        total: 59.98
                    subtotal: 59.98
                    tax: 5.40
                    total: 65.38
                    created_at: "2024-06-15T10:30:00Z"
                    expires_at: "2024-06-15T11:00:00Z"
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '422':
          description: Validation error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationError'
              examples:
                invalid_product:
                  summary: Product not found
                  value:
                    error:
                      code: "INVALID_PRODUCT"
                      message: "Product 'prod_invalid' does not exist"
                      field: "items[0].product_id"
                out_of_stock:
                  summary: Product out of stock
                  value:
                    error:
                      code: "OUT_OF_STOCK"
                      message: "Product 'prod_abc123' has only 1 unit available"
                      field: "items[0].quantity"
                      metadata:
                        available_quantity: 1

components:
  schemas:
    Order:
      type: object
      description: Represents a customer order
      properties:
        id:
          type: string
          description: Unique order identifier
          example: "ord_xyz789"
          readOnly: true
        status:
          type: string
          description: |
            Current order status. Transitions:
            - `pending` -> `confirmed` (after payment)
            - `confirmed` -> `shipped` (after fulfillment)
            - `shipped` -> `delivered` (after delivery confirmation)
            - `pending|confirmed` -> `cancelled` (before shipping)
          enum: [pending, confirmed, shipped, delivered, cancelled]

Code Examples

Multi-Language Code Examples
# cURL
HTTP client request -X POST [reference URL] \
  -H "Authorization: Bearer sk_test_EXAMPLE_KEY_REPLACE_ME" \
  -H "Content-Type: application/json" \
  -H "API-Version: 2024-01-15" \
  -d '{
    "items": [
      {"product_id": "prod_abc123", "quantity": 2}
    ],
    "shipping_address": {
      "line1": "123 Main St",
      "city": "San Francisco",
      "state": "CA",
      "postal_code": "94102",
      "country": "US"
    }
  }'
python
# Python
import company_sdk

client = company_sdk.Client(api_key="sk_test_EXAMPLE_KEY_REPLACE_ME")

order = client.orders.create(
    items=[
        {"product_id": "prod_abc123", "quantity": 2}
    ],
    shipping_address={
        "line1": "123 Main St",
        "city": "San Francisco",
        "state": "CA",
        "postal_code": "94102",
        "country": "US",
    }
)

print(f"Order created: {order.id}")
print(f"Total: ${order.total}")
javascript
// Node.js
const Company = require('company-sdk');

const client = new Company('sk_test_EXAMPLE_KEY_REPLACE_ME');

const order = await client.orders.create({
  items: [
    { product_id: 'prod_abc123', quantity: 2 }
  ],
  shipping_address: {
    line1: '123 Main St',
    city: 'San Francisco',
    state: 'CA',
    postal_code: '94102',
    country: 'US',
  }
});

console.log(`Order created: ${order.id}`);
console.log(`Total: $${order.total}`);
Code Example Best Practices
DO:
  - Show complete, copy-paste-ready examples
  - Include error handling in examples
  - Use realistic (but fake) data
  - Show the response alongside the request
  - Include the SDK version in installation instructions
  - Highlight the key parameters with inline comments

DON'T:
  - Use real API keys; use clearly-marked test keys (e.g., sk_test_EXAMPLE_KEY_REPLACE_ME)
  - Show only the happy path (include error handling)
  - Assume SDK is already installed (show installation)
  - Use outdated SDK methods
  - Skip import/require statements

Quickstart Guide

Structure Template
markdown
# Quickstart: Create Your First Order

Get up and running with the Orders API in 5 minutes.

## Prerequisites
- A Company account ([sign up free]([reference URL]))
- An API key from [Dashboard > API Keys]([reference URL])

## Step 1: Install the SDK

Choose your language:

**Python** (requires Python 3.8+)
> install via pip: company-sdk

**Node.js** (requires Node 18+)
> install via npm: company-sdk

## Step 2: Make your first API call

[Code example: list products]

**Expected response:**
[Show formatted JSON response]

## Step 3: Create an order

[Code example: create order with error handling]

**Expected response:**
[Show the order object with status: "pending"]

## Step 4: Check order status

[Code example: get order by ID]

## Next Steps
- [Authentication Guide](/docs/auth) - Learn about API keys and OAuth
- [Webhooks](/docs/webhooks) - Get real-time order status updates
- [Full API Reference](/docs/api) - Explore all endpoints
- [Error Handling](/docs/errors) - Handle errors gracefully

Error Reference

Error Documentation Pattern
yaml
# Structured error documentation
error_categories:
  authentication:
    - code: INVALID_API_KEY
      http_status: 401
      message: "The API key provided is invalid or expired"
      causes:
        - "API key was deleted or rotated"
        - "Using test key against production endpoint"
        - "Key has been compromised and revoked"
      resolution: "Generate a new API key in Dashboard > API Keys"

    - code: INSUFFICIENT_SCOPE
      http_status: 403
      message: "Your token lacks the required scope for this endpoint"
      causes:
        - "OAuth token was not granted the needed scope"
      resolution: "Request additional scopes during OAuth authorization"

  validation:
    - code: INVALID_PARAMETER
      http_status: 400
      message: "A required parameter is missing or invalid"
      fields:
        field: "The parameter that failed validation"
        expected: "What was expected"
        received: "What was received"
      example:
        error:
          code: "INVALID_PARAMETER"
          message: "quantity must be a positive integer"
          field: "items[0].quantity"
          expected: "integer > 0"
          received: "-1"

  rate_limiting:
    - code: RATE_LIMIT_EXCEEDED
      http_status: 429
      message: "Too many requests"
      headers:
        X-RateLimit-Limit: "Maximum requests per window"
        X-RateLimit-Remaining: "Requests remaining in window"
        X-RateLimit-Reset: "Unix timestamp when window resets"
        Retry-After: "Seconds to wait before retrying"
      resolution: |
        Implement exponential backoff. Check Retry-After header
        for the recommended wait time.
      code_example: |
        # Python: Automatic retry with backoff
        import time

        def api_call_with_retry(func, max_retries=3):
            for attempt in range(max_retries):
                response = func()
                if response.status_code != 429:
                    return response
                retry_after = int(response.headers.get('Retry-After', 60))
                time.sleep(retry_after)
            raise RateLimitError("Max retries exceeded")

Writing Quality Checklist

Completeness:
  [ ] Every endpoint has description, parameters, and examples
  [ ] All error codes documented with resolution steps
  [ ] Authentication fully explained with code
  [ ] Rate limits and quotas documented
  [ ] Pagination strategy documented
  [ ] Webhook events and payloads documented
  [ ] Changelog tracks breaking and non-breaking changes

Clarity:
  [ ] Quickstart gets developer to "hello world" in < 5 minutes
  [ ] Code examples are copy-paste ready
  [ ] Examples show error handling, not just happy path
  [ ] Jargon is defined in a glossary
  [ ] Warnings and important notes are visually distinct

Developer Experience:
  [ ] Code examples in at least 3 languages
  [ ] Try-it-out console available for each endpoint
  [ ] Search works across all documentation
  [ ] Code examples include expected response
  [ ] Authentication tokens in examples use realistic format

Maintenance:
  [ ] OpenAPI spec is source of truth (docs auto-generated)
  [ ] Code examples tested in CI
  [ ] Docs versioned alongside API versions
  [ ] Feedback mechanism on each page
  [ ] Analytics tracking which pages have high bounce rate

When to Use

Use this skill when:

  • Designing or implementing api documentation writer solutions
  • Reviewing or improving existing api documentation writer approaches
  • Making architectural or implementation decisions about api documentation writer
  • Learning api documentation writer patterns and best practices
  • Troubleshooting api documentation writer-related issues

Do NOT use this skill when:

  • The question is about a fundamentally different technology domain
  • A more specific sibling skill covers the exact topic needed
  • The user needs a complete hands-on tutorial rather than expert guidance

Output Format

markdown
# Api Documentation Writer Analysis

## Context Assessment
[Situation summary and constraints]

## Recommended Approach
[Primary recommendation with rationale]

## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]

## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]

## Next Steps
- [Immediate action item]
- [Follow-up action item]

Example

Input: "Help me implement api documentation writer for a medium-scale production application"

Output: A structured analysis covering current state assessment, recommended api documentation writer approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.

Edge Cases

  • Legacy system integration: When api documentation writer must coexist with legacy approaches, provide a gradual migration path rather than a complete rewrite
  • Scale mismatch: When the solution complexity exceeds the project scale, recommend a simpler approach and note when to revisit
  • Team skill gaps: When the team lacks experience with the recommended approach, include learning resources and simpler alternatives
  • Conflicting requirements: When constraints conflict (e.g., performance vs. maintainability), explicitly state the trade-off and recommend based on stated priorities

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/writing/api-documentation-writer of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

API Documentation Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

API Documentation Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
API Documentation Writer this skillFerroxLabs/wayland608—~4kAutomated safety check: PassApache-2.0
Nacos API Doc Updatenacos-group/nacos-group.github.io115—~3.3kAutomated safety check: PassApache-2.0
API Documentation Generatorluongnv89/claude-howto42k—~429Automated safety check: PassMIT
Dashclaw Shipucsandman/DashClaw310—~7.2kAutomated safety check: PassMIT
Agentic Workflows API Documentation Lungoagntcy/coffeeAgntcy112—~2.6kAutomated safety check: PassApache-2.0
Code DocumenterJeffallan/claude-skills12k—~1.5kAutomated safety check: PassMIT

Similar skills

  • Nacos API Doc Update

    nacos-group/nacos-group.github.io

    Updates Nacos API documentation from Swagger api.json. An agent skill from nacos-group/nacos-group.github.io.

    115 GitHub stars~3.3k tokensUpdated 13 days ago
    DevelopmentAuto-check passed
  • API Documentation Generator

    luongnv89/claude-howto

    Generate comprehensive, accurate API documentation from source code. Use when creating or updating API documentation, generating OpenAPI specs, or when users…

    42k GitHub stars~429 tokensUpdated 7 days ago
    DevelopmentAuto-check passed
  • Dashclaw Ship

    ucsandman/DashClaw

    The single command that gets a DashClaw change ON MAIN AND LIVE — it resolves everything blocking production, never defers, and never hands back a checklist.

    310 GitHub stars~7.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Authors and maintains the human-facing Agentic Workflows API documentation for the lungo subproject at coffeeAGNTCY/coffeeagents/lungo/docs/workflow-instanceapi.md.

    112 GitHub stars~2.6k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Code Documenter

    Jeffallan/claude-skills

    Generates and validates docstrings, OpenAPI specs, JSDoc annotations and user guides, running every code example through a real compiler or linter before reporting coverage.

    12k GitHub stars~1.5k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Ukrainian-language skill for writing API documentation from source code: OpenAPI specs, endpoint pages, SDK examples, integration and authentication guides and error code references.

    42k GitHub stars~375 tokensUpdated 7 days ago
    DevelopmentAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about API Documentation Writer

What does API Documentation Writer do?

API documentation expertise covering OpenAPI specification authoring, endpoint documentation patterns, code examples in multiple languages, authentication guides, quickstart tutorials, SDK…. API Documentation Writer is an agent skill from FerroxLabs/wayland. API documentation expertise covering OpenAPI specification authoring, endpoint documentation patterns, code examples in multiple languages, authentication guides, quickstart tutorials, SDK documentation, error reference guides, versioning strategies, interactive documentation portals, and developer experience optimization.

When should I use API Documentation Writer?

API Documentation Writer fits situations like: the user asks about api documentation writer; api documentation writer best practices; needs guidance on api documentation writer implementation; the user needs a different specialized skill.

How do I install API Documentation Writer in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill api-documentation-writer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/writing/api-documentation-writer in FerroxLabs/wayland) into .claude/skills/api-documentation-writer in your project. Claude Code loads it when a task matches its description.

How do I install API Documentation Writer in Codex?

Run `npx skills add FerroxLabs/wayland --skill api-documentation-writer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/writing/api-documentation-writer in FerroxLabs/wayland) into .agents/skills/api-documentation-writer in your project. Codex loads it when a task matches its description.

Can I use API Documentation Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill api-documentation-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-documentation-writer, .gemini/skills/api-documentation-writer, .github/skills/api-documentation-writer and .opencode/skills/api-documentation-writer in your project.

What does API Documentation Writer need to run?

Going by SKILL.md and its folder, API Documentation Writer needs credentials named INVALID_API_KEY. Our summary lists: Python 3; Node.js; A credential in INVALID_API_KEY.

Does API Documentation Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is API Documentation Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does API Documentation Writer use?

API Documentation Writer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does API Documentation Writer use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to API Documentation Writer?

Skills that share tags, products or a category with API Documentation Writer: Nacos API Doc Update (nacos-group/nacos-group.github.io, 115 stars), API Documentation Generator (luongnv89/claude-howto, 42k stars), Dashclaw Ship (ucsandman/DashClaw, 310 stars) and Agentic Workflows API Documentation Lungo (agntcy/coffeeAgntcy, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains API Documentation Writer?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.