New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Audit Verify Explain Grade 5

by nirholas in nirholas/three.ws

Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language.

Apache-2.0Auto-check passedWriting & Content

Install Audit Verify Explain Grade 5

skills CLI
$ npx skills add nirholas/three.ws --skill audit-verify-explain-grade-5 -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nirholas/three.ws audit-verify-explain-grade-5 --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nirholas/three.ws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/third_party/designcode-agent-skills/agent-skills/codex/audit-verify-explain-grade-5 .claude/skills/audit-verify-explain-grade-5 && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
audit-verify-explain-grade-5
GitHub stars
227
Used in
1 other repo
Token cost
~920 tokens
SKILL.md length
476 words
Files
7
Skills in repo
92
Repo updated
First seen
Licence
Apache-2.0

At a glance

Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language.

  • Works in 3 steps: Audit → Verify → Explain Simply
  • The user asks to review
  • SKILL.md covers Core Rule, Workflow, Explanation Standards and Output Rules
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Audit Verify Explain Grade 5 is an agent skill from nirholas/three.ws. Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language. Use when the user asks to review, audit, check, verify, explain a change, explain a fix, summarize test results, validate whether something works, or translate technical findings into plain language for non-technical readers.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files (for example `agents/openai.yaml`, `demo/PROMPT.md` and `demo/expected-output.md`).

It sits in Writing & Content, covering Plain language and style rules and Fact-checking and source verification. The repository describes itself as: Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web… The licence is Apache-2.0.

When your agent uses it

  • The user asks to review
  • Explain a change
  • Summarize test results
  • Validate whether something works

Example prompts

  • “/audit-verify-explain-grade-5”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Audit
  2. Verify
  3. Explain Simply

What it can do on your machine

Read from SKILL.md and the folder at commit ddf6e49. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Audit Verify Explain Grade 5 loads about 920 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 476 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~89
When it runs · the whole SKILL.md, loaded when a task matches
~920

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nirholas/three.ws at commit ddf6e49, republished under its Apache-2.0 licence (© nirholas). 476 words, ~920 tokens.

Download SKILL.mdSave it as .claude/skills/audit-verify-explain-grade-5/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
audit-verify-explain-grade-5
description
Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language. Use when the user asks to review, audit, check, verify, explain a change, explain a fix, summarize test results, validate whether something works, or translate technical findings into plain language for non-technical readers.

Audit, Verify, Explain

Core Rule

Treat every answer as three jobs:

  1. Audit what changed or what is being claimed.
  2. Verify it with direct evidence.
  3. Explain it like the reader is smart but new to the topic.

Do not skip verification when local files, commands, logs, tests, screenshots, or source data are available. Do not pretend something was verified if it was only inferred.

Workflow

1. Audit

Start by finding the real source of truth:

  • For code changes, inspect the diff, touched files, related call sites, and existing tests.
  • For bug fixes, identify the before/after behavior and the user-facing path.
  • For performance claims, separate measured evidence from likely improvement.
  • For release or app behavior, check the packaged/running artifact when possible.
  • For documents or content, compare the user request against the actual produced artifact.

Look for:

  • obvious bugs or regressions
  • missing edge cases
  • stale assumptions
  • unverified claims
  • mismatches between implementation and user intent
  • risks that a grade-5 explanation might accidentally hide
2. Verify

Prefer evidence in this order:

  1. Automated tests, builds, linters, typechecks, or validators.
  2. Running the actual app or workflow.
  3. Logs, process checks, screenshots, generated artifacts, or live output.
  4. Static code inspection when execution is impractical.
  5. Clearly labeled inference when nothing stronger is available.

When verification fails, report the blocker and what it means. When verification is partial, say exactly what was and was not checked.

For performance work, avoid overclaiming. Say "this removes repeated work" only when the code clearly does so. Say "should improve" only when no timing trace was captured. Say "measured faster" only when before/after measurements exist.

Show full SKILL.md (208 more words)Show less
3. Explain Simply

Use grade-5 language without talking down to the user:

  • Use short sentences.
  • Define technical terms in plain words.
  • Use one simple analogy only if it genuinely helps.
  • Say what changed, why it matters, and how to test it.
  • Keep important caveats visible.

Prefer this shape:

markdown
What changed:
- ...

Why it matters:
- ...

How I verified it:
- ...

What is still not proven:
- ...

For very small answers, use a short paragraph instead of forcing headings.

Explanation Standards

Translate technical ideas like this:

  • "cache" -> "remember the answer so we do not ask the same question again"
  • "metadata" -> "small facts about a file, like size or modified date"
  • "regression" -> "something that used to work but broke"
  • "artifact" -> "the real file or app that was created"
  • "static inspection" -> "reading the code without running it"

Do not say "everything works" unless the full workflow was tested. Say "the checked parts work" when verification covered only part of the system.

Output Rules

Lead with the answer. Keep the tone calm and clear.

Include file paths, commands, commit hashes, test names, or log snippets when they are the evidence. Keep them brief.

Separate facts from judgment:

  • Fact: "The tests passed."
  • Judgment: "That gives confidence in the timeline planner, but not the full editor UI."

End with the most useful next test only when another test would materially improve confidence.

© nirholas, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files in third_party/designcode-agent-skills/agent-skills/codex/audit-verify-explain-grade-5 of nirholas/three.ws.

  • SKILL.md
  • agents/openai.yaml
  • demo/PROMPT.md
  • demo/expected-output.md
  • demo/index.html
  • demo/input.md
  • demo/preview.jpg

Open the folder on GitHubat commit ddf6e49

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in nirholas/three.ws, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Audit Verify Explain Grade 5 next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Audit Verify Explain Grade 5 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Verify Explain Grade 5 this skillnirholas/three.ws2271 repos~920Automated safety check: PassApache-2.0
Eval Contentindranilbanerjee/digital-marketing-pro8551 repos~2.3kAutomated safety check: PassMIT
JavaScript Concept Fact Checkerleonardomso/33-js-concepts67k1 repos~5kAutomated safety check: PassMIT
Asd Ste100danyuchn/asd-ste100-skill4k—~4.1kAutomated safety check: PassMIT
Simple Issue Descriptionevery-app/open-seo23k1 repos~1.2kAutomated safety check: PassMIT
Ponytail AuditDietrichGebert/ponytail158k—~1.3kAutomated safety check: PassMIT

Similar skills

  • Eval Content

    indranilbanerjee/digital-marketing-pro

    Score marketing content across six dimensions — content quality, brand voice, hallucination risk, claim verification, structure, readability — into a composite score with letter grade, a…

    855 GitHub starsUsed in 1 repo~2.3k tokens
    Writing & ContentAuto-check passed

  • JavaScript Concept Fact Checker

    leonardomso/33-js-concepts

    Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.

    67k GitHub starsUsed in 1 repo~5k tokens
    Writing & ContentAuto-check passed

  • Asd Ste100

    danyuchn/asd-ste100-skill

    A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…

    4k GitHub stars~4.1k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed

  • Simple Issue Description

    every-app/open-seo

    Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior.

    23k GitHub starsUsed in 1 repo~1.2k tokens
    Writing & ContentAuto-check passed

  • Ponytail Audit

    DietrichGebert/ponytail

    Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.

    158k GitHub stars~1.3k tokensUpdated today
    Writing & ContentAuto-check passed

  • Technical Writing Standard

    cursor/plugins

    Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed

More from nirholas/three.ws

All 92 skills in this repo

  • Add Shader Cursor Trail

    nirholas/three.ws

    Add the Shaders WebGPU mouse effect used for the Tidal Commons hero: a white twinkling halftone cursor trail driven by ChromaFlow, masked through a DotGrid, finished with chromatic ripples and film…

    227 GitHub starsUsed in 1 repo~760 tokens
    Auto-check passed

  • Publish Project To GitHub

    nirholas/three.ws

    Package a finished local project into an intentional GitHub repository, create a strong README and visual preview, push it safely, configure a public GitHub Pages URL when the project is compatible…

    227 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check: notes

  • Audit Reference Originality

    nirholas/three.ws

    Audit a website or digital experience against its supplied source references for originality and plagiarism risk.

    227 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • Build Daily Inspiration Sites

    nirholas/three.ws

    Turn a completed daily UI inspiration capture into exactly five original landing-page builds, one per separate Codex task, using Sites.

    227 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Write Like Meng On X

    nirholas/three.ws

    Write, rewrite, review, or continuously refine X/Twitter posts in Meng To's current voice using his deduplicated authored-post corpus, personal and product context, shared resources, and Content…

    227 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Browser Video Recording

    nirholas/three.ws

    Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography…

    227 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

Categories

Questions about Audit Verify Explain Grade 5

What does Audit Verify Explain Grade 5 do?

Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language. ws. Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language.

When should I use Audit Verify Explain Grade 5?

Audit Verify Explain Grade 5 fits situations like: the user asks to review; explain a change; summarize test results; validate whether something works.

How do I install Audit Verify Explain Grade 5 in Claude Code?

Run `npx skills add nirholas/three.ws --skill audit-verify-explain-grade-5 -a claude-code`. Or copy the skill folder (third_party/designcode-agent-skills/agent-skills/codex/audit-verify-explain-grade-5 in nirholas/three.ws) into .claude/skills/audit-verify-explain-grade-5 in your project. Claude Code loads it when a task matches its description.

How do I install Audit Verify Explain Grade 5 in Codex?

Run `npx skills add nirholas/three.ws --skill audit-verify-explain-grade-5 -a codex`. Or copy the skill folder (third_party/designcode-agent-skills/agent-skills/codex/audit-verify-explain-grade-5 in nirholas/three.ws) into .agents/skills/audit-verify-explain-grade-5 in your project. Codex loads it when a task matches its description.

Can I use Audit Verify Explain Grade 5 in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nirholas/three.ws --skill audit-verify-explain-grade-5 -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-verify-explain-grade-5, .gemini/skills/audit-verify-explain-grade-5, .github/skills/audit-verify-explain-grade-5 and .opencode/skills/audit-verify-explain-grade-5 in your project.

What does Audit Verify Explain Grade 5 need to run?

SKILL.md names no scripts, command-line tools or credentials: Audit Verify Explain Grade 5 is instructions for the agent only.

Does Audit Verify Explain Grade 5 access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Audit Verify Explain Grade 5 safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Audit Verify Explain Grade 5 use?

Audit Verify Explain Grade 5 is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Verify Explain Grade 5 use?

About 920 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Audit Verify Explain Grade 5?

Skills that share tags, products or a category with Audit Verify Explain Grade 5: Eval Content (indranilbanerjee/digital-marketing-pro, 855 stars), JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars), Asd Ste100 (danyuchn/asd-ste100-skill, 4k stars) and Simple Issue Description (every-app/open-seo, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Verify Explain Grade 5?

nirholas (a GitHub user) maintains it in nirholas/three.ws, which has 227 GitHub stars. The repository holds 92 skills in this directory. The repository was last updated on October 8, 2026.

Source: nirholas/three.ws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.