CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/gremlin-chaos

Configures Gremlin (commercial) for cross-platform chaos engineering (fault injection, resilience testing) - installs the Gremlin agent on Linux / Windows / Kubernetes, picks attack types (resource, network, state, request), chains attacks into Scenarios (chaos experiments), integrates with the Reliability Score for forward-looking metrics. Use when the platform spans multiple environments (bare metal + cloud + serverless) and the team needs a commercial-supported solution per Gremlin's multi-platform support.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, executable skill body: concrete code, a sequenced multi-step workflow with validation checkpoints for destructive operations, and clean one-level-deep progressive disclosure to a verified reference file. Minor redundancy in the trailing References section does not reduce any dimension.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — executable install/curl snippets, a compact attack-class table, and no padding with generic chaos-engineering concepts; the only redundancy is the bottom References block re-describing the Gremlin overview.

3 / 3

Actionability

Fully executable guidance throughout: `apt install`, a complete `helm install` with real `--set` flags, and a copy-paste-ready `curl` attack payload with concrete args — meeting the score-3 anchor.

3 / 3

Workflow Clarity

The 6-step 'How to use' and the numbered worked example both include explicit validation checkpoints (steady-state assertion before injecting, abort-path verification) appropriate for destructive chaos operations, with fix-and-retry feedback loops.

3 / 3

Progressive Disclosure

SKILL.md stays an overview and consistently defers exhaustive detail to the one-level-deep, clearly signaled references/advanced-operations.md, which exists as a real bundle file.

3 / 3

Total

12

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that names concrete capabilities, includes an explicit 'Use when' trigger, and is well-differentiated from OSS alternatives. Slightly verbose at the tail but no over-claims that reduce any dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'installs the Gremlin agent on Linux / Windows / Kubernetes', 'picks attack types (resource, network, state, request)', 'chains attacks into Scenarios', 'integrates with the Reliability Score' — matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what (configure/install/chain attacks) and when via the 'Use when the platform spans multiple environments ... and the team needs a commercial-supported solution' clause.

3 / 3

Trigger Term Quality

Good coverage of natural terms users would say — 'chaos engineering', 'fault injection', 'resilience testing', 'Gremlin', 'Scenarios', 'Linux / Windows / Kubernetes' — though the trailing 'per Gremlin's multi-platform support' is mildly padded.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche — commercial, multi-platform chaos engineering — with distinct triggers (bare metal + cloud + serverless, enterprise support) unlikely to fire for the OSS K8s-only alternatives.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents