DOWNLOADABLE CODEX SKILL · v1.0.0
Verify product and technical claims against current first-party documentation.
By Abdessalam · Updated
THE WORKFLOW
Verify product and technical claims against current first-party documentation. It keeps the work tied to evidence and the project’s actual constraints.
The user asks to fact-check a draft, refresh claims, or establish source support. Download the package, inspect its instructions, and adapt its review notes to the project.
EXAMPLE REQUEST
$aboutcodex-primary-source-check Fact-check this Codex plugin guide against current OpenAI documentation.A claim-to-source check and corrected copy with visible uncertainty.
Inspect the extracted package first. For a local project, place the skill folder here:
.agents/skills/aboutcodex-primary-source-check/SKILL.mdOpen the project and inspect the Skills sidebar to locate the skill by name. Follow the skill controls available in your current desktop application.
Open the project in Codex CLI. Use /skills or $aboutcodex-primary-source-check to select the skill explicitly.
Open the project in the Codex IDE extension. Use /skills or $aboutcodex-primary-source-check to select the skill explicitly.
Verify discovery: locate the exact skill name before starting. If missing, check the folder, SKILL.md filename, and name/description frontmatter, then restart the client.
After selecting the skill, use this inspection request:
Read the aboutcodex-primary-source-check skill. Explain its purpose, inputs, and boundaries. Do not edit files or run its workflow yet.Documentation-based guidance, checked September 10, 2026. Client discovery was not independently tested here. OpenAI’s skill documentation. Troubleshoot installation
aboutcodex-primary-source-check/SKILL.md1 KBaboutcodex-primary-source-check/references/NOTES.md453 Baboutcodex-primary-source-check/LICENSE.txt1 KB---
name: "aboutcodex-primary-source-check"
description: "Verify product and technical claims against current first-party documentation. Use when the user asks to fact-check a draft, refresh claims, or establish source support."
---
# Check claims against primary sources
Verify product and technical claims against current first-party documentation.
## Workflow
1. Extract claims that are specific, update-sensitive, quantitative, or central to the reader decision.
2. Find the closest current primary source: official documentation, release notes, repository, standard, or original paper.
3. Record whether each source supports, narrows, contradicts, or does not address the claim.
4. Revise wording to match the available evidence and attach links near the supported claim.
5. Mark inferences as inferences and preserve unresolved uncertainty instead of filling gaps.
Read `references/NOTES.md` before finalizing the work. Follow project instructions and the user's authorized scope. Use available evidence, label assumptions, and never report a check as passing unless it actually ran.
## Deliverable
A claim-to-source check and corrected copy with visible uncertainty. State material limitations and link to changed files or rendered evidence when available.
A primary source can still omit edge cases; this is not independent product testing.
Structure checked · 2026-09-10
Required frontmatter, folder layout, file inventory, validator run, and generated ZIP round-trip checked. Workflow behavior has not been independently evaluated.
Package checks confirm file structure. They do not establish that a skill works well on every task.
1.0.0 — Initial instruction-only release with supporting review notes.
Progress stays in this browser. No account needed.
Added interface-specific guidance and a read-only inspection request. The downloadable package is unchanged.
What to do: No re-download needed for this documentation update. Inspect the current version and compare your local changes before replacing a skill.
This log starts with the first recorded review; it is not a reconstruction of earlier revisions.
THE ABOUTCODEX BRIEFING
One workflow to try, one change explained, and one resource to keep. Planned weekly.
Read the sample issue ↗Confirm your email to join. Unsubscribe anytime through a delivered newsletter. Privacy policy.