developer-docs

Agent Skills › odysseus-dev/odysseus › developer-docs

developer-docs

GitHub

在开发实现过程中，查找、阅读并应用权威开发者文档。用于解答库、框架或 API 的使用问题，确保基于官方文档而非记忆进行实现，并提供版本特定的准确指导。

resources/skills/dev/developer-docs/SKILL.md odysseus-dev/odysseus

Trigger Scenarios

询问库、框架或 API 的使用方法实现依赖特定版本行为需要确认官方文档中的 API 细节

Install

npx skills add odysseus-dev/odysseus --skill developer-docs -g -y

More Options

Non-standard path

npx skills add https://github.com/odysseus-dev/odysseus/tree/dev/resources/skills/dev/developer-docs -g -y

Use without installing

npx skills use odysseus-dev/odysseus@developer-docs

指定 Agent (Claude Code)

npx skills add odysseus-dev/odysseus --skill developer-docs -a claude-code -g -y

安装 repo 全部 skill

npx skills add odysseus-dev/odysseus --all -g -y

预览 repo 内 skill

npx skills add odysseus-dev/odysseus --list

SKILL.md

Frontmatter

{
    "name": "developer-docs",
    "tags": [
        "docs",
        "documentation",
        "api",
        "software-development"
    ],
    "owner": "",
    "source": "builtin",
    "status": "published",
    "created": "2026-08-18T00:00:00Z",
    "version": "1.0.0",
    "category": "dev",
    "confidence": 1,
    "description": "Find, read, and apply authoritative developer documentation during implementation"
}

When to Use

Use when the user asks how a library, framework, API, protocol, CLI, or SDK works, or when implementation depends on version-specific behavior. Prefer this skill over guessing from memory.

Procedure

Identify the exact product, package, version, and task. Ask one focused clarification only when the target is genuinely ambiguous.
Prefer the vendor's or project's primary documentation, source repository, release notes, and API reference. Use a general search only to locate those sources.
Read the relevant page or reference section, then apply the documented behavior to the user's codebase and active workspace.
Separate documented facts from inference, and call out version or environment assumptions.
For code changes, add a focused regression test for the documented contract and run it before reporting completion.

Pitfalls

Do not present search snippets, stale cached knowledge, or a third-party tutorial as authoritative when primary documentation is available.
Do not silently mix instructions from different major versions.
Do not claim an API or option exists without confirming it in the relevant reference.
Do not use web search for a local project task when the active workspace and local tools can answer it.