BD yes-ja
ファイル・設定・データベース・デプロイの変更を伴うタスクで発動。デバッグが2回以上連続で失敗した時に発動。証拠なしに推測・仮定しようとした時に発動（「おそらく」「多分」「〜だと思う」「〜のはず」）。ユーザーに丸投げしようとした時に発動（「ご確認ください」「手動で対応してください」「〜が必要かもしれません」）。修正後に動作確認せず完了と報告しようとした時に発動。根本原因の結論を出す時に発動。使えるツールを使わない時に発動（WebSearchがあるのに検索しない、Bashがあるのに実行しない、Readがあるのに読まない）。同じアプローチで3回以上パラメータだけ変えて空回りしている時に発動。バグ修正後に関連する問題を確認しない時に発動。自分で調べられることをユーザーに質問する時に発動。具体的なコードやコマンドではなくアドバイスだけ出す時に発動。全タスクタイプに適用：デバッグ、実装、設定、デプロイ、API連携、データ処理。初回失敗時や既知の修正手順を実行中の場合は発動しない。
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 41/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (yes-ja) differs from the folder (yes-md-ja)
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 100Steps. 40 steps
- 100Execution cost. Instruction body is 1355 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 440: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.