Thanks Robert, sounds good!
Carsten
On 10/27/2026 5:24 PM, Robert Munteanu wrote:
Hi,
I plan to move the skills folder [1] out of the whiteboard . We already
have three skills and five contributors which is IMO a very good sign.
This also supports the parent pom update automation work [2].
I plan to make the repository compatible with the agent-plugins
standard [3], which defines a nested structure:
my-agent-skills/
├── plugin.json
├── skills/
│ └── summarize/
│ ├── SKILL.md
│ ├── scripts/
│ └── references/
├── mcp.json
└── com.example.client/
└── hooks/
This simplifies installation in various harnesses.
For now, we have two contributor-facing skills: update-sling-parent-pom
and sling-release, and one which is generally useful: osgi-scr-migrator
.
I suggest keeping all three in the same plugin initially: the parent-
update workflow should reuse the OSGi migrator when required, and the
standard does not currently define dependency installation between
plugins.
Users of individual skills can still install them separately, with the
parent-update workflow documenting its dependency on the migrator.
I will adjust the structure before moving to the new git repo.
Thoughts?
Thanks,
Robert
[1]: https://github.com/apache/sling-whiteboard/tree/master/skills
[2]: https://issues.apache.org/jira/browse/SLING-13397
[3]: https://agent-plugins.org/
--
Carsten Ziegeler
Adobe
[email protected]
