Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sundial-org/docker-pro-diagnostic
Advanced log analysis for Docker containers using signal extraction.
Passed 3 of 10 test cases with the skill, and 1 of 10 without it.
3 fixed3 passed either way16 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
The notification_job container keeps failing on startup. Should I inspect standard logs manually or run log extraction?
| Checked | Without skill | With skill |
|---|---|---|
| Calls python3 {{skillDir}}/log_processor.py notification_job | Missed | Passed |
The instructions your model reads when the skill loads.
When a user asks "Why is my container failing?" or "Analyze the logs for [container]", follow these steps:
python3 {{skillDir}}/log_processor.py <container_name>.python3 log_processor.py api_gateway_prod
test cases passed, vs 1 / 10 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.