AC traefik
Deploy, configure, and troubleshoot Traefik v3 reverse proxy — covers all providers, routing, TLS/ACME, middlewares, and production patterns with YAML examples. Load when setting up or debugging a Traefik instance. Do not use this skill for unrelated requests; route to the nearest named specialist.
Deploy, configure, and troubleshoot Traefik v3 reverse proxy — covers all providers, routing, TLS/ACME, middlewares, and production patterns with YAML examples.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securityreferences/production-deployment.md:128Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- no-new-privileges:true # Prevent privilege escalation
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
edit-residuethe text marks something as outdated (lines 64): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 52/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
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2586 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low The response is described with custom markup (6 tags): a typed call is more reliable
- low No test case covers injection arriving through data
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
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 299: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (17 of 17)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 94.