원클릭으로 Manus에서 모든 스킬 실행

verify-this

스타2,198

포크170

업데이트2026년 5월 28일 16:57

Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

cursor

cursor/plugins

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Verify This

Verification is not a recap. It proves or disproves a specific claim with repeatable evidence.

When To Use

The user asks "verify this", "prove it works", "did this fix it", or "show me the evidence".
A bug fix needs a before/after repro.
A UI, CLI, API, performance, or memory claim needs measurement.
A test passes but the user-visible behavior still needs confirmation.

Do not use this for vague claims like "the code is cleaner". Ask for a measurable claim first.

Workflow

Restate the claim in falsifiable form: condition, metric, and threshold.
Pick the smallest local surface that can disprove it.
Capture a baseline from the old state: merge base, parent commit, failing branch, or current broken repro.
Capture treatment from the changed state with the same command, data, warmup, and environment.
Compare raw artifacts: numbers, screenshots, terminal transcripts, HTTP responses, profiles, heap snapshots, or test output.
Return exactly one verdict: VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

Local Surfaces

Code behavior: focused unit/integration tests or a minimal repro script.
CLI/TUI behavior: control-cli, terminal transcript, or demo recording.
UI behavior: control-ui, screenshots, accessibility snapshots, or browser traces.
API behavior: local HTTP/RPC request and response diff.
Performance: same-machine baseline/treatment timings or CPU profiles.
Memory: heap snapshots before and after the suspected operation.

Artifact Layout

When safe to write artifacts:

/tmp/verify-this/<claim-slug>/
├── claim.md
├── timeline.md
├── baseline/
├── treatment/
├── diff/
└── verdict.md

If artifacts may contain sensitive code, prompts, screenshots, HTTP bodies, or heap data, keep only the minimal inline evidence unless the user agrees to disk storage.

Verdict Rules

VERIFIED: baseline and treatment differ in the predicted direction, by the claimed threshold, with no obvious confound.
NOT VERIFIED: the behavior is unchanged, moves the wrong way, or misses the threshold.
INCONCLUSIVE: no valid baseline, noisy signal, failed measurement, or an environment difference invalidates the comparison.

Output

Use this shape:

VERIFIED | NOT VERIFIED | INCONCLUSIVE
Claim: <falsifiable claim>

Evidence:
<metric/artifact>: baseline=<...>, treatment=<...>, delta=<...>, threshold=<...>

Reasoning:
<one tight paragraph naming the evidence and any confounds>

Do not soften a negative result. A clear NOT VERIFIED is useful.

이 저장소의 다른 Skills

같은 저장소

reproduce-and-fix-issues

cursor/plugins

Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.

2026-06-242.2k

setup-benny

cursor/plugins

Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.

2026-06-242.2k

triage-issue-reports

cursor/plugins

Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.

2026-06-242.2k

blast-radius

cursor/plugins

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

2026-06-172.2k

recall

cursor/plugins

Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.

2026-06-172.2k

poteto-mode

cursor/plugins

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

2026-06-142.2k

Verify This

Verification is not a recap. It proves or disproves a specific claim with repeatable evidence.

When To Use

The user asks "verify this", "prove it works", "did this fix it", or "show me the evidence".

A bug fix needs a before/after repro.

A UI, CLI, API, performance, or memory claim needs measurement.

A test passes but the user-visible behavior still needs confirmation.

Do not use this for vague claims like "the code is cleaner". Ask for a measurable claim first.

Workflow

Restate the claim in falsifiable form: condition, metric, and threshold.

Pick the smallest local surface that can disprove it.

Capture a baseline from the old state: merge base, parent commit, failing branch, or current broken repro.

Capture treatment from the changed state with the same command, data, warmup, and environment.

Compare raw artifacts: numbers, screenshots, terminal transcripts, HTTP responses, profiles, heap snapshots, or test output.

Return exactly one verdict: VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

Local Surfaces

Code behavior: focused unit/integration tests or a minimal repro script.

CLI/TUI behavior: control-cli, terminal transcript, or demo recording.

UI behavior: control-ui, screenshots, accessibility snapshots, or browser traces.

API behavior: local HTTP/RPC request and response diff.

Performance: same-machine baseline/treatment timings or CPU profiles.

Memory: heap snapshots before and after the suspected operation.

Artifact Layout

When safe to write artifacts:

/tmp/verify-this/<claim-slug>/ ├── claim.md ├── timeline.md ├── baseline/ ├── treatment/ ├── diff/ └── verdict.md

If artifacts may contain sensitive code, prompts, screenshots, HTTP bodies, or heap data, keep only the minimal inline evidence unless the user agrees to disk storage.

Verdict Rules

VERIFIED: baseline and treatment differ in the predicted direction, by the claimed threshold, with no obvious confound.

NOT VERIFIED: the behavior is unchanged, moves the wrong way, or misses the threshold.

INCONCLUSIVE: no valid baseline, noisy signal, failed measurement, or an environment difference invalidates the comparison.

Output

Use this shape:

VERIFIED | NOT VERIFIED | INCONCLUSIVE Claim: <falsifiable claim> Evidence: <metric/artifact>: baseline=<...>, treatment=<...>, delta=<...>, threshold=<...> Reasoning: <one tight paragraph naming the evidence and any confounds>

Do not soften a negative result. A clear NOT VERIFIED is useful.

name	verify-this
description	Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.