[ENHANCEMENT] Awesome Anti Gravity Skills

[martincebis-lgtm]

Problem (one or two sentences)

The project at https://github.com/sickn33/antigravity-awesome-skills supports many coding agents but does not appear to integrate directly with roocode.
The skills can likely be imported and manually used at the moment but this is not as convenient for users as using this system is for other codign platforms.

It would be a great if that project directly supported roocode or perhaps for roocode to be more in control, if roocode could integrate what is there into its system.

Context (who is affected and when)

Any user wanting to use the exploding number of skills in that repository.

Desired behavior (conceptual, not technical)

The user should be able to easily select and configure the right skills for the current project or the agent should be able to load them automatically or on demand.

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I have been looking into this issue and wanted to share some observations and questions before proposing a plan.

Roo Code already has a built-in skills system that supports:

• Project-level skills stored in .roo/skills/ (or .agents/skills/) within a project
• Global skills stored in ~/.roo/skills/ (or ~/.agents/skills/)
• Skill discovery, creation, deletion, mode filtering, and invocation via slash commands or the skill tool

The antigravity-awesome-skills repository is an external catalog of community-contributed skill files for various coding agents. Integrating it would essentially mean building a way to browse and import skills from that (or similar) external catalogs into the existing Roo Code skills infrastructure.

Before I propose a concrete plan, I have a few questions:

1. Scope of integration: Are you envisioning a built-in "skill marketplace/browser" within Roo Code that fetches from that repository (or similar registries)? Or something lighter, like a CLI command or UI action to import a skill from a URL/GitHub repo?

2. Repository coupling: Should Roo Code be tightly coupled to that specific repository, or would a more generic approach be preferred (e.g., support importing skills from any GitHub repo that follows a certain structure)?

3. Automatic vs. manual: The issue mentions both "easily select and configure" and "load them automatically or on demand." Is the primary goal a manual browse-and-install flow, or should the agent also be able to discover and load skills at runtime based on the current project context?

4. Priority: Given the scope, would a first pass that simply allows importing individual skill files from a URL (or cloning a skills repo into the global/project skills directory) be a reasonable starting point?

These questions would help narrow down the implementation approach significantly. Please tag @roomote in your response with the answers, and I will be happy to propose a concrete implementation plan.

[martincebis-lgtm]

I think that there are many libraries of skills and this is one of them but it is more than that as it says on the tin:
"1340 Agentic Skills for Claude Code, Gemini CLI, Cursor, Copilot & More" but not roocode. Presumably the plugins are value added over a pure directory structure of 1340 skills. It should help manage getting the right skills because 1340 is otherwise confusing.

TBH I have not tried what the plugin does to help with skills management as I am not an active user of the other platforms (but someone looking at this could 'go to school' to look at how it integrates with those other tools ;-) ) ... but the FAQ gives you an idea.
https://github.com/sickn33/antigravity-awesome-skills?tab=readme-ov-file#quick-faq

But as an active user of roo what I would EXPECT of a skills manager plugin tied to an exploding number of skills options would be the following:

1. A way to add, organise and browse and bring skills manually and easily into my project scope. The assumption is that it is a fools feast. Plenty of skills options but no way of knowing which is the best, best for my project, or which might be the best given the current task.
2. An LLM/ Agent driven way to do the same by looking at a project spec/plan/existing code and picking (or suggesting) the right skills. That might be project lifecycle driven (ie. moving to maintenance so focus on security & maintenance). I am guessing that this is what they do with 'bundles' and 'workflow'. Or that could be context driven. For example if the majority of my project is typescript but there is a small component in another language, picking up and using some skills related to that if that section of code is worked on would make sense otherwise I don't want it cluttering the context and costing me.
3. Primarily something that delivers knowledge density for what the present task is. A way not to clutter and fill my context with skills. Right skills at the right time. To do that a skills manager must record a lot more than a number of .md files in a directory that I can browse. It should house metadata that includes effectiveness for my codebase (could be learned) of due to the ratings and experience of other users (agents?) in different code contexts.

Does that help?