Direction Picker
nexu-io/open-design
Resolves the visual direction at the plan stage from the brief and design system, without asking the user.
Verify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts.
MITAuto-check passed
Install Verification Methodology
$ npx skills add magnus919/agent-skills --skill verification-methodology -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/agent-skills verification-methodology --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/verification-methodology .claude/skills/verification-methodology && rm -rf skills-srcUse ~/.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/
Install the "verification-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/verification-methodology into .claude/skills/verification-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-methodology", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/agent-skills/tree/main/verification-methodologyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/agent-skills --skill verification-methodology -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/agent-skills verification-methodology --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/verification-methodology .agents/skills/verification-methodology && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verification-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/verification-methodology into .agents/skills/verification-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-methodology", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill verification-methodology -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/agent-skills verification-methodology --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/verification-methodology .cursor/skills/verification-methodology && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verification-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/verification-methodology into .cursor/skills/verification-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-methodology", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/agent-skills.git --path verification-methodology--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/agent-skills --skill verification-methodology -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/agent-skills verification-methodology --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/verification-methodology .gemini/skills/verification-methodology && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verification-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/verification-methodology into .gemini/skills/verification-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-methodology", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/agent-skills verification-methodologyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/agent-skills --skill verification-methodology -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/verification-methodology .github/skills/verification-methodology && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verification-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/verification-methodology into .github/skills/verification-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-methodology", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/agent-skills --skill verification-methodology -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/agent-skills verification-methodology --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/verification-methodology .opencode/skills/verification-methodology && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verification-methodology" agent skill from https://github.com/magnus919/agent-skills/tree/main/verification-methodology into .opencode/skills/verification-methodology/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-methodology", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verification-methodology- GitHub stars
- 116
- Token cost
- ~2.1k tokens
- SKILL.md length
- 962 words
- Files
- 7 (incl. references)
- Skills in repo
- 130
- Repo updated
- First seen
- Licence
- MIT
At a glance
Verify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts.
- Works in 5 steps: Receive — restate the artifact, claim,… → Assess criteria — convert requirements… → Investigate — collect direct,… → …
- Exploratory research without pass/fail criteria
- SKILL.md covers The Verification Protocol, Source Fidelity, When not to use and Related Skills, plus 3 more sections
- Calls curl
What it does
Verification Methodology is an agent skill from magnus919/agent-skills. Verify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts. Use before declaring an artifact, implementation, or claim complete; do not use for exploratory research without pass/fail criteria.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `README.md`, `evals/evals.json` and `references/criteria-assessment.md`). Compatibility notes: No runtime dependency.
The repository describes itself as: Curated collection of AI agent skills for Hermes and other agent frameworks. The licence is MIT.
When your agent uses it
- Exploratory research without pass/fail criteria
Example prompts
- “/verification-methodology”
Requirements
- Compatibility (from SKILL.md): No runtime dependency.
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Receive — restate the artifact, claim, or implementation being verified and the decision it will support.
- Assess criteria — convert requirements into observable pass/fail conditions; identify what would disprove each claim.
- Investigate — collect direct, reproducible evidence from the source named by the request and record commands, source locations, or source…
- Decide — mark each criterion passed, failed, blocked, or not applicable. Do not convert missing evidence into a pass.
- Report — use the verdict template to distinguish verified facts, assumptions, and remaining work.
What it can do on your machine
Read from SKILL.md and the folder at commit c545c2b. 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
Shell commands in SKILL.md call:
curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
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.
Compatibility
No runtime dependency.
From compatibility in the SKILL.md frontmatter.
Context cost
Verification Methodology loads about 2.1k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 962 words of instructions outside code blocks.
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 magnus919/agent-skills at commit c545c2b, republished under its MIT licence (© magnus919). 962 words, ~2,106 tokens.
Download SKILL.mdSave it as
.claude/skills/verification-methodology/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- verification-methodology
- description
- Verify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts. Use before declaring an artifact, implementation, or claim complete; do not use for exploratory research without pass/fail criteria.
- compatibility
- No runtime dependency.
- license
- MIT
- metadata.source_repo
- https://github.com/magnus919/hermes-profiles
- metadata.source_commit
- 867a555
Verification Methodology
Pass/fail assessment against pre-defined criteria.
The Verification Protocol
- Receive — restate the artifact, claim, or implementation being verified and the decision it will support.
- Assess criteria — convert requirements into observable pass/fail conditions; identify what would disprove each claim.
- Investigate — collect direct, reproducible evidence from the source named by the request and record commands, source locations, or source URLs. Own this collection when the source is accessible: do not ask the user to relay evidence you can retrieve yourself. Ask only for access you genuinely lack.
- Decide — mark each criterion passed, failed, blocked, or not applicable. Do not convert missing evidence into a pass.
- When verification is split across lanes, no lane's PASS is the gate verdict. Wait for every required lane and reconcile conflicts before synthesis.
- A later source-fidelity BLOCK supersedes an earlier prose, rendering, or checklist PASS for the same artifact hash. Immediately label earlier PASS packets as superseded so downstream workers cannot mistake them for the current verdict.
- Pattern scans and internal consistency cannot substitute for checking factual transformations against the named primary source or source dossier.
- Report — use the verdict template to distinguish verified facts, assumptions, and remaining work.
Stop when every criterion has direct evidence or an explicit blocked/not-applicable verdict. Escalate when the criterion is ambiguous, evidence conflicts, or the required access is unavailable.
Source Fidelity
Treat the requested or configured local service as part of the verification criterion, not as an interchangeable topic label.
- Load the matching skill and use its documented executable or service path before adjacent integrations, generic web search, or public project sources.
- Use the path resolved by the skill itself. A missing global
PATHentry does not prove that a bundled executable is unavailable. - If the direct source fails, report the attempted command or endpoint and its exact failure. Do not silently substitute evidence from another source.
- Use a substitute only when the user requests broader context or explicitly accepts the fallback. Label substitute evidence as secondary and do not present it as the requested source's state.
Example: for “What’s new on Jellyfin?” in an environment with a configured Jellyfin skill and bundled CLI, query that server through the bundled CLI first. Home Assistant entities and public Jellyfin project activity answer different questions.
When not to use
Do not use this skill for open-ended exploration that has no artifact, claim, decision, or observable completion criterion. Use a research or discovery skill first, then return here when there is something falsifiable to verify.
Related Skills
- playwright — browser-based E2E checks as a verification instrument: authoring and running specs against the real UI boundary.
- documents — producing verification reports or evidence packets as PDF/Word/Excel/PowerPoint deliverables.
Reference Files
| Reference | When to load |
|---|---|
references/criteria-assessment.md | You need to evaluate whether work meets completion criteria |
references/evidence-standards.md | You need to judge whether evidence supports the claims made |
references/magnus919-refine-to-ship-gate.md | You are running the Magnus919 Refine-to-Ship verifier gate — 12 criteria, editorial change verification, output structure |
references/verdict-template.md | You need to produce a structured pass/fail/hold verdict |
Magnus919 Refine-to-Ship Gate Criteria
12 criteria for the verifier profile. Each criterion maps to an observable, reproducible check.
Show full SKILL.md (442 more words)Show less
All 12 Criteria
| # | Criterion | How to Verify |
|---|---|---|
| 1 | Dash scan — zero em dash (U+2014), en dash (U+2013), horizontal bar (U+2015), or visible prose double-hyphen | search_files for [\u2014\u2013\u2015] and \-\-. Double-hyphens in YAML frontmatter delimiters are OK. |
| 2 | Fact-check — all methodology claims map to source; no fabricated numbers, chronology, or universal claims | Cross-reference article claims to source document sections. Search for \d+%, percent, average of, illustrative. Search for research proves, studies demonstrate. |
| 3 | Voice-check — Magnus fingerprint: conversational first-person, contractions, "But" pivots (not formal transitions), colons over semicolons, no consultant cadence | Search for Furthermore, Moreover, Nevertheless, Consequently, Therefore, not only.*but also, triplet parallelism. Count colons vs semicolons (should skew heavily toward colons). |
| 4 | Oxford commas, spelling, grammar — American English, Oxford commas in series, no spelling errors | Manual read of series. Check for consistent formatting. |
| 5 | No formulaic AI closing — zero "In conclusion", "To summarize", "In this article", generic motivational advice | search_files for In conclusion, Ultimately,, To summarize, In this article, In this post. |
| 6 | Methodology-first — personal frame ≤ ~10% of article; rest is methodology | Count paragraphs in frame vs body. |
| 7 | Human stake integrated — cognitive burden, expertise formation, transferred work, anti-surveillance, accountable authority | Verify dedicated section or dispersed coverage of all dimensions. |
| 8 | Privacy/anonymization — zero company identifiers, role titles, named people, source filename, proprietary domain examples | search_files for company name, product names, domain-specific terminology from source. |
| 9 | Frontmatter — title, slug, date, byline correct and value-identical to specification | read_file lines 1–11. |
| 10 | Links resolve — each distinct URL appears once at first meaningful mention; all return 200 | curl -s -o /dev/null -w "%{http_code}" each URL. Verify link text is at first meaningful mention. |
| 11 | Hugo build + routes — build exit 0; new route returns 200; old take-home-title route returns 404 | hugo --quiet && echo EXIT:$?. curl both routes. |
| 12 | No duplicate source bundle — single directory, single index.md; no stale *take-home* directories | ls the page bundle directory. find in content/posts for duplicate slug patterns. |
Parent-Requested Editorial Changes
When the parent profile specifies editorial changes during gate recovery, verify each one is present before proceeding with the full criteria scan:
| Change Type | Verification Method |
|---|---|
| Fabricated illustrative numbers removed | search_files for \d+%, percent, PRs? per, average of → zero hits |
| Tense correction | search_files for the exact parent-specified phrase |
| Closing replacement | search_files for the first and last sentence of the parent-specified closing |
Verdict Rules
- PASS: All 12 criteria met. Produce 00-index.md, 01-summary/verdict.md, 02-analysis/per-criteria-results.md.
- BLOCK: Any criterion fails. Produce gap-details.md with specific fix instructions. See
verifier-gate-recoveryskill for remediation patterns.
Output Structure
/private/tmp/verifier-gate/<slug>-refine/
00-index.md — verdict, links to artifacts
01-summary/verdict.md — per-criterion pass/fail table
02-analysis/
per-criteria-results.md — detailed evidence per criterion
gap-details.md — only if BLOCK, with remediation instructionsPortability
This skill is intentionally host-neutral. Use your agent's normal mechanisms to load the references, templates, and scripts listed here. Do not assume a particular profile system, task orchestrator, memory service, or response-handoff format.
© magnus919, MIT. 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 (references) in verification-methodology of magnus919/agent-skills.
- SKILL.md
- README.md
- evals/evals.json
- references/criteria-assessment.md
- references/evidence-standards.md
- references/source-index.md
- references/verdict-template.md
Open the folder on GitHubat commit c545c2b
Compare with similar skills
Verification Methodology 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verification Methodology this skillmagnus919/agent-skills | 116 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Direction Pickernexu-io/open-design | 100k | — | ~472 | Automated safety check: Warn | Apache-2.0 | |
| Frontend Design Directionaffaan-m/ECC | 276k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Direction Attributethedaviddias/Front-End-Checklist | 74k | — | ~534 | Automated safety check: Pass | MIT | |
| Benchmark Methodologyaffaan-m/ECC | 276k | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Evaluation Methodologywshobson/agents | 40k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Frontend Design Direction
affaan-m/ECC
Set an ECC-specific frontend design direction for production UI work.
Direction Attribute
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Set text direction for RTL languages.
Benchmark Methodology
affaan-m/ECC
Score a scoped competitor set into comparable profile cards: nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing…
Evaluation Methodology
wshobson/agents
PluginEval quality methodology, covering dimensions, rubrics, and scoring formulas.
Code Review Criteria
penpot/penpot
Code review criteria — the five review axes, core principles, severity format, and verdict for reviewing code changes.
More from magnus919/agent-skills
All 130 skills in this repoArtifact Pyramids
magnus919/agent-skills
Organize durable agent research outputs as summaries, analysis, and evidence dossiers.
Ascii City Engine
magnus919/agent-skills
Build portable, first-person colored ASCII city engines and small GIS-derived city packs.
Color Management
magnus919/agent-skills
Manage color workflows with ICC profiles, working spaces, gamut mapping, and color science.
Data Scientist
magnus919/agent-skills
A skill your agent uses for PhD-level expertise in data science, statistics, and machine learning: rigorous statistical analysis, experimental design, causal inference, advanced modeling, research…
Docker Compose
magnus919/agent-skills
Use Docker Compose to define, run, debug, and harden multi-container applications.
Fpga Development
magnus919/agent-skills
Design, review, simulate, and verify FPGA logic using explicit RTL contracts, clock and reset models, CDC analysis, timing constraints, and reproducible implementation evidence.
Questions about Verification Methodology
What does Verification Methodology do?
Verify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts. Verification Methodology is an agent skill from magnus919/agent-skills. Verify work against explicit criteria using direct, source-faithful evidence, reproducible checks, and clear verdicts.
When should I use Verification Methodology?
Verification Methodology fits situations like: exploratory research without pass/fail criteria.
How do I install Verification Methodology in Claude Code?
Run `npx skills add magnus919/agent-skills --skill verification-methodology -a claude-code`. Or copy the skill folder (verification-methodology in magnus919/agent-skills) into .claude/skills/verification-methodology in your project. Claude Code loads it when a task matches its description.
How do I install Verification Methodology in Codex?
Run `npx skills add magnus919/agent-skills --skill verification-methodology -a codex`. Or copy the skill folder (verification-methodology in magnus919/agent-skills) into .agents/skills/verification-methodology in your project. Codex loads it when a task matches its description.
Can I use Verification Methodology 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 magnus919/agent-skills --skill verification-methodology -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verification-methodology, .gemini/skills/verification-methodology, .github/skills/verification-methodology and .opencode/skills/verification-methodology in your project.
What does Verification Methodology need to run?
Going by SKILL.md and its folder, Verification Methodology needs the command-line tools its instructions call (curl). Compatibility (from SKILL.md): No runtime dependency..
Does Verification Methodology access the network?
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Verification Methodology 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 Verification Methodology use?
Verification Methodology is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verification Methodology use?
About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 783 tokens, read only when the agent opens those files.
What are the alternatives to Verification Methodology?
Skills that share tags, products or a category with Verification Methodology: Direction Picker (nexu-io/open-design, 100k stars), Frontend Design Direction (affaan-m/ECC, 276k stars), Direction Attribute (thedaviddias/Front-End-Checklist, 74k stars) and Benchmark Methodology (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verification Methodology?
magnus919 (a GitHub user) maintains it in magnus919/agent-skills, which has 116 GitHub stars. The repository holds 130 skills in this directory. The repository was last updated on October 8, 2026.
Source: magnus919/agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.