Issue Summary
Forge developers can create custom Rovo actions (e.g. a “Search with JQL (POC)” skill) and use them within their own Forge agents, and can expose them to no‑code agents via the read:chat:rovo scope and the skills picker. However, these Forge actions are app-scoped only and cannot be promoted to behave like platform-level, built-in skills such as the out‑of‑the‑box “Search with JQL”.

This leads to a gap for customers who want to:

• Implement organization-specific variants of core skills (e.g. custom JQL search behavior or guardrails), and
• Reuse those custom skills consistently across multiple agents and apps, without having to manually rewire the same action into each agent or re‑implement the logic per app.

Today, even if a Forge action has the same name and description as the built‑in “Search with JQL”, it:

• Is not globally registered in Rovo’s skill catalog,
• Cannot be discovered and used by all agents by default, and
• Cannot be invoked by agents from other Forge apps as a shared/global capability.

This behavior is confusing for customers who expect their custom JQL skill to be invokable “from other agents like the OOTB ‘Search with JQL’ skill,” and it limits reuse of richer, enterprise-specific skills built on Forge.