Brave Local POI Details
brave/brave-search-skills
Looks up full details for local businesses and places, including ratings, hours and contact information, from Brave Search API point-of-interest IDs.
A skill your agent uses when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs…
Install Read The Damn Docs
$ npx skills add BuilderIO/skills --skill read-the-damn-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install BuilderIO/skills read-the-damn-docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/read-the-damn-docs .claude/skills/read-the-damn-docs && rm -rf skills-srcUse ~/.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/
Install the "read-the-damn-docs" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/read-the-damn-docs into .claude/skills/read-the-damn-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "read-the-damn-docs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/BuilderIO/skills/tree/main/skills/read-the-damn-docsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add BuilderIO/skills --skill read-the-damn-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install BuilderIO/skills read-the-damn-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/read-the-damn-docs .agents/skills/read-the-damn-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "read-the-damn-docs" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/read-the-damn-docs into .agents/skills/read-the-damn-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "read-the-damn-docs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill read-the-damn-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install BuilderIO/skills read-the-damn-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/read-the-damn-docs .cursor/skills/read-the-damn-docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "read-the-damn-docs" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/read-the-damn-docs into .cursor/skills/read-the-damn-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "read-the-damn-docs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/BuilderIO/skills.git --path skills/read-the-damn-docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add BuilderIO/skills --skill read-the-damn-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install BuilderIO/skills read-the-damn-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/read-the-damn-docs .gemini/skills/read-the-damn-docs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "read-the-damn-docs" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/read-the-damn-docs into .gemini/skills/read-the-damn-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "read-the-damn-docs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install BuilderIO/skills read-the-damn-docsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add BuilderIO/skills --skill read-the-damn-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/read-the-damn-docs .github/skills/read-the-damn-docs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "read-the-damn-docs" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/read-the-damn-docs into .github/skills/read-the-damn-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "read-the-damn-docs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add BuilderIO/skills --skill read-the-damn-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install BuilderIO/skills read-the-damn-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/BuilderIO/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/read-the-damn-docs .opencode/skills/read-the-damn-docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "read-the-damn-docs" agent skill from https://github.com/BuilderIO/skills/tree/main/skills/read-the-damn-docs into .opencode/skills/read-the-damn-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "read-the-damn-docs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
read-the-damn-docs- GitHub stars
- 4.5k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 920 words
- Files
- 3
- Skills in repo
- 25
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs…
- Works in 7 steps: Identify the exact surface: package… → Search the web for the current official… → Open and read the docs closest to that… → …
- Answering anything involving third-party APIs
- SKILL.md covers Docs-First Triggers, What Counts As Docs, Required Workflow and Examples That Must Trigger Docs, plus 2 more sections
- Calls npm and pnpm
What it does
Read The Damn Docs is an agent skill from BuilderIO/skills. Use when implementing, integrating, upgrading, debugging, or answering 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 Codex to web-search for current official docs and read primary docs before assuming from…
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `README.md` and `agents/openai.yaml`).
It sits in Backend & APIs, covering Web search and Third-party API integration. The licence is MIT.
When your agent uses it
- Answering anything involving third-party APIs
- Model/provider SDKs
- Fast-moving product behavior
- User requests for latest/current/official behavior
Example prompts
- “/read-the-damn-docs”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify the exact surface: package name, installed version, target version,
- Search the web for the current official docs unless the relevant docs are
- Open and read the docs closest to that surface. Prefer local docs first for
- Extract the few facts needed for the task: option names, imports, lifecycle
- Implement or answer using those facts. If the docs conflict with existing
- Verify with the smallest useful check: typecheck, tests, build, CLI dry run,
- In the final answer, name the docs or local files consulted when that
What it can do on your machine
Read from SKILL.md and the folder at commit da158ca. 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:
npmpnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and pnpm, 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
Read The Damn Docs loads about 1.8k tokens when it runs. Until then it costs about 136 tokens; SKILL.md has 920 words of instructions outside code blocks.
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 BuilderIO/skills at commit da158ca, republished under its MIT licence (© BuilderIO). 920 words, ~1,758 tokens.
Download SKILL.mdSave it as
.claude/skills/read-the-damn-docs/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- read-the-damn-docs
- description
- Use when implementing, integrating, upgrading, debugging, or answering 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 Codex to web-search for current official docs and read primary docs before assuming from memory.
Read The Damn Docs
Do not guess where authoritative docs can answer the question. The most common right move is to web-search for the current official docs, open the relevant pages, and read them before coding. For APIs, versions, provider behavior, config, limits, lifecycle hooks, or security-sensitive flows, ground the answer in what the docs actually say.
Docs-First Triggers
Read docs before proceeding when any of these are true:
- The user asks for "latest", "current", "official", "supported", "best practice", "recommended", "today", "now", or "look it up".
- The needed docs are not already in the repo or supplied by the user. Search the web for the official docs rather than hoping model memory is current.
- The task adds, upgrades, configures, or imports a package, SDK, framework, plugin, CLI, model, cloud resource, or provider integration.
- The API is fast-moving or version-sensitive: AI SDKs, OpenAI/Anthropic/Google APIs, Next.js, React, Tailwind, Vite, Nitro, Drizzle, Prisma, Stripe, GitHub, Slack, Notion, browser APIs, deployment platforms, auth libraries, and similar.
- The implementation depends on auth, OAuth scopes, permissions, secrets, webhooks, billing, payments, PII, encryption, data retention, migrations, retries, rate limits, quotas, caching, deploys, or compliance.
- An error mentions deprecation, unknown options, missing exports, invalid config, unsupported fields, changed defaults, or version mismatch.
- A repo has local docs, ADRs, generated schemas, OpenAPI specs, route/action registries, design-system docs, or package-level READMEs that could define the contract.
- The choice is expensive to reverse: public wire formats, database schema, migration strategy, persistent IDs, event names, customer-visible behavior, or external automation contracts.
- You catch yourself about to write "usually", "probably", "I think", "from memory", or code copied from model memory for an external API.
What Counts As Docs
Use the most authoritative source available:
- Local repo docs, specs, ADRs, schemas, generated types, package READMEs, and tests for project-specific behavior.
- Official product docs, API references, migration guides, changelogs, release notes, and SDK source/types for third-party behavior. Find these with web search when you do not already have the exact URL.
- Package registry metadata for versions. Before adding a dependency, run
npm view <pkg> version,pnpm view <pkg> version, or the ecosystem equivalent, then read the docs for that major version. - Source code or type definitions when official docs are incomplete. Treat this as evidence, not folklore.
Avoid Stack Overflow, old blog posts, random snippets, and memory as the primary source when official docs exist. Use community sources only to debug symptoms after the authoritative contract is known.
Required Workflow
- Identify the exact surface: package name, installed version, target version, provider endpoint, CLI command, config file, local helper, schema, or product feature.
- Search the web for the current official docs unless the relevant docs are
already local or the user supplied a URL. Use targeted searches such as
<product> <feature> official docs,<package> migration guide, or<provider> API reference. - Open and read the docs closest to that surface. Prefer local docs first for internal code, then official upstream docs. For new packages, verify the latest version before writing imports, config, or install commands.
- Extract the few facts needed for the task: option names, imports, lifecycle rules, default behavior, breaking changes, limits, permissions, and examples for the current major version.
- Implement or answer using those facts. If the docs conflict with existing code, inspect the local code path and call out the discrepancy.
- Verify with the smallest useful check: typecheck, tests, build, CLI dry run, API schema validation, or a local reproduction.
- In the final answer, name the docs or local files consulted when that evidence affects the recommendation or implementation.
Show full SKILL.md (328 more words)Show less
Examples That Must Trigger Docs
- "Add Tailwind to this app." Check the current Tailwind major and its install docs from the web before creating config files or assuming old PostCSS setup.
- "Use the AI SDK to stream responses." Verify the current AI SDK major, imports, provider package names, streaming helpers, and server/runtime examples from official docs.
- "Wire up Stripe webhooks." Read Stripe's current signature verification, event retry, endpoint secret, and framework body-parsing docs before coding.
- "Fix this Next.js caching bug." Read the docs for the installed Next.js major and router mode before assuming cache invalidation semantics.
- "Add Drizzle migrations." Read the current Drizzle kit docs and existing repo migration conventions before generating files.
- "Create a GitHub Action." Read official Actions syntax and permissions docs,
especially for
pull_request,workflow_run, OIDC, tokens, and artifacts. - "Why does this OAuth flow fail?" Read the provider's scopes, redirect URI, PKCE, token refresh, and app verification docs before changing code.
- "Use this repo's plan/comment/action system." Read local docs, route/action registries, schemas, and tests before inventing endpoints or props.
- "Upgrade Vite/Nitro/React." Read the migration guide for the exact target major before editing config or imports.
- "What model should we use?" Read current provider model docs, pricing/limits pages, and SDK examples before recommending.
When A Quick Local Read Is Enough
Do not browse the web for every tiny edit. A docs pass can be local and brief when the answer is already in the repo: existing helper usage, nearby tests, typed interfaces, generated clients, ADRs, or package READMEs. But if the task depends on an external tool, package, provider, or current product behavior, web search is usually the right first step. For trivial language syntax, typo fixes, formatting, or self-contained code with no external contract, proceed normally.
If Docs Are Unavailable
If network access, auth, or missing local files prevents reading the docs, say that plainly before relying on memory. Narrow the uncertainty, inspect source or types if available, and avoid presenting the result as confirmed-current.
© BuilderIO, 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 2 other files in skills/read-the-damn-docs of BuilderIO/skills.
- SKILL.md
- README.md
- agents/openai.yaml
Open the folder on GitHubat commit da158ca
Compare with similar skills
Read The Damn Docs 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Read The Damn Docs this skillBuilderIO/skills | 4.5k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Brave Local POI Detailsbrave/brave-search-skills | 183 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Brave Local Place Descriptionsbrave/brave-search-skills | 183 | — | ~1k | Automated safety check: Pass | MIT | |
| Firecrawl App Integrationfirecrawl/firecrawl | 190k | — | ~2.1k | Automated safety check: Notes | ISC | |
| Tavily Search API Integrationandrewyng/context-hub | 14k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Brave LLM Context APIbrave/brave-search-skills | 183 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Brave Local Place Descriptions
brave/brave-search-skills
Fetches AI-written text descriptions for local places from the Brave Search API, using place IDs returned by an earlier local search.
Firecrawl App Integration
firecrawl/firecrawl
Adds web search, scraping, structured extraction and browser interaction to application code using Firecrawl's scrape, search and interact endpoints.
Tavily Search API Integration
andrewyng/context-hub
Guides building Tavily integrations for web search, URL extraction, site crawling and AI-assisted research in Python or JavaScript agent and RAG projects.
Brave LLM Context API
brave/brave-search-skills
Documents Brave's LLM Context API, which returns pre-extracted, ranked web page content for grounding agent and RAG answers, with GET and POST calls and Goggles filters.
Brave Local Place Search
brave/brave-search-skills
Looks up businesses, points of interest, addresses and streets through the Brave Search place endpoint, returning contact details, ratings and hours in one call.
More from BuilderIO/skills
All 25 skills in this repoTurn Into App
BuilderIO/skills
Turns a thread, skill, spreadsheet, or Claude/ChatGPT project into a polished, visual Agent-Native app: populated domain screens with the in-app agent working behind contextual controls.
Agent Watchdog
BuilderIO/skills
A skill your agent uses when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log…
Plan Arbiter
BuilderIO/skills
A skill your agent uses when asked to compare, cross-review, merge, judge, choose, or arbitrate competing plans from multiple agents such as Codex and Claude Code; when given two or more proposed…
Plow Ahead
BuilderIO/skills
A skill your agent uses when the user explicitly wants autonomous progress without routine clarification stops: "plow ahead", "do not stop", "use your best judgment", "keep going until done"…
Stay Within Limits
BuilderIO/skills
A skill your agent uses when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window…
Efficient Fable
BuilderIO/skills
A skill your agent uses when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy…
Related
Questions about Read The Damn Docs
What does Read The Damn Docs do?
A skill your agent uses when implementing, integrating, upgrading, debugging, or answering anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs…. Read The Damn Docs is an agent skill from BuilderIO/skills. Use when implementing, integrating, upgrading, debugging, or answering 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.
When should I use Read The Damn Docs?
Read The Damn Docs fits situations like: answering anything involving third-party APIs; model/provider SDKs; fast-moving product behavior; user requests for latest/current/official behavior.
How do I install Read The Damn Docs in Claude Code?
Run `npx skills add BuilderIO/skills --skill read-the-damn-docs -a claude-code`. Or copy the skill folder (skills/read-the-damn-docs in BuilderIO/skills) into .claude/skills/read-the-damn-docs in your project. Claude Code loads it when a task matches its description.
How do I install Read The Damn Docs in Codex?
Run `npx skills add BuilderIO/skills --skill read-the-damn-docs -a codex`. Or copy the skill folder (skills/read-the-damn-docs in BuilderIO/skills) into .agents/skills/read-the-damn-docs in your project. Codex loads it when a task matches its description.
Can I use Read The Damn Docs 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 BuilderIO/skills --skill read-the-damn-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/read-the-damn-docs, .gemini/skills/read-the-damn-docs, .github/skills/read-the-damn-docs and .opencode/skills/read-the-damn-docs in your project.
What does Read The Damn Docs need to run?
Going by SKILL.md and its folder, Read The Damn Docs needs the command-line tools its instructions call (npm and pnpm).
Does Read The Damn Docs access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Read The Damn Docs 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 Read The Damn Docs use?
Read The Damn Docs 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 Read The Damn Docs use?
About 1.8k tokens (SKILL.md is roughly 7k 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 Read The Damn Docs?
Skills that share tags, products or a category with Read The Damn Docs: Brave Local POI Details (brave/brave-search-skills, 183 stars), Brave Local Place Descriptions (brave/brave-search-skills, 183 stars), Firecrawl App Integration (firecrawl/firecrawl, 190k stars) and Tavily Search API Integration (andrewyng/context-hub, 14k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Read The Damn Docs?
BuilderIO (a GitHub organization) maintains it in BuilderIO/skills, which has 4,541 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 7, 2026.
Source: BuilderIO/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.