agentleFS
Sign inStart free
AWSKnown publisherawslabs/managed-service-for-apache-flink-agent-steering-files/SKILL.md

flink

Skill5 starsChanged 7 months agoApache-2.0View on GitHub

Comprehensive guidance for developing, optimizing, and operating Apache Flink applications on Amazon Managed Service for Apache Flink. Use when working with Apache Flink, Managed Service for Apache Flink, streaming, stream-processing, real-time data, Kafka, or Kinesis.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. gordonmurray/data-engineering-skills★ 47same name
    2. pravsjv/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Don't get started until you confirm the user's goals and use case

    line 44
  2. Distinctive:

    Don't make changes unless the user asks you to

    line 45
  3. Distinctive:

    When developing code, use this skill's reference files as guidance first, followed by general knowledge

    line 46
  4. Distinctive:

    When creating Flink applications, always reference multiple relevant files together:

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. SPDX-License-Identifier: Apache-2.0 -->

Managed Service for Apache Flink Skill

Overview

This skill provides comprehensive guidance for developing, optimizing, and operating Apache Flink applications on AWS Managed Service for Apache Flink. It is designed to improve Apache Flink onboarding and improve operational excellence.

Disclaimer

All code generated by this skill is AI-assisted and should be thoroughly reviewed, tested, and validated by users before being used in production environments. AI-generated code may contain errors, security vulnerabilities, or suboptimal patterns that require human judgment to identify and correct. Any code changes adopted from this skill should be tagged with generated by Managed Service for Apache Flink Kiro Power in code comments or commit messages to clearly indicate when generated changes were adopted.

Key Problems Solved

  1. New Customer Onboarding: Overcome the steep learning curve for Flink's Java-centric development model
  2. Existing Customer Optimization: Systematic review and improvement of Flink applications to align to best practices
  3. Operational Excellence: Integrated troubleshooting and monitoring using automated tools with CloudWatch and Managed Service for Apache Flink APIs
  4. Migrating / upgrading to Flink 2: Systematic review and upgrade from Flink 1.x apps to Flink 2.x apps to handle migrations to 2.x with breaking changes

Reference Files

Load these files as needed based on the user's task:

  • Core Managed Service for Apache Flink Development Workflow — how to approach user interaction, development, and testing
  • Environment Setup — set up a local dev environment
  • Dependency Management — Maven pom.xml dependencies for new projects
  • Best Practices — Flink best practices for new apps
  • Managed Service for Apache Flink Overview and Concepts — Managed Service for Apache Flink-specific optimizations and constraints
  • Flink 2.x Migration Guide — upgrading from Flink 1.x to 2.x, including state compatibility
  • Resource Optimization — KPU sizing, operator parallelism tuning, configuration overrides, and checkpoint resource impact
  • Job Graph Architecture — job graph optimization, monolith anti-pattern, high fan-out, and operator-to-task-slot mapping
  • Monitoring and Metrics — CloudWatch metrics analysis, recommended alarms, and custom metrics emission
  • Logging Configuration — logging best practices, Log4j2 configuration, and rate-limited logging patterns for Managed Service for Apache Flink
  • Kinesis Source / Sink Development — Kinesis connector-specific guidance

General Guidance

  • Don't get started until you confirm the user's goals and use case
  • Don't make changes unless the user asks you to
  • When developing code, use this skill's reference files as guidance first, followed by general knowledge

CRITICAL: Required Reading for All Flink Development

BEFORE writing ANY Flink code, you MUST read these files:

  1. ALWAYS read core-workflow.md first — Contains essential steps for development
  2. ALWAYS read best-practices.md second — Contains essential Managed Service for Apache Flink patterns, anti-patterns, serialization guidance, state management, and configuration separation

These are NOT optional — you must read them before generating any code.

Working with Multiple Reference Files

When creating Flink applications, always reference multiple relevant files together:

  1. Start with best-practices.md — Read this FIRST for all development work
  2. Then read dependency-management.md — For correct Maven dependencies when building new Flink apps
  3. Then read connector-specific guides (e.g., kinesis-connector-guide.md) for API usage whenever making changes to or evaluating app's source/sink configs or making new apps
  4. For resource sizing and scaling — Read resource-optimization.md for KPU sizing, parallelism tuning, and checkpoint impact on resources
  5. For job graph design — Read job-graph-architecture.md for operator chaining, data skew, anti-patterns, and task slot mapping
  6. For monitoring and observability — Read monitoring-and-metrics.md for CloudWatch metrics analysis and custom metrics emission, and logging-configuration.md for log configuration
  7. Cross-reference between documents — They link to each other for related information

Support & Legal

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free