ai-read-docs
From the author
Use when the work depends on versioned or external behaviour — adding a package, writing setup or config, integrating an SDK or a paid API, debugging a framework change — or on anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces a docs pass (web-search of official sources) and reading primary docs before assuming from memory. Not for evidence from outside this repository generally — use /ai-research; not for questions the repository answers — use /ai-explore.
Install
npx skills add arcasilesgroup/ai-engineering --skill ai-read-docs -a claude-code
Installs to .claude/skills/ai-read-docs/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- openai-docsopenai/skillsUse when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.OfficialOther★ 28.3K
- ai-writearcasilesgroup/ai-engineeringWrites technical documentation for this repository: a README, a wiki page, product documentation, API docs or a technical post. Applies the framework's single writing standard (`references/documentation-writer.md`) and verifies every document against the tree. Trigger for "write the README", "update the wiki", "document this API", "write a technical post about", "refresh the docs". Not for the changelog. Not for a feature plan — use /ai-orchestrator. Not for a finding — use /ai-note. Not for an issue or incident report — use /ai-issue-report.Writing★ 61
- docs-guardamElnagdy/guard-skillsReview generated or changed documentation before it ships — READMEs, API references, docstrings, PHPDoc/JSDoc, changelogs, tutorials, and doc sites. Best used reactively after an agent writes or edits docs, after code changes documented behavior, or before publishing docs. Use when the user says 'review the docs', 'is this documentation accurate', 'update the docs', 'write a README', 'document this API', 'add a docstring', or 'add a changelog entry'. Core job: verify every referenced function, flag, endpoint, config key, and code sample against the source; catch docs-vs-code drift; strip filler and unverifiable claims. DO NOT USE for production code review (use clean-code-guard), test review (use test-guard), marketing copy or blog posts, prose style editing of non-technical writing, or documentation site theming.Testing★ 1.3K
- docsaiskillstore/marketplaceResearch documentation, find examples, explain APIs and libraries - Use when you need to look up official documentation, find code examples, understand library APIs, or research best practices.Science★ 443
- ai-audit-docsarcasilesgroup/ai-engineeringAudits documentation files against actual repo state. Detects dead references (links to nonexistent files/URLs), false claims (doc says feature X exists but the code doesn't), outdated version numbers, and references to commands that don't exist. Input: path to docs dir or specific files (defaults to docs/ README.md AGENTS.md). Output: ranked markdown table of findings with severity and location. Report-only, NO auto-fix. Trigger phrases: "audit docs", "check documentation", "verify docs", "docs review", "documentation audit".Planning★ 61
- documentation-lookupforyourhealth111-pixel/Vibe-SkillsUse when the user needs current library, framework, or API documentation and version-specific code examples.Planning★ 3.8K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in