extract-visa-rules

Extract visa-policy rules for (nationality → destination) pairs into committed, schema-validated JSON artifacts, using a Claude subscription (Claude Agent SDK) or OpenAI Codex — not a metered gateway key. Use when broadening visa data coverage (EPIC-005 slice 5), when a human says "run the visa extraction" / "fetch visa rules for X", or on a schedule. Produces a reviewable PR; the diff review is the factual-accuracy gate. Never runs at request time. SPEC-019 / ADR 062.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured instructional skill with executable commands, an explicit human-gated accuracy checkpoint, and clear guardrails. The only blemish is mild redundancy between the intro, description, and Guardrails sections.

Suggestions

Tighten the opening paragraph so it does not restate the frontmatter description verbatim; the runtime-app-makes-no-AI point already appears in the description.

De-duplicate the 'offline / never at request time' guidance, which appears in both 'When to use' and 'Guardrails' — keep it in one place and cross-reference.

Consider replacing EPIC/ADR/SPEC tokens in the body (or at least the description) with a one-line plain-English pointer so the skill stays self-contained without internal jargon.

Dimension	Reasoning	Score
Conciseness	Lean and efficient, assuming Claude's competence — no padding explaining what a visa, JSON, or PR is — but the opening paragraph partially restates the description and the Guardrails section lightly overlaps 'When to use', leaving minor trims.	4 / 5
Actionability	Fully executable guidance: concrete commands (`pnpm visa:schema`, `pnpm visa:extract --runner=claude JPN VNM…`, `export CLAUDE_CODE_OAUTH_TOKEN=…`, `codex login`), exact output file paths, and a named commit-message format cover the common cases.	5 / 5
Workflow Clarity	Five clearly sequenced steps with an explicit validation gate (step 3: 'Review the JSON diff — this is the accuracy gate'), a fix/retry feedback loop ('Address every sanity warning'), and Guardrails covering the destructive/batch commit operation.	5 / 5
Progressive Disclosure	Well-organized into clear sections (When to use, Prerequisites, Steps, Guardrails) with no nested references; referenced paths (schema, seed dir) are real one-level-deep project files, and the skill needs no separate bundle files.	5 / 5
	Total	19 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that clearly states capabilities, triggers, and boundaries in third person. Minor room to add natural synonyms and trim internal-jargon references, but it is otherwise comprehensive and distinct.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Extract visa-policy rules for (nationality → destination) pairs into committed, schema-validated JSON artifacts' and 'Produces a reviewable PR; the diff review is the factual-accuracy gate' — with comprehensive, specific coverage.	5 / 5
Completeness	Explicitly answers both what (extract rules into schema-validated JSON, produce a reviewable PR) and when via a clear 'Use when…' clause with concrete trigger phrases ('broadening visa data coverage', 'when a human says…', 'on a schedule').	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say — 'run the visa extraction', 'fetch visa rules for X', 'on a schedule', 'broadening visa data coverage' — but leans on some technical jargon (EPIC-005 slice 5, metered gateway key) and omits common synonyms like 'visa requirements'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (offline, human-gated visa data acquisition for a specific deterministic evaluator), states an explicit boundary ('Never runs at request time'), and anchors to SPEC-019 / ADR 062 — minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: matthew-a-carr/travel-planner
Path: .agents/skills/extract-visa-rules/SKILL.md
Commit: 2d8e79c

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.