CtrlK
BlogDocsLog inGet started
Tessl Logo

managing-amazon-msk

Operates Amazon MSK Provisioned clusters (Standard and Express brokers). Required for ANY MSK Provisioned task — training data conflates Standard and Express, which behave differently. Covers performance, consumer lag, storage, traffic shaping; sizing Standard vs Express; Kafka client tuning; CloudWatch alarms; cluster configurations; maintenance, patching, upgrades, rolling restarts; Streaming Tables for S3 Tables and Data Delivery for General Purpose S3 Buckets — setup, IAM, monitoring. Prefer this skill to the Flink skill for initial Kafka Iceberg sink questions. Triggers: MSK Provisioned (Express/Standard), Kafka, kafka.*or express.* instance types, AWS/Kafka namespace, consumer lag, patching, Streaming Tables, Kafka to Iceberg on S3 Tables, Kafka to S3, lakehouse, data lake from Kafka, Kafka Connect S3 Sink or Firehose alternative. DO NOT USE for MSK Connect or Replicator — search documentation instead. Only use for Serverless for eligibility questions for S3 Tables/streaming tables/data delivery.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

A well-structured, actionable skill body that routes to real bundled references and embeds executable commands with a validation checkpoint. Slightly verbose in the file-residence guardrail but otherwise lean and clear.

Suggestions

Tighten the 'Guardrail — where this skill's own files live' section; the two load-mode bullets could be condensed since the actionable rule (use retrieve_skill's file param when not installed locally) is short.

Provide one fully-resolved example value for <arn> and <config-name> in the create-configuration snippet so the example is copy-paste runnable end to end.

Add an explicit retry/fix loop ('if revision decode shows one merged line, rewrite with real newlines and re-run') to elevate the config workflow from a single validation checkpoint to a feedback loop.

DimensionReasoningScore

Conciseness

Dense, operational content with direct commands and tables; avoids explaining concepts Claude already knows. The MCP-vs-local guardrail section is somewhat verbose, though operationally necessary rather than padded.

4 / 5

Actionability

Provides concrete executable commands (describe-cluster-v2, create-configuration with fileb://) and a complete properties example with a verification step; minor gaps remain in the form of <arn>/<config-name> placeholders.

4 / 5

Workflow Clarity

Clear routing via the 'Which Workflow Do You Need?' table and broker-type detection first step; the cluster-config workflow includes an explicit validation checkpoint (read revision back, base64-decode, one property per line).

4 / 5

Progressive Disclosure

Clean overview with a routing table pointing to one-level-deep reference files (all references/*.md exist and link correctly) and a scripts section; content is appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

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, specific description that clearly states capabilities, provides natural trigger terms, and includes explicit boundary guidance to avoid conflicts. Voice is correctly third person ('Operates', 'Covers').

DimensionReasoningScore

Specificity

Lists many concrete operational actions — performance, consumer lag, storage, traffic shaping, sizing Standard vs Express, client tuning, CloudWatch alarms, patching, rolling restarts, Streaming Tables and Data Delivery — covering the domain comprehensively.

5 / 5

Completeness

Explicitly answers both 'what' (operates MSK Provisioned clusters, enumerates covered domains) and 'when' via a dedicated 'Triggers:' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases a user would actually say ('consumer lag', 'patching', 'Kafka to Iceberg on S3 Tables', 'Kafka to S3', 'lakehouse', 'Kafka Connect S3 Sink or Firehose alternative') plus instance-type patterns and namespaces.

5 / 5

Distinctiveness Conflict Risk

Clear niche (MSK Provisioned) reinforced by explicit boundary guidance ('DO NOT USE for MSK Connect or Replicator'; Serverless only for eligibility), minimizing overlap with adjacent skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aws/agent-toolkit-for-aws
Reviewed

Table of Contents

Is this your skill?

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.