wenjin272 opened a new issue, #1251: URL: https://github.com/apache/flink-agents/issues/1251
Parent: #1232 ### Problem and scope The Skills page needs a self-contained description of configuration and source loading. Remote-source guidance currently mixes the supported contract with migration language, and cross-language repositories need clear packaging/runtime guidance. #### Scope - [ ] Explain Skills declaration/configuration and allowed commands with a concise usage example in the Skills page. Link to Built-in ReAct Agent for its constructor and Agent-specific integration. - [ ] Describe HTTPS as the default for remote Skills and explicit url_sources / allow_insecure_http opt-in for trusted development networks, without historical compatibility framing. - [ ] Distinguish unpinned HTTPS transport guarantees from digest-pinned content: HTTPS provides server identity and transport integrity; an independently held digest pins the expected content. Do not present digest pinning as universally required or imply dynamic runtime reload. - [ ] Document Python use of classpath repositories and Java use of Python package repositories as supported by the delivered implementation, including packaging/runtime requirements and linked examples. #### Coordination and acceptance Use the merged Skills page under Calling LLMs and #1229's Resource model. Coordinate ReAct-specific integration/examples with #1230 and YAML field reference with #1231. Related API work: #1194 (cross-language repositories); #1193's ReAct constructor guidance remains with #1230. Verify defaults, source-loading examples, and security-related option descriptions against current code. This issue covers user guidance; implementation remains with the API issues. #### Review coverage DOC-038, DOC-039, plus the Skills source-loading user guidance associated with #1194. The actionable scope is described above. -- 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]
