wenjin272 opened a new issue, #1194: URL: https://github.com/apache/flink-agents/issues/1194
### Search before asking - [x] I searched existing issues for duplicates; related work is linked below where applicable. ### Description This is a child issue of #1055. #### Problem The shared Skills schema accepts source schemes that the selected runtime cannot load. Python accepts `classpath` declarations but its built-in registry has no classpath handler; Java accepts `package` declarations but has no built-in package handler. The current schema documentation explicitly notes the Python load-time failure. Consequently a structurally valid declaration can fail only when Skills are initialized in the execution runtime. #### Proposed direction Prefer providing the missing source materialization where practical. Until supported, reject incompatible built-in source/runtime combinations as early as the target runtime language is known, with an error identifying the source, language, and supported alternatives such as `local`/`url`. Validation must use the language that actually loads the Skill, not merely the language parsing YAML or constructing a cross-language descriptor. Preserve the extensible handler registry; do not reject a custom scheme solely because it is absent from the built-in list. #### Acceptance criteria - Each accepted built-in source/runtime combination can actually be materialized, or is rejected before operator initialization when its incompatibility is known. - Native, YAML, and cross-language tests cover `classpath`, `package`, portable sources, and registered custom handlers. - Diagnostics and docs clearly state runtime support and alternatives. Relevant code: Java/Python Skills YAML specs and SkillSourceRegistry; `python/flink_agents/api/yaml/specs.py`, `python/flink_agents/runtime/skill/skill_source_registry.py`. ### Are you willing to submit a PR? - [ ] 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]
