accept
Use as a terminal node that emits accepted@1 only when an upstream verdict@1 says pass, and fails loudly on a rejected draft…
Use when checking a record / dataset / GMP document for ALCOA+ data integrity — attribution, contemporaneity (backdating), completeness, accuracy (recompute / in-spec), consistency — before a human approves. DEGRADED mode lints any CSV/JSON record against a declared .alcoa.json
$ npx -y skills add s0912758806p/agentic-sop-to-work --skill alcoa-guard --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/alcoa-guardContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when checking a record / dataset / GMP document for ALCOA+ data integrity — attribution, contemporaneity (backdating), completeness, accuracy (recompute / in-spec), consistency — before a human approves. DEGRADED mode lints any CSV/JSON record against a declared .alcoa.json
name: alcoa-guard description: Use when checking a record / dataset / GMP document for ALCOA+ data integrity — attribution, contemporaneity (backdating), completeness, accuracy (recompute / in-spec), consistency — before a human approves. DEGRADED mode lints any CSV/JSON record against a declared .alcoa.json contract; FULL mode snaps onto an agentic-sop-kit run dir. | 要檢查紀錄/資料/GMP 文件的資料完整性(ALCOA+:可歸屬、同步性/防 backdating、完整、正確、一致)時使用。輸出為 DRAFT,人擁有最終判定;確定性檢查只覆蓋可機械驗證的部分,其餘列為人判斷清單,絕不臆造。
You are a deterministic data-integrity checker. You NEVER auto-conclude compliance.
1. Run the deterministic linter (above). It writes `alcoa_guard.json` + `alcoa_guard.md`. 2. Present the HARD/SOFT findings verbatim. Do not soften or invent. 3. Present the human-judgment checklist — these are NOT auto-verified; a human must assess them. 4. STOP. The human owns the verdict; a deterministic GREEN is not "fully compliant".
Loop Engineering — make an agent's loop produce verifiable progress, stay honest, and stay bounded, by deterministic mechanism rather than vibes.
Use as a terminal node that emits accepted@1 only when an upstream verdict@1 says pass, and fails loudly on a rejected draft…
Use to compute summary statistics (count/sum/mean/min/max) from a readings artifact, preserving the upstream source trace. Single…
Use to extract numeric readings (key: value lines) from a plain-text input into a structured readings artifact with…
Use to render a DRAFT Markdown summary report from a stats artifact, including a source-trace section; output is always a DRAFT…
Use to derive a deterministic reject/pass verdict from a draft@1 artifact's open-defect count, emitting a verdict@1 artifact for…
Use when turning a human SOP or manual process into an agentic workflow, building or adding an agent tool, or starting a new…