# Official Source Check

> Use for version-sensitive framework, library, SDK, or platform behavior: upgrades, deprecations, current APIs.

- Skill: `kreek/official-source-check` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add kreek/official-source-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kreek/official-source-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: kreek (https://skillmd.com/u/kreek)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kreek/official-source-check

---


# Official Source Check

## Iron Law

`MODEL MEMORY IS A HINT, NOT EVIDENCE, FOR VERSION-SENSITIVE BEHAVIOR.`

## When to Use

- Implementation depends on current external framework, library, runtime,
  browser, SDK, cloud, or platform behavior that the repo does not already
  prove.
- The user asks for current, official, documented, or verified
  implementation.

## When NOT to Use

- Project-local logic with tests and no external API dependency.
- Stable language syntax covered by the compiler, linter, or type checker.
- Emergency mitigation where the user accepts unverified risk.

## Rules

1. Find the local version first: manifests, lockfiles, imports, generated
   clients, schemas, config, CI images. Report its absence if none exists.
2. Check the narrow source of truth for the exact pattern: official docs,
   release notes, migration guide, standards spec, or provider SDK
   reference. Official sources beat blog posts.
3. Surface conflicts between source guidance and local convention. Use the
   smallest source-compatible implementation.
4. When source guidance alone does not prove runtime behavior, prove it with
   `proof`.
5. In the final claim, name the source checked, or mark the claim unverified.

## Tripwires

| Trigger | Do this instead | False alarm |
| --- | --- | --- |
| "I know this API" | Check the local version and the source of truth. | Project-local helper with tests. |
| "The docs are too broad" | Check the narrow API, migration, or release-note page. | Offline task where the user accepts unverified output. |
| "Existing code does it this way" | Check whether the pattern is still supported before copying it. | Repo policy pins an older supported pattern. |
| "I'll cite a blog post" | Use official docs, standards, release notes, or provider references. | The project owns the library being edited. |

## Handoffs

- `proof`: runtime evidence behind source guidance.
- `documentation`: capture the checked source for maintainers when asked.