跳到正文
cccskills
免费在 GitHub 公开

audit-verify-explain-grade-5

Review changes or finished work, check claims against tests, logs, running software, or source files, and explain the findings in plain language. It separates verified facts from assumptions and makes incomplete checks and remaining uncertainty clear.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

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.

查看安装方法

适用场景

  • Verify a bug fix against actual behavior
  • Explain test results to nontechnical readers
  • Check the evidence behind performance claims
  • Compare a finished document with its requirements

包含的文件(7)

  • SKILL.md3.6 KB
  • agents/openai.yaml224 B
  • demo/expected-output.md266 B
  • demo/index.html3.9 KB
  • demo/input.md272 B
  • demo/preview.jpg83.0 KB
  • demo/PROMPT.md2.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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.

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:

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.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Build woven fabric in Three.js with visible threads, realistic sheen, seams, and thick hems. The skill covers folds that preserve texture proportions, light passing through thin cloth, and variations in dye and wear.

中文简介正在准备中。当前显示英语简介。

  • Creating backlit curtains
  • Differentiating linen, silk, and wool
  • Adding hems and stitches for close-up views
MengTo/Skills69272026年10月18日 更新

Build falling leaves in Three.js and similar 3D scenes, with visible front, edge, and back views as they tumble and drift. Coordinate wind, scene depth, camera-aware recycling, and performance checks for a convincing autumn effect.

中文简介正在准备中。当前显示英语简介。

  • Adding falling autumn leaves to a 3D scene
  • Coordinating leaf tumble, sideways drift, and wind
  • Managing leaves around buildings and camera movement
MengTo/Skills69272026年10月18日 更新

Add coordinated seasonal transitions to an existing 3D scene. Blend foliage, lighting, sky, ground, snow, and particles from one shared state while preserving camera controls and interactions, so the same place remains recognizable throughout spring, summer, fall, and winter.

中文简介正在准备中。当前显示英语简介。

  • Add a four-season selector to an outdoor 3D scene
  • Show seasonal changes in an architectural walkthrough
  • Coordinate foliage, sunlight, sky, and ground appearance
MengTo/Skills69272026年10月18日 更新

Create or integrate detailed 3D models with smooth outlines and believable edges for close-up views. Prepare lower-detail versions for distant viewing, prioritize loading, and measure rendering costs in the actual scene.

中文简介正在准备中。当前显示英语简介。

  • Creating a detailed 3D model for close-up views
  • Replacing visibly faceted curves with smoother geometry
  • Preparing detailed architectural assets for rendering
MengTo/Skills69272026年10月18日 更新

Prepare detailed 3D materials that remain clear in close-up views. The skill guides texture resolution, physically based material maps, surface mapping, filtering, and progressive loading while checking download size and GPU memory use.

中文简介正在准备中。当前显示英语简介。

  • Prepare wood, stone, and fabric materials for close-up views
  • Fix texture seams, grain direction, and normal map orientation
  • Preserve floor and foliage detail at oblique or distant views
MengTo/Skills69272026年10月18日 更新

Create realistic metal surfaces in Three.js by combining structured reflections, studio lighting, scratches, fingerprints, and beveled edges. Includes polished, brushed, and aged finishes for objects such as tools, rings, and metal product parts.

中文简介正在准备中。当前显示英语简介。

  • Fixing metal that looks like gray plastic
  • Creating polished or brushed metal finishes
  • Adding patina and worn edges
MengTo/Skills69272026年10月18日 更新

查看 MengTo 的全部技能

报告此技能的问题