SKILLEMALL.ai

BB msk-migration

Use this skill to assess and plan a migration from AWS MSK (Managed Streaming for Apache Kafka) to Confluent Cloud. Triggers on user intent like "migrate MSK to Confluent Cloud", "move off MSK", "MSK to CC cutover", "Zero-Cut migration from MSK", "kcp scan my MSK", or any discussion of MSK-to-CC assessment, planning, cluster sizing, Cluster Linking setup, Gateway-based switchover, or post-cutover validation. Do NOT trigger for non-MSK Kafka sources (open-source Kafka, Aiven, Confluent Platform, Redpanda) — this skill is MSK-only. Do NOT trigger for greenfield Confluent Cloud projects with no existing Kafka source. Do NOT trigger for general Kafka programming questions (producer/consumer code, Kafka Streams) unrelated to migration.

confluentinc/agent-skills Agent Skills author: confluentinc Apache-2.0 35 files body ≈ 15 653 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Use this skill to assess and plan a migration from AWS MSK (Managed Streaming for Apache Kafka) to Confluent Cloud.

As a process B 70/100 · Nearly there — weak spots: result and completion, execution cost

AnalyzerAWSGitHubTerraformInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
B
70/100
Nearly there
Result and completion w 14
0
Execution cost w 6
40
Tools and files w 18
60
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 15653 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 70/100

  • 0Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 15653 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 69 steps, 3 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 6 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 top-level sections: this looks like several domains in one skill
  • 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 5 example trigger phrases
  • +3Description length 740: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 69 items
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.