Primary finding
Parent resolution fallback uses current repo as parent on non-forks, will list the canonical repo's own forks unintentionally
lowbugmedium
- skills/fork-release-tracker/SKILL.md:47-54
On the canonical (non-fork) parent repo `AntFleet/aeon-bench`, `.parent.full_name` is null and the jq fallback returns `.full_name`, so PARENT_REPO becomes the current repo and the skill happily lists forks of itself. That matches the var docstring ('on a non-fork, uses the current repo itself as parent'), so on the canonical repo it's intended. However, on a fork-of-a-fork (rare but legal), `.parent.full_name` is the intermediate fork, not the ultimate source, so the skill will scan the wrong universe of forks. The doc claims 'parent', but GitHub's `.parent` is one level up, not the root. Use `.source.full_name // .full_name` to get the true source when traversing the fleet.
Recommendation
Change the jq filter to `.source.full_name // .full_name` (source is the ultimate upstream on GitHub's fork API), or document explicitly that nested forks must use PARENT_OVERRIDE.