Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/CleanExpo/Unite-Group --skill evidence-verifier명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
The authoritative environment-variable registry for the Unite-Group Nexus. Use whenever adding, reading, renaming, or debugging an env var or secret — new integration config, a `process.env.X` read, an auth/OAuth wiring, a cron secret, a "which variable holds this" question, or a "works locally but not in prod" symptom. Also use before pinning any variable name in code, and when reconciling the two credential planes (Vercel prod vs the local hermes fleet). Prevents the `APIFY_API_KEY` vs `APIFY_API_TOKEN` class of drift.
Create, verify, and promote Supabase schema changes via database branches. Every schema change/migration must be validated on a Supabase database branch before prod (see CLAUDE.md line 44).
Verify production Supabase schema before shipping code that touches it. Use BEFORE writing or reviewing ANY code that reads or writes a Supabase table in the Nexus — new queries, inserts, updates, CHECK-constrained values, RLS-dependent reads, cron data access — even one-line changes and even when the table "obviously" exists. Also use immediately when a query fails with "column does not exist", when inserts appear to succeed but produce no rows, or when generated TypeScript types disagree with runtime behaviour.
SOC 직업 분류 기준
SKILL.md 표시 중
| id | evidence-verifier |
| name | evidence-verifier |
| type | Capability Uplift |
| version | 1.0.0 |
| created | 20/03/2026 |
| modified | 20/03/2026 |
| status | active |
| triggers | ["verify the proof","check the evidence","is there proof","show me the artifacts","validate the evidence","confirm the proof","check artifacts"] |
| description | > |
Purpose: Ensure that claimed proof artifacts are real, accessible, and relevant. Phantom evidence is evidence that is claimed but does not exist.
Use this skill when:
| Class | Definition | Accepted? |
|---|---|---|
| VERIFIED | Artifact shown, accessible, relevant, and recent | Yes |
| CLAIMED | Artifact referenced but not shown | No |
| PHANTOM | Artifact claimed to exist but cannot be found | No |
| STALE | Artifact exists but is from an outdated state | No (without note) |
List every artifact that has been claimed as proof:
reports/gap-analysis.md)https://production-url.com)For each claimed artifact:
If it's a file path:
lsIf it's a URL:
If it's tool output (test results, curl, etc.):
If it's a screenshot:
Assign VERIFIED, CLAIMED, PHANTOM, or STALE to each artifact.
EVIDENCE VERIFICATION REPORT
═══════════════════════════════════════════════════
Verified: [N] / [total] artifacts
ARTIFACT 1: [description]
Type: [file | URL | test output | screenshot]
Claim: [what was claimed]
Status: VERIFIED | CLAIMED | PHANTOM | STALE
Notes: [what was found / what is missing]
ARTIFACT 2: [description]
...
VERDICT
─────────────────
If all VERIFIED: → ACCEPT evidence
If any not VERIFIED: → REJECT — list what is needed:
□ [artifact 1]: [exact action to produce real evidence]
□ [artifact 2]: [exact action]
═══════════════════════════════════════════════════
Before marking any artifact VERIFIED:
| Failure | Recovery |
|---|---|
| Artifact is a description, not the artifact | Request the actual file/output/screenshot |
| File exists but is empty | Mark PHANTOM — empty files are not evidence |
| URL returns 404 | Mark PHANTOM — request correct URL |
| Test output shows failures | Do not reclassify as VERIFIED — failures are failures |
| Screenshot is blurry or cropped | Request full clear screenshot |
Claim: "All tests pass" Evidence shown: Full vitest output with 47 tests, 0 failures, coverage 82% Classification: VERIFIED
Claim: "All tests pass" Evidence shown: "I ran the tests and they all passed." Classification: CLAIMED — test output not shown