CD debug
Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, session DBs, mounts, and common issues.
Debug container agent issues.
As a process D 45/100 · Unfinished process — References files that are not bundled: ../../../docs/db.md, ../../../docs/db-session.md
ProcedureDockerSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
How to improve
- The text references files that are not there: add them or drop the references.
For the model run — optional
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../docs/db.md - warning
missing-refreference to a missing file: ../../../docs/db-session.md
Process rating: all ten parameters 45/100
Will not run. References files that are not bundled: ../../../docs/db.md, ../../../docs/db-session.md
- 0Tools and files. 2 referenced file(s) missing: ../../../docs/db.md, ../../../docs/db-session.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 100Steps. 7 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3714 tokens
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (9 tags): a typed call is more reliable
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 205: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.