Query Docs And Library Metadata
Use this skill to collect authoritative context before code generation or integration selection.
Best use case
Query Docs And Library Metadata is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use this skill to collect authoritative context before code generation or integration selection.
Teams using Query Docs And Library Metadata should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/query-docs-library-metadata/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Query Docs And Library Metadata Compares
| Feature / Agent | Query Docs And Library Metadata | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use this skill to collect authoritative context before code generation or integration selection.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Query Docs And Library Metadata Use this skill to collect authoritative context before code generation or integration selection. ## Setup ```bash npx @tanstack/cli libraries --json ``` ## Core Patterns ### Resolve valid library ids before doc fetch ```bash npx @tanstack/cli libraries --json ``` ### Fetch a specific docs page with explicit version ```bash # Syntax: tanstack doc <library-id> <path> [--docs-version <version>] npx @tanstack/cli doc router framework/react/guide/routing npx @tanstack/cli doc router framework/react/guide/routing --docs-version latest ``` ### Search docs for implementation targets ```bash npx @tanstack/cli search-docs "server functions" --library start --json ``` ## Common Mistakes ### HIGH Use invalid library id/version/path for doc fetch Wrong: ```bash # Wrong: --library and --version are not flags on doc; path must not include /docs/ prefix npx @tanstack/cli doc --library router --version latest --path /docs/framework/react/guide/routing ``` Correct: ```bash # Step 1: resolve a valid library id npx @tanstack/cli libraries --json # Step 2: fetch using positional args — library id then doc path (no /docs/ prefix) npx @tanstack/cli doc router framework/react/guide/routing ``` `doc` takes `<library>` and `<path>` as positional arguments (not flags), and the path must not include a leading `/docs/` segment. Use `--docs-version` (not `--version`) to pin a specific version. Source: packages/cli/src/cli.ts:746 ### MEDIUM Rely on deprecated create alias for discovery Wrong: ```bash npx create-tsrouter-app --list-add-ons ``` Correct: ```bash npx @tanstack/cli create --list-add-ons --json ``` Legacy alias workflows can produce confusing outputs that do not match current CLI discovery behavior. Fixed in newer versions, but agents trained on older examples may still generate this pattern. Source: https://github.com/TanStack/cli/issues/93 ### HIGH Tension: Single-command convenience vs integration precision This domain's patterns conflict with create-app-scaffold and choose-ecosystem-integrations. Skipping discovery to run one-shot scaffold commands tends to lock in plausible defaults that miss architecture constraints. See also: create-app-scaffold/SKILL.md § Common Mistakes ## References - [Discovery command output schemas](references/discovery-command-output-schemas.md)
Related Skills
generating-api-docs
Create comprehensive API documentation with examples, authentication guides, and SDKs. Use when creating comprehensive API documentation. Trigger with phrases like "generate API docs", "create API documentation", or "document the API".
filtering-query-builder
Filtering Query Builder - Auto-activating skill for API Development. Triggers on: filtering query builder, filtering query builder Part of the API Development skill category.
database-query-profiler
Database Query Profiler - Auto-activating skill for Performance Testing. Triggers on: database query profiler, database query profiler Part of the Performance Testing skill category.
cte-query-builder
Cte Query Builder - Auto-activating skill for Data Analytics. Triggers on: cte query builder, cte query builder Part of the Data Analytics skill category.
bigquery-table-creator
Bigquery Table Creator - Auto-activating skill for GCP Skills. Triggers on: bigquery table creator, bigquery table creator Part of the GCP Skills skill category.
bigquery-scheduled-query
Bigquery Scheduled Query - Auto-activating skill for GCP Skills. Triggers on: bigquery scheduled query, bigquery scheduled query Part of the GCP Skills skill category.
bigquery-ml-model-creator
Bigquery Ml Model Creator - Auto-activating skill for GCP Skills. Triggers on: bigquery ml model creator, bigquery ml model creator Part of the GCP Skills skill category.
analyzing-query-performance
Execute use when you need to work with query optimization. This skill provides query performance analysis with comprehensive guidance and automation. Trigger with phrases like "optimize queries", "analyze performance", or "improve query speed".
defold-docs-fetch
Fetches Defold manuals and documentation. Use when looking up how Defold features work, understanding concepts, components, workflows, platform setup, or needing guidance beyond API reference.
mkdocs-translations
Generate a language translation for a mkdocs documentation stack.
microsoft-docs
Query official Microsoft documentation to find concepts, tutorials, and code examples across Azure, .NET, Agent Framework, Aspire, VS Code, GitHub, and more. Uses Microsoft Learn MCP as the default, with Context7 and Aspire MCP for content that lives outside learn.microsoft.com.
java-docs
Ensure that Java types are documented with Javadoc comments and follow best practices for documentation.