no-invented-code
/no-invented-code
Use whenever writing or suggesting code that calls a function, file, module, package, CLI flag, config key, environment variable, or API endpoint — especially third-party libraries, SDKs, or framework features. Prevents hallucinated APIs by checking the repo and docs before using anything.
- Author
- geadalfa ↗
- Repository
- OverhaulMyAgent ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use whenever writing or suggesting code that calls a function, file, module, package, CLI flag, config key, environment variable, or API endpoint — especially third-party libraries, SDKs, or framework features. Prevents hallucinated APIs by checking the repo and docs before using anything.
Original author description
Use whenever writing or suggesting code that calls a function, file, module, package, CLI flag, config key, environment variable, or API endpoint — especially third-party libraries, SDKs, or framework features. Prevents hallucinated APIs by checking the repo and docs before using anything.
How it works
- Inside the project
- Third-party libraries
- Adding a dependency
- Commands, flags, config keys, env vars
- Red flags — stop and check
- Memory
SKILL.md preview
--- name: no-invented-code description: Use whenever writing or suggesting code that calls a function, file, module, package, CLI flag, config key, environment variable, or API endpoint — especially third-party libraries, SDKs, or framework features. Prevents hallucinated APIs by checking the repo and docs before using anything. --- # No Invented Code Every identifier you use must exist. If you have not seen it, check it — or say you have not. ## Inside the project Before calling or importing something from the codebase: - Search for it (`grep -rn`, file search, IDE symbols). Confirm the **exact** name, signature, and export. - Read the file it lives in. Check argument order, return type, and whether it is async. - Before referencing a file path, confirm the file exists. - Use the project's existing helpers instead of inventing new ones with similar names. ## Third-party libraries - Check the **installed version** first: `package.json` / lockfile, `requirements.txt` / `pyproject.toml`, `go.mod`, `Cargo.toml`. APIs change between major versions. - Verify the API against one of: the library source in `node_modules` / site-packages / module cache, official docs for that version (use web search when available), or the project's existing usage. - If you cannot verify, say so: *"I believe the option is `X` in v4, but I could not confirm it — please check."* ## Adding a dependency - Confirm the package name exists and is the right one (watch for look-alike/typosquat names). - Prefer what the project already uses. Mention every new dependency in your report. ## Commands, flags, config keys, env vars - Check `--help`, the tool's docs, or existing scripts/config before using a flag or key. - Never invent environment variables; find where the code reads them. ## Red flags — stop and check - "This library probably has a method for that." - A function name that sounds right but you have not seen in this codebase. - Copying a pattern from a different framework or an older major version. - Mixing APIs from two different SDKs. ## Memory If you discover a version-specific gotcha (renamed API, breaking change, wrong docs), save it with `mem_save` so it is not rediscovered next session.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · geadalfa/OverhaulMyAgent | 90 | MIT |
| fvkmizel/soulkeeper | 90 | MIT |
Database snapshot: 13.11.2026 · package version 56491cd85bc3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100use-external-api
Use a library, SDK, CLI or web API correctly by checking the installed version and real docs instead of relying on memory. Use this whenever code calls a third-party package or service, when you are unsure of a method or parameter name, or when an API call fails. It prevents… - 100ai-read-docs
Use when the work depends on versioned or external behaviour — adding a package, writing setup or config, integrating an SDK or a paid API, debugging a framework change — or on anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs,… - 100fact-checker
Anti-hallucination discipline for any code that names an external symbol you aren't certain exists — a library function, method, config key, package version, CLI flag, env var, or endpoint. Before you call it, cite it, or import it, confirm it's real: grep the codebase, read the… - 100find-docs
Retrieve authoritative, up-to-date documentation, API references, configuration details, and code examples for any developer technology (libraries, frameworks, languages, SDKs, APIs, CLI tools, cloud services) via the Context7 CLI. Use whenever answering technical questions or… - 100microsoft-code-reference
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated… - 100ctxhub-get-api-docs
Use this skill to get documentation for third-party APIs, SDKs, or libraries before writing code that uses them, so you have the latest accurate docs instead of stale training data. Triggers: any task like "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK",…