Run and write Ark Chainsaw tests with mock-llm. Use for running tests, debugging failures, or creating new e2e tests.
82
73%
Does it follow best practices?
Impact
95%
1.37xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/chainsaw/SKILL.mdCRD readiness anti-pattern
No kubectl wait for CRD
0%
100%
Chainsaw assert for CRD readiness
0%
100%
JMESPath Established condition
0%
100%
Assert checks Established status True
0%
100%
Assert targets CustomResourceDefinition
0%
100%
No shell condition script
100%
100%
Manifests numeric prefix naming
40%
100%
Catch block with events
0%
100%
README.md present
100%
100%
Correct test directory structure
100%
100%
Query wait vs assert pattern
Uses wait for Query completion
100%
100%
Wait uses Completed condition
100%
100%
Wait condition value True
100%
100%
No assert before wait
100%
100%
Post-completion assert is separate step
100%
100%
JMESPath in response assert
100%
100%
Catch block with events
100%
100%
Catch block with describe
100%
100%
Wait has timeout
100%
100%
Mock-llm short timeout
0%
0%
Test structure and shell script avoidance
chainsaw-test.yaml present
100%
100%
mock-llm-values.yaml present
100%
100%
README.md present
100%
100%
manifests/ subdirectory present
100%
100%
Manifest numeric prefix ordering
100%
100%
Agent manifest before Query manifest
100%
100%
No kubectl get jq script
100%
100%
Chainsaw assert for resource state
100%
100%
Catch block with events
100%
100%
Catch block with describe
100%
100%
Mock-llm assert timeout short
0%
0%
fc5746e
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.