Establish a Skills Reviewers sub-team for the skills-library #31

Open
opened 2026-07-03 02:29:28 +00:00 by jflory7 · 17 comments
Owner

Summary

Create a small "Skills Reviewers" sub-team within the AI/ML SIG, responsible for creating, reviewing, and curating shared AI skills in the skills-library repo.

Background

There is growing interest in AI skills that follow the Agent Skills specification — guided, agent-neutral skill definitions that can be shared, improved, and used by any LLM/model. The skills-library repo already has active contributions (e.g., @cverna merged PR #8), but there is no formal review process or reviewer team on Forgejo. Formalizing this will make the effort more sustainable and welcoming to new contributors.

This was proposed at the 2026-07-02 AI/ML SIG meeting. No opposition was raised. @cverna is implicitly on board based on recent engagement.

Details

  1. Create a Forgejo team (e.g., skills-reviewers) in the ai-ml org with write access to ai-ml/skills-library.
  2. Seed the team with initial members: @jflory7, @cverna, and anyone else who expresses interest.
  3. Define a lightweight review process for skill PRs (e.g., at least one reviewer approval before merge).
  4. Post an open call on Matrix and Discourse inviting others to join.
  5. Related: feedback wanted on the git submodule distribution approach in skills-library#3.

Outcome

A recognized sub-team in the SIG with a clear mandate to curate the skills-library, making it easy for contributors to participate and for PRs to get reviewed consistently.

Assisted-by: Claude Opus 4.6 (1M context)

## Summary Create a small "Skills Reviewers" sub-team within the AI/ML SIG, responsible for creating, reviewing, and curating shared AI skills in the [skills-library](https://forge.fedoraproject.org/ai-ml/skills-library) repo. ## Background There is growing interest in AI skills that follow the [Agent Skills specification](https://agentskills.io/specification) — guided, agent-neutral skill definitions that can be shared, improved, and used by any LLM/model. The skills-library repo already has active contributions (e.g., @cverna merged [PR #8](https://forge.fedoraproject.org/ai-ml/skills-library/pulls/8)), but there is no formal review process or reviewer team on Forgejo. Formalizing this will make the effort more sustainable and welcoming to new contributors. This was proposed at the [2026-07-02 AI/ML SIG meeting](https://meetbot.fedoraproject.org/meetings/meeting-2_matrix_fedoraproject-org/2026-07-02/fedora-ai-ml-sig.2026-07-02-16.30.html). No opposition was raised. @cverna is implicitly on board based on recent engagement. ## Details 1. Create a Forgejo team (e.g., `skills-reviewers`) in the `ai-ml` org with write access to `ai-ml/skills-library`. 2. Seed the team with initial members: @jflory7, @cverna, and anyone else who expresses interest. 3. Define a lightweight review process for skill PRs (e.g., at least one reviewer approval before merge). 4. Post an open call on Matrix and Discourse inviting others to join. 5. Related: feedback wanted on the git submodule distribution approach in [skills-library#3](https://forge.fedoraproject.org/ai-ml/skills-library/issues/3). ## Outcome A recognized sub-team in the SIG with a clear mandate to curate the skills-library, making it easy for contributors to participate and for PRs to get reviewed consistently. <sub>_Assisted-by: Claude Opus 4.6 (1M context)_</sub>
jflory7 self-assigned this 2026-07-03 02:29:28 +00:00
Member

+1 @ttomecek might be interested too

+1 @ttomecek might be interested too
Owner

I am interested.

I am interested.
Member

I am interested in joining too.

I am interested in joining too.
Member

Related to this, I have opened ai-ml/skills-library#13 to discuss CI/Linting for skills.

Related to this, I have opened https://forge.fedoraproject.org/ai-ml/skills-library/issues/13 to discuss CI/Linting for skills.
Author
Owner

@davdunc @lbarczio Awesome! Thanks both for sharing your interest. I am thinking we can likely transition most planning over into ai-ml/skills-library as we get going, but for now, we can brainstorm more here.

I think one of the most helpful things would be a human reviewer guide for things to observe and look out for when reviewing Agent Skills. It feels like new territory figuring out how to standardize a collaborative review process for something like this. If anyone wants to take a crack at this, it would be an ambitious but useful output.

In the meantime, does anyone have any ideas for new skills to create? I have one that I am working on locally about the Forgejo API on forge.fedoraproject.org. Especially the issues, labels, and milestone APIs. I have been wrangling the (more or less) same skill between several different projects, and I would like to commit it here and start looking into something like agr for using skills in my Forgejo projects.

@davdunc @lbarczio Awesome! Thanks both for sharing your interest. I am thinking we can likely transition most planning over into `ai-ml/skills-library` as we get going, but for now, we can brainstorm more here. I think one of the most helpful things would be a human reviewer guide for things to observe and look out for when reviewing Agent Skills. It feels like new territory figuring out how to standardize a collaborative review process for something like this. If anyone wants to take a crack at this, it would be an ambitious but useful output. In the meantime, does anyone have any ideas for new skills to create? I have one that I am working on locally about the Forgejo API on forge.fedoraproject.org. Especially the issues, labels, and milestone APIs. I have been wrangling the (more or less) same skill between several different projects, and I would like to commit it here and start looking into something like `agr` for using skills in my Forgejo projects.
Member

Hi everyone, to add to the brainstorming pool, I'm interested in creating skills focused on easing the packaging workflow (on top of e.g. what Packit already does), my first ideas would be:

  • fixing failing scratch builds
  • automated patch backporting - taking inspiration from what we do in RHEL/CentOS stream in our team

I’m also up for kicking off the human reviewer guide, though I'm on vacation this week, I could dive into drafting that once I'm back next week.

Hi everyone, to add to the brainstorming pool, I'm interested in creating skills focused on easing the packaging workflow (on top of e.g. what Packit already does), my first ideas would be: - fixing failing scratch builds - automated patch backporting - taking inspiration from what we do in RHEL/CentOS stream in our team I’m also up for kicking off the human reviewer guide, though I'm on vacation this week, I could dive into drafting that once I'm back next week.
Owner

I'm interested as well

I'm interested as well
Author
Owner

I also realized recently that all of "The Open Organization" books are made available under CC BY-SA license. This got me thinking that an Agent Skill for working in open organizations, like Fedora community in a sense, could be an interesting one. Unlike the Forgejo API skill I am already working on, this idea is conceptual only right now. But I am thinking about something like this.

I also realized recently that all of ["The Open Organization" books](https://theopenorganization.org/books/) are made available under CC BY-SA license. This got me thinking that an Agent Skill for working in open organizations, like Fedora community in a sense, could be an interesting one. Unlike the Forgejo API skill I am already working on, this idea is conceptual only right now. But I am thinking about something like this.
Member

(back from my vacation), yes please, count me in!

(back from my vacation), yes please, count me in!
Author
Owner

Discussed in 2026-07-16 Fedora AI/ML SIG meeting.


The SIG voted to create the skills-reviewers team. Five volunteers joined over the past two weeks (@cverna, @davdunc, @lbarczio, @cybette, @ttomecek), and together with @jflory7 the team is seeded with six members. @davdunc, the only volunteer present, expressed support; no objections were raised. @trix noted significant energy around skills work generally and pointed to existing RPM-build skills in ClawHub that Fedora could learn from.

  • Agreed: We will create the skills-reviewers team on Forgejo, seed it with @jflory7, @cverna, @davdunc, @lbarczio, @cybette, and @ttomecek, and post an open call on Matrix and Discourse for anyone else who wants to join. The team would get write access to ai-ml/skills-library with a lightweight review process. To start, at least one reviewer approval before merge.
  • Action: @jflory7 to create the skills-reviewers team on Forgejo, then close this issue. Continue planning in the ai-ml/skills-library repo. (Still working out the permissions needed to create the team. Will follow up shortly.)
  • Next step: Support @lbarczio on drafting human reviewer guidelines.

Assisted-by: Claude Opus 4.6 (1M context)

_Discussed in [2026-07-16 Fedora AI/ML SIG meeting](https://discussion.fedoraproject.org/t/fedora-ai-ml-sig-meeting-2026-07-16-skills-reviewers-team-approved-help-wanted-with-llama-cpp-and-navigating-gpu-infrastructure/196876)._ --- The SIG voted to create the skills-reviewers team. Five volunteers joined over the past two weeks (@cverna, @davdunc, @lbarczio, @cybette, @ttomecek), and together with @jflory7 the team is seeded with six members. @davdunc, the only volunteer present, expressed support; no objections were raised. @trix noted significant energy around skills work generally and pointed to existing RPM-build skills in ClawHub that Fedora could learn from. - **Agreed:** We will create the skills-reviewers team on Forgejo, seed it with @jflory7, @cverna, @davdunc, @lbarczio, @cybette, and @ttomecek, and post an open call on Matrix and Discourse for anyone else who wants to join. The team would get write access to `ai-ml/skills-library` with a lightweight review process. To start, at least one reviewer approval before merge. - **Action:** @jflory7 to create the skills-reviewers team on Forgejo, then close this issue. Continue planning in the `ai-ml/skills-library` repo. (Still working out the permissions needed to create the team. Will follow up shortly.) - **Next step:** Support @lbarczio on drafting human reviewer guidelines. <sub>_Assisted-by: Claude Opus 4.6 (1M context)_</sub>
Owner

I asked this on matrix on Friday but never got a response - should the team be named skills-reviewers or should it be called something else?

I asked this on matrix on Friday but never got a response - should the team be named `skills-reviewers` or should it be called something else?
Member

@tflink yes let's do skills-reviewers, But I wonder if that group doesn't need to be created in FAS first?

@tflink yes let's do `skills-reviewers`, But I wonder if that group doesn't need to be created in FAS first?
Owner

filed infra ticket for new FAS group and linked forge team: infra/tickets#13466

filed infra ticket for new FAS group and linked forge team: https://forge.fedoraproject.org/infra/tickets/issues/13466
Owner

Filed the ticket in the wrong place, new ticket in the correct place is forge/forge#677

Filed the ticket in the wrong place, new ticket in the correct place is https://forge.fedoraproject.org/forge/forge/issues/677
Member

@jflory7 and anyone interested - I opened a PR with an initial draft of the reviewer guidelines: ai-ml/skills-library#15. Feedback welcome!

@jflory7 and anyone interested - I opened a PR with an initial draft of the reviewer guidelines: https://forge.fedoraproject.org/ai-ml/skills-library/pulls/15. Feedback welcome!
Owner

The new team and matching FAS group have been created. @jflory7 and @tflink are the initial sponsors and I think that everyone mentioned has been added.

Note that you will need to logout of the forge and log back in before the team membership to take effect.

The new team and matching FAS group have been created. @jflory7 and @tflink are the initial sponsors and I think that everyone mentioned has been added. Note that you will need to logout of the forge and log back in before the team membership to take effect.
Member

Thanks Tim! I confirm that I see a "member" badge next to my name in the repo.

Thanks Tim! I confirm that I see a "member" badge next to my name in the repo.
Sign in to join this conversation.
No project
7 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ai-ml/tickets#31
No description provided.