New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Generate Doc

by hyochan in hyochan/react-native-nitro-sound

Create or update react-native-nitro-sound API documentation, examples, migration notes, FAQ entries, changelog or release notes, and compiled AI context.

MITAuto-check passedDevelopment

Install Generate Doc

skills CLI
$ npx skills add hyochan/react-native-nitro-sound --skill generate-doc -a claude-code

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

GitHub CLI
$ gh skill install hyochan/react-native-nitro-sound generate-doc --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/hyochan/react-native-nitro-sound.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/generate-doc .claude/skills/generate-doc && 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
generate-doc
GitHub stars
961
Token cost
~824 tokens
SKILL.md length
375 words
Files
2
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Create or update react-native-nitro-sound API documentation, examples, migration notes, FAQ entries, changelog or release notes, and compiled AI context.

  • Works in 6 steps: AGENTS.md and the user's requested change. → package.json, nitro.json, and the… → src/index.tsx, src/index.web.tsx, hooks,… → …
  • Native behavior
  • SKILL.md covers Choose The Surface, Collect Evidence, Write Accurate Examples and Prepare Release Documentation, plus 1 more section
  • Calls yarn and git

What it does

Generate Doc is an agent skill from hyochan/react-native-nitro-sound. Create or update react-native-nitro-sound API documentation, examples, migration notes, FAQ entries, changelog or release notes, and compiled AI context. Use when public exports, Nitro specs, native behavior, compatibility requirements, installation steps, or releases need documentation.

Its SKILL.md is about 820 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Changelog and release notes, Cross-platform mobile apps and Help center and FAQ content. It works with React Native. The repository describes itself as: react-native native module for audio recorder and player with nitromodule! The licence is MIT.

When your agent uses it

  • Native behavior
  • Compatibility requirements
  • Installation steps
  • Releases need documentation

Example prompts

  • “/generate-doc”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. AGENTS.md and the user's requested change.
  2. package.json, nitro.json, and the current Git tag or intended release.
  3. src/index.tsx, src/index.web.tsx, hooks, and src/specs/*.nitro.ts.
  4. Relevant ios/*.swift and android/src/main/**/*.kt implementations.
  5. Existing README, FAQ, changelog, issue, and PR language that the edit affects.
  6. CI and release workflows when documenting build or publication behavior.

What it can do on your machine

Read from SKILL.md and the folder at commit efd5e54. 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

    Shell commands in SKILL.md call:

    • yarn
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use yarn and git, which can reach the network depending on how they are called.

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Generate Doc loads about 824 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 375 words of instructions outside code blocks.

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

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 hyochan/react-native-nitro-sound at commit efd5e54, republished under its MIT licence (© hyochan). 375 words, ~824 tokens.

Download SKILL.mdSave it as .claude/skills/generate-doc/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
generate-doc
description
Create or update react-native-nitro-sound API documentation, examples, migration notes, FAQ entries, changelog or release notes, and compiled AI context. Use when public exports, Nitro specs, native behavior, compatibility requirements, installation steps, or releases need documentation.

Generate Nitro Sound Documentation

Ground every statement in the current repository and keep all documented platforms aligned with the implementation.

Choose The Surface

  • Update README.md for installation, requirements, API usage, public examples, and high-level migration guidance.
  • Update docs/FAQ.md for reproducible troubleshooting and platform-specific workarounds.
  • Update CHANGELOG.md only when preparing or correcting release history.
  • Update knowledge/_claude-context/context.md after meaningful API, native, dependency, or maintenance-workflow changes.
  • Update example screens when documentation depends on behavior users must be able to run.

Do not create a new documentation surface when an existing one has the right audience.

Collect Evidence

Read, in order:

  1. AGENTS.md and the user's requested change.
  2. package.json, nitro.json, and the current Git tag or intended release.
  3. src/index.tsx, src/index.web.tsx, hooks, and src/specs/*.nitro.ts.
  4. Relevant ios/*.swift and android/src/main/**/*.kt implementations.
  5. Existing README, FAQ, changelog, issue, and PR language that the edit affects.
  6. CI and release workflows when documenting build or publication behavior.

Use package metadata for versions. Verify current registry, platform, or toolchain facts from authoritative sources when they may have changed. Never infer a released version from an unreleased branch or generated file.

Write Accurate Examples

  • Use imports actually exported by src/index.tsx.
  • Show asynchronous recorder/player loading states where the API requires them.
  • Keep record and playback positions in milliseconds.
  • Include microphone permission and native setup only where the platform needs it.
  • Distinguish iOS, Android, and Web behavior instead of implying false parity.
  • Prefer a short runnable example over disconnected snippets.
  • Link issues or releases for non-obvious compatibility guidance.
  • Never document hand-edits to nitrogen/generated/** as a supported fix.
Show full SKILL.md (118 more words)Show less

Prepare Release Documentation

Derive the change range from the previous published tag through the exact target head. Group notes by user impact rather than commit mechanics. Exclude generated file churn, version-only noise, and internal workflow edits unless they change a maintainer-facing contract.

When the automated deploy workflow will update CHANGELOG.md, prepare or test the release-note input without duplicating the generated entry. Confirm the tag format and version behavior from .github/workflows/publish-package.yml before naming links.

Validate

Run the checks relevant to the examples and files changed:

bash
yarn typecheck
yarn lint
yarn test
git diff --check

Add yarn build:web for Web examples and a platform build for native setup or behavior claims. Re-read rendered Markdown, verify anchors and links, and report any platform behavior that was documented but not exercised.

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

Files

SKILL.md and 1 other file in .codex/skills/generate-doc of hyochan/react-native-nitro-sound.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit efd5e54

Compare with similar skills

Generate Doc 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.

Generate Doc compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Generate Doc this skillhyochan/react-native-nitro-sound961—~824Automated safety check: PassMIT
DocumentationEliasOulkadi/shokunin114—~2kAutomated safety check: PassMIT
Opencollective Stewardhyodotdev/openiap154—~1.5kAutomated safety check: PassMIT
Code Guidelinesgetsentry/sentry-react-native1.8k—~3.2kAutomated safety check: PassMIT
Jazz UI Developmentgarden-co/classic-jazz2.5k—~1.7kAutomated safety check: PassMIT
Release Pluginflutter/flutter-intellij2k—~1kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Documentation

    EliasOulkadi/shokunin

    Generate READMEs, API docs, changelogs, and knowledge base articles.

    114 GitHub stars~2k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Opencollective Steward

    hyodotdev/openiap

    Manage OpenIAP's OpenCollective presence, including profile copy, slug/link migrations, sponsor/backer recognition, update posts, and README/docs sponsor assets.

    154 GitHub stars~1.5k tokensUpdated yesterday
    MobileAuto-check passed

  • Code Guidelines

    getsentry/sentry-react-native

    Official

    Enforce Sentry React Native SDK code guidelines for implementation, refactoring, and review.

    1.8k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Jazz UI Development

    garden-co/classic-jazz

    A skill your agent uses when building, debugging, or optimizing Jazz applications.

    2.5k GitHub stars~1.7k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Release Plugin

    flutter/flutter-intellij

    Prepare and execute a new release for the flutter-intellij plugin, including updating dependencies, compatibility bounds, changelogs, and verification.

    2k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check passed

  • Survey SDK Audit

    PostHog/posthog

    Official

    Audit PostHog survey SDK features and version requirements, and implement survey changes across the backend, UI, and SDK repositories.

    40k GitHub stars~4.3k tokensUpdated today
    DevelopmentAuto-check passed

More from hyochan/react-native-nitro-sound

All 14 skills in this repo

  • Simulator Audio E2E

    hyochan/react-native-nitro-sound

    Build and run repeatable react-native-nitro-sound recorder/player regression tests on an iOS Simulator or Android emulator, with explicit virtual-device selection, microphone permission, Maestro…

    961 GitHub stars~1.1k tokensUpdated 9 days ago
    Auto-check passed

  • Android Audio E2E

    hyochan/react-native-nitro-sound

    Build and run device-backed Android end-to-end checks for react-native-nitro-sound permissions, recording, playback, listeners, pause/resume, seek, speed, audio focus, lifecycle behavior, and rapid…

    961 GitHub stars~814 tokensUpdated 9 days ago
    Auto-check passed

  • iOS Audio E2E

    hyochan/react-native-nitro-sound

    Build and run device-backed iOS end-to-end checks for react-native-nitro-sound recording, playback, listeners, pause/resume, seek, speed, interruption, audio-session behavior, and rapid switching.

    961 GitHub stars~907 tokensUpdated 9 days ago
    Auto-check passed

  • Funding Steward

    hyochan/react-native-nitro-sound

    Maintain react-native-nitro-sound funding links, GitHub Funding configuration, Buy Me a Coffee and PayPal calls to action, supporter acknowledgements, and transparent maintainer updates.

    961 GitHub stars~650 tokensUpdated 9 days ago
    Auto-check passed

  • Nitro Sound Workflows

    hyochan/react-native-nitro-sound

    A skill your agent uses for react-native-nitro-sound repository work that should follow the project workflows for PR review, code audit, knowledge compilation, full verification, iOS or Android…

    961 GitHub stars~1.2k tokensUpdated 9 days ago
    Auto-check passed

  • Rebase Main

    hyochan/react-native-nitro-sound

    Safely update local main from origin/main, rebase the current react-native-nitro-sound work branch, resolve conflicts without losing staged, unstaged, untracked, ignored, or generated work, and…

    961 GitHub stars~702 tokensUpdated 9 days ago
    Auto-check passed

Works with

Categories

Questions about Generate Doc

What does Generate Doc do?

Create or update react-native-nitro-sound API documentation, examples, migration notes, FAQ entries, changelog or release notes, and compiled AI context. Generate Doc is an agent skill from hyochan/react-native-nitro-sound. Create or update react-native-nitro-sound API documentation, examples, migration notes, FAQ entries, changelog or release notes, and compiled AI context.

When should I use Generate Doc?

Generate Doc fits situations like: native behavior; compatibility requirements; installation steps; releases need documentation.

How do I install Generate Doc in Claude Code?

Run `npx skills add hyochan/react-native-nitro-sound --skill generate-doc -a claude-code`. Or copy the skill folder (.codex/skills/generate-doc in hyochan/react-native-nitro-sound) into .claude/skills/generate-doc in your project. Claude Code loads it when a task matches its description.

How do I install Generate Doc in Codex?

Run `npx skills add hyochan/react-native-nitro-sound --skill generate-doc -a codex`. Or copy the skill folder (.codex/skills/generate-doc in hyochan/react-native-nitro-sound) into .agents/skills/generate-doc in your project. Codex loads it when a task matches its description.

Can I use Generate Doc 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 hyochan/react-native-nitro-sound --skill generate-doc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/generate-doc, .gemini/skills/generate-doc, .github/skills/generate-doc and .opencode/skills/generate-doc in your project.

What does Generate Doc need to run?

Going by SKILL.md and its folder, Generate Doc needs the command-line tools its instructions call (yarn and git).

Does Generate Doc access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Generate Doc 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 Generate Doc use?

Generate Doc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Generate Doc use?

About 824 tokens (SKILL.md is roughly 3.3k 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 Generate Doc?

Skills that share tags, products or a category with Generate Doc: Documentation (EliasOulkadi/shokunin, 114 stars), Opencollective Steward (hyodotdev/openiap, 154 stars), Code Guidelines (getsentry/sentry-react-native, 1.8k stars) and Jazz UI Development (garden-co/classic-jazz, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Generate Doc?

hyochan (a GitHub user) maintains it in hyochan/react-native-nitro-sound, which has 961 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 29, 2026.

Source: hyochan/react-native-nitro-sound on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.