chore: Reconcile skills/ directory with rossoctl/agent-skills (3-month divergence)
Maintainers usually reply within 3 days
@rubambiza is already working on this.
Since Aug 25, 2026.
Assessment
This issue has not been assessed yet.
Description
Problem
The `skills/` directory in this repo is out of date relative to the canonical skill definitions in rossoctl/agent-skills. The automation repo's skills last changed 2026-06-01 (commit `0309d41`); the agent-skills repo was last updated 2026-08-20 (commit `f4ae90e`), a gap of roughly 3 months.
Divergence Summary
Skills present in `automation/skills/` but not in `agent-skills/skills/`
None — both skills here have counterparts there, under renamed/split directories.
Skills present in `agent-skills/skills/` but missing from `automation/skills/`
| Skill (agent-skills) | Notes |
|---|---|
| `automation-health-dashboard` | No counterpart in automation |
| `dep-bump-fixer` | Split from `dep-bump` (automation has scanner + fixer combined in one dir) |
| `github-pr-review` | Absent from automation |
| `github-weekly-report` | Absent from automation |
| `link-health-fixer` | Split from `link-health` (same split as dep-bump) |
Skills present in both, but structurally diverged
| Skill (automation) | Counterpart (agent-skills) | Divergence |
|---|---|---|
| `dep-bump/SKILL.md` | `dep-bump-scanner/SKILL.md` | automation version hardcodes `kagenti` org + `~/kagenti/` clone path; agent-skills version is org-agnostic (`--org` flag), portable, ships `reference/` and `scripts/` subdirs |
| `dep-bump/FIXER-SKILL.md` | `dep-bump-fixer/SKILL.md` | Same org-hardcoded vs. generic pattern |
| `link-health/SKILL.md` | `link-health-scanner/SKILL.md` | automation version hardcodes `kagenti` + inline scan logic; agent-skills version is org-agnostic with `--help`, `scripts/`, and `reference/` subdirs |
Proposal
- Replace the contents of `automation/skills/` with the current skill tree from `rossoctl/agent-skills/skills/`, preserving any automation-specific overrides as noted above.
- Establish a process (or CI check) to keep these in sync going forward — see the open discussion at rossoctl/automation#62 on ownership for automation adopters.
Out of Scope
Changing the `agent-skills` repo itself — that repo is the source of truth; changes flow from there.
References
- Canonical skill source: rossoctl/agent-skills/tree/main/skills
- Last commit to `automation/skills/`: `0309d41` (2026-06-01) — feat: Add dependency bump fixer
- Last commit to `agent-skills/skills/`: `f4ae90e` (2026-08-20) — fix: Reject --repos entries outside --org
- Ownership discussion: rossoctl/automation#62
- Dominant language
- Shell
- Stars
- 2
- Forks
- 4
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 12
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/automation
-
enhancement repoman
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rossoctl/automation#101 ·
Maintainers usually reply within 3 days
-
enhancement repoman
Difficulty 4/5 3-5 days Newbie friendliness 52/100
rossoctl/automation#99 ·
Maintainers usually reply within 3 days
-
enhancement repoman
Difficulty 4/5 3-5 days Newbie friendliness 48/100
rossoctl/automation#98 ·
Maintainers usually reply within 3 days
-
enhancement repoman
Difficulty 5/5 Over a week Newbie friendliness 45/100
rossoctl/automation#96 ·
Maintainers usually reply within 3 days
-
blocked enhancement repoman
Difficulty 5/5 Over a week Newbie friendliness 35/100
rossoctl/automation#81 ·
Maintainers usually reply within 3 days
All issues in rossoctl/automation
Similar issues
-
Do not leave the distro Suricata service enabled after make installPossibly taken @himanishpuri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Ergane-Foundation/vajra#49 · 2 comments ·
-
good first issue need help packaging
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
phonology024/babelscribe#23 ·
-
chore
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
alunduil/alunduil-chezmoi#882 ·
Maintainers usually reply within 1 day
-
package-update
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
oSoWoSo/vOid_Community_repOsitory#319 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rios0rios0/pipelines#726 ·
Maintainers usually reply within 1 day