Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Enforces documentation-first code generation to prevent LLM hallucination bugs. Before writing any code, it loads relevant docs, extracts actual API signatures, and validates the output against them. Works for API usage, configuration files, and feature implementation.
Code generators that rely on training data alone will hallucinate method names and parameters; this skill forces every generation step to reference live documentation instead.
When to use it
- Generating code for an unfamiliar third-party API
- Writing configuration files for a new tool or framework
- Updating code after a library releases breaking changes
- Implementing a feature with an SDK you haven't used before
- Verifying that a method signature hasn't been renamed or removed
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Write a Python script that uses the requests library to fetch paginated API results
- 1Fetches the official requests library documentation via web_fetch
- 2Extracts method signatures for Session, get, and response handling
- 3Generates Python code using exact parameter names and return types from docs
- 4Validates generated code against the extracted signatures
- 5Returns code with documentation source references and validation status
Validated Python script with inline doc source references and confirmed API signatures
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.