rn-technical-documentation

rn-technical-documentation is a skill for Claude Code, Codex from cmaranho/rn-agent-skills. It costs 50 tokens per session (450 once invoked), scanned A, original, MIT.

A guide for writing technical documentation for React Native projects, which are mobile applications built with React Native. It covers setup guides, READMEs, architecture decisions, components, APIs, and build or release processes.

In plain words
What is it for?
Use it to create or update onboarding and setup documentation, architecture decision records, component or API references, and build instructions.
Why use it?
It helps new contributors understand, run, and maintain a project without relying on undocumented knowledge. It also encourages recording why important technical decisions were made.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to create or update onboarding and setup documentation, architecture decision records, component or API references, and build instructions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cmaranho/rn-agent-skills/rn-technical-documentation
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cmaranho/rn-agent-skills --skill rn-technical-documentation
Clone the repo
git clone --depth 1 https://github.com/cmaranho/rn-agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for rn-technical-documentation

README.md
[![agentmods](https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-technical-documentation/github.svg)](https://agentmods.dev/skills/cmaranho/rn-agent-skills/rn-technical-documentation)
Your own site
<a href="https://agentmods.dev/skills/cmaranho/rn-agent-skills/rn-technical-documentation"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-technical-documentation/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for rn-technical-documentation

Your own site · 80×15
<a href="https://agentmods.dev/skills/cmaranho/rn-agent-skills/rn-technical-documentation"><img src="https://agentmods.dev/badge/skills/cmaranho/rn-agent-skills/rn-technical-documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00450
Opus 5.5 $0.00020 $0.00180
Sonnet 5.5 $0.00010 $0.00090
Haiku 4.5 $0.00005 $0.00045

Measured 2mo ago against content hash 1d852c355526, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rn-technical-documentation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/rn-technical-documentation/SKILL.md · 52 lines

What it actually says

React Native — Documentação Técnica

Objetivo

Documentar o essencial para que qualquer pessoa entenda, rode e evolua o projeto.

Quando utilizar

  • Criar/atualizar README, guia de setup ou onboarding.
  • Registrar uma decisão de arquitetura (ADR).
  • Documentar componentes, APIs públicas ou o fluxo de build/release.

Conhecimentos necessários

  • Estrutura de README e documentação de setup (pré-requisitos, install, run, env).
  • ADRs (contexto, decisão, consequências).
  • Documentação de componentes/props e contratos de API.
  • Diagramas simples (fluxo/camadas) quando ajudam.

Fluxo de execução

  1. Identifique a audiência e o objetivo do documento.
  2. Documente o setup: pré-requisitos, instalação, variáveis e comandos de build/run por plataforma.
  3. Descreva arquitetura e fluxo de dados de alto nível (com diagrama, se útil).
  4. Registre decisões relevantes como ADR (por quê, alternativas, consequências).
  5. Mantenha a doc próxima do código; atualize junto com a mudança.

Boas práticas

  • Objetivo e conciso; exemplos executáveis e copiáveis.
  • Documente o PORQUÊ; o QUÊ deve ser óbvio pelo código.
  • Fonte única da verdade; evite duplicar o que muda com frequência.
  • Docs versionadas junto ao código.

Armadilhas comuns

  • Documentação que desatualiza (duplica detalhes voláteis).
  • README sem passos reproduzíveis de setup/run.
  • Decisões arquiteturais não registradas.
  • Muro de texto sem estrutura, exemplos ou diagramas.

Critérios de sucesso

  • Alguém novo consegue rodar o projeto seguindo o README.
  • Decisões-chave rastreáveis via ADRs.
  • Docs atualizadas junto com a mudança que descrevem.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 52 lines · 50 tokens per session scan A 1d852c355526

Subscribe to this mod's changes

rn-technical-documentation is a skill published in the GitHub repository cmaranho/rn-agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 450 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

rn-technical-documentation compared with skills from other repositories

rn-technical-documentation next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
rn-technical-documentationcmaranho/rn-agent-skillsSkill24mo agoMITA50Claude Code, Codex
orca-emulator-androidstablyai/orcaSkill117kyesterdayMITA102Claude Code, Codex
glance-canonical-layoutsandroid/skillsSkill10kyesterdayApache-2.0A56Claude Code
android-tombstone-symbolicationdotnet/skillsSkill5.8kyesterdayMITA176Claude Code
dogfoodcallstack/agent-deviceSkill5.3kyesterdayMITA55Claude Code
winapp-mauimicrosoft/winappCliSkill1.4kyesterdayMITA68Claude Code
app_remixrome-os/romeSkill889yesterdayMITA50Claude Code, Codex