luigidemasi opened a new issue, #126: URL: https://github.com/apache/camel-kit/issues/126
The workflow manifest `camel-kit-core/src/main/resources/workflow/camel-kit-workflow.yaml` classifies the thirteen shipped skills: | status | skills | user_invocable | generated_command | |---|---|---|---| | `router` | `camel-start` | `true` | `camel-start` | | `pipeline` | `camel-brainstorm`, `camel-migrate`, `camel-plan`, `camel-execute`, `camel-validate` | `false` | the command | | `standalone` | `camel-ship`, `camel-knowledge`, `camel-debug` | `false` | the command | | `internal` | `camel-verify`, `camel-design`, `camel-implement`, `camel-test` | `false` | `null` | Only `camel-start` is `user_invocable: true` in the shared source; the nine public skills still get entry points through generated command stubs or native project skills, and the Bob 2 generator sets both invocation fields to `true` for them in the generated copies. `ShippedAssetStructureTest` requires every shipped `skills/<name>/SKILL.md` directory to have a manifest entry, internal ones included. While writing the public documentation for the component, the contributor recipe initially said that only user-facing skills are registered in the manifest; the correction exposed that the internal/public boundary and its per-agent exposure rules are documented in several places (`docs/commands.md`, `docs/architecture.md`, `CONTRIBUTING.md`, the generated `user-invocable` aliases, Doctor's hidden-skill check) without one place that states the classification criteria. **Task** 1. Review the classification of each skill: is every `internal` skill truly never user-invoked, and is every public skill correctly exposed on every agent (command stubs, native skills, Bob 2 picker, Codex `$camel-*`, Pi `/skill:`)? 2. Decide whether any skill should change status (for example whether `camel-verify` should stay internal now that `/camel-debug` covers standalone troubleshooting). 3. Write the criteria down once, next to the manifest, and align `docs/commands.md`, `docs/architecture.md`, `CONTRIBUTING.md` and the published pages on skills and contributing with the outcome. Website impact: required if any status changes; the skills and contributing pages describe the current classification. -- 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]
