restructure: Reshape to Agent Skills format #2
No reviewers
jsteffan
tflink
dominikkawka
cybette
jflory7
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-ml/skills-library!2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "cverna/skills-library:restructure/agent-skills-format"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reorganize the repository to follow the agentskills.io open format,
matching the structure used in coreos/ai-helpers.
Changes:
workflow instructions from definition.md)
skills/meeting-secretary/assets/example-discourse-post.md
The skill is now self-contained: SKILL.md references supporting
files in references/ and assets/ via relative paths, keeping the
main instructions under the recommended 500-line limit.
Assisted-by: OpenCode claude-sonnet-4-6@default
@ -23,0 +24,4 @@- **Reference files**: `skills/meeting-secretary/references/` — reference data loaded on demand.Currently includes `teams.md` (Fedora org chart) and `meetbot-commands.md` (Meetbot command parsing reference).- **Assets**: `skills/meeting-secretary/assets/` — output templates and the golden reference example.Currently includes `discourse-post.md`, `forgejo-comment.md`, and `example-discourse-post.md`.Should the repo
AGENTS.mdfile get into the details of themeeting-secretaryskill, or should it be more clear that this is the current example in the repo, and others will be added over time? I'm wondering the agent might get confused, thinking there is only one skill to maintain, when in fact, we want to build a library.@ -35,0 +37,4 @@| `skills/meeting-secretary/references/meetbot-commands.md` | Meetbot command reference and HTML format detection || `skills/meeting-secretary/assets/discourse-post.md` | Output template: Fedora Discussion post || `skills/meeting-secretary/assets/forgejo-comment.md` | Output template: Forgejo ticket comment || `skills/meeting-secretary/assets/example-discourse-post.md` | Golden reference output example |This seems fine for now, but not sure we will want to document every skill in this much detail in the
AGENTS.mdfile.@ -58,3 +63,3 @@## Things agents often get wrong here- **Hallucinating attendees or actions**: The Gem must only report what is in the log. Agents editing the definition or templates should not add example content that could be mistaken for real meeting data.- **Hallucinating attendees or actions**: The Gem must only report what is in the log. Agents editing the skill or templates should not add example content that could be mistaken for real meeting data.This seems like something specific to the
meeting-secretaryskill versus the entire repository.@ -22,1 +21,4 @@- Files in `skills/meeting-secretary/references/` and `skills/meeting-secretary/assets/` are attached to the Gem as knowledge context.Changes to these files affect Gem behavior.- Use one sentence per line (ventilated prose) in all Markdown files.- Template placeholders use `{{DOUBLE_BRACES}}` syntax.Should we just make
CLAUDE.mda symbolic link toAGENTS.md? A lot of what I am seeing here is specific to themeeting-secretaryskill, not an entire library.@ -74,4 +62,3 @@- **Markdown**: One sentence per line (ventilated prose).- **Template placeholders**: `{{DOUBLE_BRACES}}` syntax.- **Naming**: `YYYY-MM-DD-<team>-<type>` for example files.- **License**: All contributions are made under CC BY-SA 4.0.This entire file likely needs a closer look to shape what a library looks like, versus the individual
meeting-secretaryskill.@ -0,0 +1,44 @@# Meeting SecretaryTitle needs to be updated.
@ -0,0 +41,4 @@## License[CC BY-SA 4.0](LICENSE.txt) — Justin Wheeler, Fedora AI/ML SIG, and community contributors.@cverna At this point, you might as well add your name here. 😉
@ -0,0 +37,4 @@- **Fork a template** — Copy [`assets/discourse-post.md`](skills/meeting-secretary/assets/discourse-post.md) or [`assets/forgejo-comment.md`](skills/meeting-secretary/assets/forgejo-comment.md) and adjust the structure for your team's conventions.- **Update the team registry** — Add new or changed teams to [`references/teams.md`](skills/meeting-secretary/references/teams.md).- **Add a Meetbot command** — Update [`references/meetbot-commands.md`](skills/meeting-secretary/references/meetbot-commands.md) if Meetbot's command set changes.This README needs an audit for a skills library versus the individual
meeting-secretaryskill.Agrees with @jflory7, might make more sense for AGENTS.md, README.md etc. to more broadly cover the whole skills library than a specific skill. Restructuring takes quite a bit of organization, thanks for taking this on @cverna! <3
Resolves #1
Agreed, I pushed a second commit that cleans up the README and AGENTS.md. Let me know what you think of it
@cverna Thanks for the quick iteration! As I mentioned in chat, my hands are full with Flock planning and prep right now, among other things. But this is a priority to me, and I will find time to give a second pass this week.
In the meantime, if anyone else has time to take a look from @ai-ml/Members, please share your feedback! 🙏
I need this MR to merge so that we can start adding new skills. I propose that we merge this as is and we can follow-up with smaller PRs if needed to fix things as needed. WDYT?
@cverna You are on-stage now at the Flock lightning talks talking about this right now. I am going to make the executive decision that this is fine to merge for now, and we can always iterate and improve as we go. Thanks so much for working on this!
Merging. 🌊