Hi Rui + 1 to the overall idea. I agree with the proposal to create a dedicated skill repository. I have found them helpful as well. 1. +1, It would be a good to from both user and the customer perspective to have skills for this in the community-maintained repo. 2. +1 to a dedicated skill repo, rather than it distributed across the repos. It can contain end-to-end experiences that do not fall within the scope of any single repository.
Additionally, I have 2 skill repo which I have been using from 6 months, thought I thought of expanding it across various other applications besides Flink when I work on them. Repo - https://github.com/spuru9/ai-helper There are two skills: flink-oss-setup <https://github.com/spuru9/ai-helper/tree/main/skills/flink-oss-setup> and flink-pr-reviewer <https://github.com/spuru9/ai-helper/tree/main/skills/flink-pr-reviewer>. I have used flink-oss-setup extensively and it is really helpful and compatible with Gemini and Claude. If we move forward with a dedicated repo for this, I would love to contribute these skills and collaborate further with you on this idea. On Sun, Oct 11, 2026 at 12:20 PM Rui Fan <[email protected]> wrote: > Hi everyone, > > I would like to discuss whether the Flink community should maintain > reusable > Agent Skills for community work and, if so, where they should live. > > AI agents can now handle much of the evidence gathering, checking, and > drafting > involved in a release. This could reduce repetitive work for release > managers > and make more frequent patch releases practical, while release decisions, > votes, and signing remain with people. > > How can release skills become reliable? The approach is to start with the > current official release process and study at least ten past real releases > when designing a skill. Problems found in past and future releases can then > become checks in the skill, used during preparation and verification to > avoid > repeating the same mistakes. > > As a POC, I have drafted two skills [1]: flink-release and > verify-flink-release. Together, they are designed to cover the full > patch-release workflow, from gathering evidence before the first dev@ > discussion through post-publication follow-up. So far, the Discovery stage > has > been refined and generated three [DISCUSS] emails for Flink 1.20.6 [2], > 2.2.2 [3], and 2.3.1 [4]; all three were sent to dev@. These releases will > help test and improve the later stages. > > Future skills could cover major and minor releases and other Flink > projects, > such as Flink CDC, the Flink Kubernetes Operator, and connectors. > Troubleshooting skills could also help Flink users diagnose problems. More > background is in the Project purpose and direction document [5]. > > The POC currently lives in my own repository. I would particularly welcome > feedback on two questions: > > 1. Should the Flink community maintain these skills? If not, I can continue > maintaining them in my own repository. > 2. If so, where should they live? I favor a dedicated community skills > repository so similar workflows, especially connector releases, can be > reused across projects. Keeping each skill in its project's code repository > is another option. > > Best, > Rui > > [1] https://github.com/1996fanrui/flink-skills > [2] https://lists.apache.org/thread/mjmb5hfgnxzy7081dk7oqbj4znv5fzoy > [3] https://lists.apache.org/thread/tzklqoy343q2nfm7kwzbgd8kpjgtq0t9 > [4] https://lists.apache.org/thread/x68b0xvfxv78s7d1pq72r92y71b80k9r > [5] > > https://github.com/1996fanrui/flink-skills/blob/main/PROJECT_PURPOSE_AND_DIRECTION.md > -- Best Regards, Purushottam Sinha शुभकामनाएं पुरूषोत्तम सिन्हा
