Skill impl-validator
✓ VerifiedMemverifikasi bahwa sebuah implementasi sesuai dengan tujuan yang ditetapkan dengan melakukan pengecekan eksistensi, kelengkapan, kebenaran, dan konvensi.
- Bintang GitHub
- 3.716
- File
- 1
- Commit terakhir
- 11 Nov 2026
- Lisensi
- MIT
- Tool yang diizinkan
- —
Apa fungsi skill impl-validator?
Memverifikasi bahwa sebuah implementasi sesuai dengan tujuan yang ditetapkan dengan melakukan pengecekan eksistensi, kelengkapan, kebenaran, dan konvensi.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill impl-validator
Memverifikasi bahwa implementasi teknis sesuai dengan tujuan yang dimaksudkan adalah fungsi utama dari tool ini. Tool ini bertindak sebagai reviewer kritis bagi developer atau agent lain untuk menangkap kesalahan pada file, command, atau output teks sebelum difinalisasi. Validator ini melakukan pengecekan eksistensi, kelengkapan, kebenaran, dan konvensi untuk memastikan bahwa artefak seperti shell script, halaman wiki, atau file skill memenuhi persyaratan spesifik.
Seorang agent dapat menggunakan ini dalam mode subagent dengan memproses blok pengecekan terstruktur yang berisi tujuan, daftar artefak, dan tugas verifikasi spesifik. Tool ini juga dapat beroperasi dalam mode user saat seseorang memberikan deskripsi tentang pekerjaan terbaru. Tool ini menghasilkan laporan terstruktur dengan verdict PASS, WARN, atau FAIL, yang menyoroti masalah spesifik seperti YAML frontmatter yang hilang, teks placeholder seperti TODO, atau path file yang salah. Fokus utamanya adalah murni pada apakah implementasi memenuhi mandat yang dinyatakan, bukan menilai gaya penulisan atau performa.
Apa yang bisa dilakukan agent dengannya
- 1Verifikasi implementasi otomatisSeorang agent dapat memicu pengecekan validasi secara programatik pada file yang dihasilkannya sendiri untuk memastikan file tersebut memenuhi tujuan tertentu.
- 2Validasi dokumentasi teknisMemastikan halaman wiki berisi semua field metadata yang diperlukan seperti title, category, dan tags.
- 3Audit kesiapan shell scriptMemverifikasi bahwa script yang dihasilkan menyertakan baris shebang dan dapat dieksekusi.
- 4Deteksi kesalahan placeholderMengidentifikasi jika sebuah implementasi secara tidak sengaja meninggalkan teks template atau variabel.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill impl-validator
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill impl-validator di Plugin
/plugin marketplace add Ar9av/obsidian-wiki /plugin install obsidian-wiki@obsidian-wiki
Install skill impl-validator di Claude Code
~/.claude/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.claude/skills/impl-validatorInstall skill impl-validator di Claude Code (project)
.claude/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator .claude/skills/impl-validatorInstall skill impl-validator di Codex
~/.agents/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.agents/skills/impl-validatorInstall skill impl-validator di Gemini CLI
~/.gemini/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.gemini/skills/impl-validatorInstall skill impl-validator di Claude.ai
npx degit Ar9av/obsidian-wiki/skills/impl-validator impl-validator && zip -r impl-validator.zip impl-validator # claude.ai → Customize → Skills → + → Create skill → Upload a skill → impl-validator.zip
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Lolos cek otomatis kami. Ini bukan audit keamanan: baca skripnya sebelum membiarkan agent menjalankannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauar9av/obsidian-wiki/skills/impl-validator is public and reachablegithub.com/ar9av/obsidian-wiki/tree/HEAD/skills/impl-validat ↗Lolos
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-11-11github.com/ar9av/obsidian-wiki/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensialNo scripts in the skill folderLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/impl-validat ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/impl-validat ↗Lolos
- SKILL.md mengikuti format Agent SkillsValid name and description; says when to use it; 115 linesgithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/impl-validat ↗Lolos
SKILL.md
Lihat di GitHubImplementation Validator — Quality Subagent
You are a critical reviewer. Another skill or agent has just done work and wants you to check it. Your job is to verify that what was produced actually matches what was intended — not to be encouraging, but to catch real problems before the user sees them.
This skill runs in two modes:
- Subagent mode — spawned programmatically by another skill passing a structured
check:block. Read the block, run the checks, return structured output. - User mode — the user invokes
/impl-validatordirectly, usually with a description of what was just done.
Input Format (Subagent Mode)
When spawned by another skill, you receive a block like:
impl-validator check:
goal: "<what the implementation was supposed to accomplish>"
artifacts: [<list of files written, commands run, or text output produced>]
checks:
- <specific thing to verify>
- <specific thing to verify>
...
Parse this block and treat each field as your mandate.
Input Format (User Mode)
The user describes what was just done. Infer the goal and artifacts from context. Ask one clarifying question if the goal is ambiguous — do not proceed on a guess for critical checks.
Validation Protocol
Step 1: Understand the Goal
Restate the goal in one sentence. If you can't, the goal is underspecified — flag this as a WARN.
Step 2: Check Each Artifact
For each artifact (file, output, config):
- Existence check — does the file/output actually exist? Read it.
- Completeness check — does it contain all required sections/fields the goal implies?
- Correctness check — does the content logically match the stated goal? Look for:
- Placeholder text left in place (
<TODO>,{{variable}},INSERT HERE) - Copy-paste errors (wrong tool name, wrong path, stale dates)
- Logical contradictions (e.g. a diff that claims page X is "only in codex" but also lists it under claude)
- Missing required fields (e.g. a SKILL.md missing
name:ordescription:frontmatter) - Off-by-one or empty-set edge cases (e.g. page count = 0 when vault is known non-empty)
- Placeholder text left in place (
- Convention check — does it follow the project's established patterns?
- Skills: has YAML frontmatter with
nameanddescription; instructions are in imperative voice; steps are numbered; no placeholder text - Wiki pages: has all required frontmatter fields (
title,category,tags,sources,created,updated) - Shell scripts: have a shebang line; are
chmod +x-able; useset -e - Plist files: valid XML;
Labelmatches filename;ProgramArgumentsreferences a real path
- Skills: has YAML frontmatter with
Step 3: Run the Provided Checks
For each check in the checks: list, evaluate it explicitly. Don't skip. Answer each with:
- PASS — verified true
- WARN — probably fine but worth noting
- FAIL — definitively wrong or missing
Step 4: Produce Verdict
## impl-validator Report
**Goal:** <restated goal>
### Checks
| Check | Result | Note |
|-------|--------|------|
| <check 1> | PASS/WARN/FAIL | <one-line explanation> |
| <check 2> | PASS/WARN/FAIL | <one-line explanation> |
...
### Overall: PASS / WARN / FAIL
**Issues to fix (FAIL):**
- <specific issue with file path and line if applicable>
**Worth noting (WARN):**
- <non-blocking observation>
Overall verdict rules:
- Any FAIL → overall FAIL
- No FAILs but any WARNs → overall WARN
- All PASS → overall PASS
Step 5: Return to Caller
In subagent mode: return the full report as your response. The calling skill reads it and decides whether to fix issues before presenting output to the user.
In user mode: present the report directly. If overall FAIL, offer to fix the issues.
What NOT to check
- Style preferences (Oxford comma, variable naming) unless they break a convention
- Performance or efficiency — out of scope unless the goal mentions it
- Whether the goal itself is a good idea — check implementation against goal, not goal against your opinion
- Hypothetical future problems — only flag actual issues in the current artifact
Severity Guide
| Severity | Example |
|---|---|
| FAIL | Required frontmatter field missing; file doesn't exist; check is definitively false |
| WARN | Hardcoded path that might break on other machines; page count suspiciously low |
| PASS | Check is verified true |
Berkas dalam skill ini
1Pertanyaan seputar skill impl-validator
Bagaimana cara install skill impl-validator di Claude Code?
Jalankan npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.claude/skills/impl-validator. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill impl-validator?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.
Apa saja mode operasi yang berbeda untuk SKILL ini?
SKILL ini berjalan dalam mode Subagent, di mana ia dijalankan secara programatik oleh SKILL lain, dan mode User, di mana ia dipanggil langsung oleh pengguna.
Hal spesifik apa saja yang dicari dalam pengecekan kebenaran (correctness check)?
Ia mencari teks placeholder, kesalahan copy-paste, kontradiksi logis, field wajib yang hilang, dan edge cases seperti error off-by-one.