wenjin272 opened a new issue, #917: URL: https://github.com/apache/flink-agents/issues/917
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description #### Motivation Users increasingly rely on coding agents such as Codex, Claude Code, Gemini CLI, and Qoder to build Flink Agents applications. Today, each coding agent must rediscover Flink Agents APIs, version compatibility, YAML schema constraints, dependency setup, cross-language resource support, and local MiniCluster verification for every project. This often leads to speculative API usage, unsupported version combinations, and incomplete project scaffolding. This proposal is complementary to [#877](https://github.com/apache/flink-agents/issues/877), which adds repository guidance for contributors, and is distinct from the runtime Agent Skills feature tracked by [#589](https://github.com/apache/flink-agents/issues/589). It provides reusable development guidance for users building applications with external coding agents. #### Proposal Add a repository-managed, portable `flink-agents-dev` skill under `dev/agent-skills/flink-agents-dev/`. The skill should: - be self-contained so users do not need to clone the Flink Agents repository; - bundle the YAML schema and focused references required for application development; - guide users through Flink Agents/Flink version selection, API selection, application language, resource implementation, and Python environment choices; - support the YAML, Python, and Java APIs; - treat custom Actions, Tools, prompts, and runtime Skills as user-owned business logic, generating framework-compatible skeletons with explicit placeholders by default; - support cross-language chat models, embedding models, and vector stores whenever the selected Flink Agents version exposes the required wrappers; - generate dependency-managed Maven or Python projects; - connect generated agents to Flink through `RemoteExecutionEnvironment` and support local verification by submitting jobs to a MiniCluster; - provide host-specific interaction guidance for coding agents while keeping generated applications platform-independent. Keeping the skill in the repository allows its bundled schema, API guidance, supported versions, and examples to evolve together with Flink Agents. #### Scope The initial change adds the portable skill package and the repository configuration needed to manage it. It does not introduce or change Flink Agents runtime APIs. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
