Loading the registry…
クライアント（発注者・事業側の担当者）に渡して受け入れテスト（UAT）をしてもらうための、 平易な言葉で書かれたMarkdown形式のテスト項目書を作成するスキル。 `docs/画面設計書/`（画面ごとの操作・確認ポイント）と `docs/要件定義書.md`（機能要件）を情報源にし、 API・バッチ等の技術的な項目は含めない（そちらは spec-test が開発者向けの自動テストコードとして 別途カバーする）。**実装がまだ完了していない・開発前でも、これらの仕様書さえ存在すれば作成できる** （architecture-design の開発前モードで作った設計書ベースでもよい。その場合は想定ベースである旨を 明記する）。出力は単独ファイル `docs/受け入れテスト項目書.md`。文末に検収の署名欄を含む。 **このスキルは独立して直接呼び出す（spec-dev-cycle を経由しない）。** ユーザーが「受け入れテスト項目書を作って」「UATの資料を作りたい」「クライアントに渡す テスト項目書がほしい」「検収用のチェックリストを作って」「納品用のテスト項目書を作成して」 「開発前だけどテスト項目の想定を作りたい」と言ったとき、または spec-dev-cycle の完了報告後に 受け入れテスト文書の作成を求められたときは、必ずこのスキルを使うこと。`docs/` に仕様書が 無い場合は作成せず、先に architecture-design での仕様書作成を案内する。 ユーザーが「Excelでもほしい」「エクセルファイルにして」と言った場合は、`docs/受け入れテスト項目書.md` を正としつつ `xlsx` スキルで `docs/受け入れテスト項目書.xlsx` も追加生成する。
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'daisy-link/claude-document-plugins (acceptance-test-writer)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'daisy-link/claude-document-plugins (acceptance-test-writer)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
19 findings · 8.3s
v0.3.74
1 finding · 1.1s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.1s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Caution89 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Caution badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 20 findings above stand exactly as their scanners reported them, at full severity.