Skip to content
cccskills
FreePublished on GitHub

docs-routing

Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.7 KB
  • agents/openai.yaml268 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Documentation Routing

Use this route for current product documentation unless a higher-authority product-specific documentation workflow applies.

Before each lookup:

  • Ask for the missing documentation fact or closely related facts, rather than passing the whole implementation task to the provider.
  • Separate independent products or topics into focused queries. Combine them when the question concerns their interaction or a comparison.
  • Include the exact product and requested version; add the repository owner or technical context when names are ambiguous (for example, mistral.rs with Apple's Metal backend). Set the tool's product field when available.

Follow this provider order for each lookup:

  1. Use context7 to resolve the exact library and version. The plugin default is anonymous, but native same-name configuration may replace it with an authenticated connection.
  2. Accept only nonempty, relevant results that cover the requested version and include traceable source URLs.
  3. When context7 is anonymous and rate-limited, unavailable, or insufficient, use context7_auth if available and apply the same acceptance test.
  4. Then fall back to official primary documentation or source.
  5. Never send secrets, credentials, private code, full prompts, or non-public internal content to either connection.
  6. If a named tool is absent, advance without automatically installing, authenticating, or retrying it. A host authentication prompt leaves the call pending; after it is resolved or dismissed, evaluate the result and continue when insufficient.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

adhx

Free

Read public X/Twitter post URLs as structured evidence through the ADHX API. Use for relevant user-provided or research-discovered x.com, twitter.com, or adhx.com links. ADHX does not search X, and long-form Article content may be incomplete.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Design, review, or report a measured performance comparison. Use for benchmark methodology, speedup or regression claims, and performance-based choices; not generic performance discussion, ordinary dependency bumps, local renames, or prose edits.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Trace what an actual code change could break beyond its diff when interfaces, serialized data, database schemas, configuration, caches, lifecycle ordering, or cross-language consumers are involved. Use for explicit impact analysis; not local renames, prose edits, ordinary dependency bumps, or generic architecture discussion.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Plan or implement retirement of a system, API, feature, persisted configuration, or database shape. Use for compatibility cutovers, explicit deprecation review, or an explicit unreleased replacement decision, including determining whether consumers or data exist; not ordinary dependency bumps, local renames, prose edits, or generic architecture discussion.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.

The English summary is being prepared. Showing the original description.

bioinformatist/codex-base9Updated Oct 16, 2026

See all skills by bioinformatist

Report a problem with this skill