feat(skills): ingest 650 de-branded skills from top OSS providers

.github/workflows/publish-registry.yml

@@ -12,6 +12,8 @@ on:
 jobs:
   build-and-publish:
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
@@ -60,3 +62,21 @@ jobs:
             registry.json
             registry-signature.json
           retention-days: 90
+
+      - name: Publish registry to the rolling release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          # One moving release holds the current registry. The Actions
+          # artifact above is retained separately for 90-day forensics.
+          # --latest=false keeps this rolling tag from displacing real
+          # version tags in the GitHub UI; the CLI addresses the tag
+          # directly, not /releases/latest/.
+          if ! gh release view registry-latest >/dev/null 2>&1; then
+            gh release create registry-latest \
+              --title "Skill registry (rolling)" \
+              --notes "Generated registry.json for the current main. Updated automatically; do not delete." \
+              --latest=false
+          fi
+          gh release upload registry-latest \
+            registry.json registry-signature.json --clobber

AGENTS.md

@@ -1,12 +1,12 @@
 ---
-description: starling — validation, registry, and contribution conventions.
+description: graycode-skills — validation, registry, and contribution conventions.
 globs: "*.md,*.py,*.toml,*.yaml,*.yml"
 alwaysApply: false
 ---
 
-# starling Conventions
+# graycode-skills Conventions
 
-Community skill packages for [hawk](https://github.com/GrayCodeAI/hawk).
+Community skill packages for [Graycode](https://github.com/GrayCodeAI/graycode-cli).
 
 ## Development workflow
 
@@ -41,11 +41,11 @@ ruff format --check .
 
 ## Ecosystem Boundaries
 
-- Extends Hawk through public skill and plugin surfaces only
-- Do not reference support engine repos (`graycode-router`, `yaad`, `tok`, `trace`, `sight`, `inspect`)
-- Do not reference `hawk/internal/*` or removed legacy paths
+- Extends Graycode through public skill and plugin surfaces only
+- Do not reference support engine repos (`graycode-router`, `harrier`, `shrike`, `swift`, `kestrel`, `merlin`)
+- Do not reference `graycode-cli/internal/*` or removed legacy paths
 
-For full hawk-eco extension guidelines, see [hawk/AGENTS.md](https://github.com/GrayCodeAI/hawk/blob/main/AGENTS.md).
+For full graycode-eco extension guidelines, see [graycode-cli/AGENTS.md](https://github.com/GrayCodeAI/graycode-cli/blob/main/AGENTS.md).
 
 <!-- gitnexus:start -->
 ## GitNexus — Code Intelligence

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-All notable changes to starling are documented in this file.
+All notable changes to graycode-skills are documented in this file.
 
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing to hawk Community Skills
 
-Thank you for your interest in contributing! Every skill helps make hawk smarter for everyone. This repository contains 12,171+ community-contributed skill packages organized into 31 domain categories.
+Thank you for your interest in contributing! Every skill helps make Graycode smarter for everyone. This repository contains 12,167 community-contributed skill packages organized into 27 domain categories.
 
 ## Ways to Contribute
 

README.md

@@ -1,10 +1,10 @@
-# hawk Community Skills
+# Graycode Community Skills
 
-Community skill packages for [hawk](https://github.com/GrayCodeAI/hawk) — the AI coding agent. This repository contains 12,171+ modular instruction packages that teach hawk specialized workflows across 31 categories.
+Community skill packages for [Graycode](https://github.com/GrayCodeAI/graycode-cli) — the AI coding agent. This repository contains 12,167 modular instruction packages that teach Graycode specialized workflows across 27 categories.
 
 ## What are Skills?
 
-Skills are self-contained Markdown instruction packages that hawk loads into its system prompt when activated. Each skill is a single `SKILL.md` file with YAML frontmatter, containing structured guidance for a specific workflow or technology. Skills are organized by domain under `categories/`.
+Skills are self-contained Markdown instruction packages that Graycode loads into its system prompt when activated. Each skill is a single `SKILL.md` file with YAML frontmatter, containing structured guidance for a specific workflow or technology. Skills are organized by domain under `categories/`.
 
 ## Quick Start
 
@@ -13,15 +13,15 @@ Skills are self-contained Markdown instruction packages that hawk loads into its
 
 ```bash
 # View available skills
-hawk skills list
+graycode skills list
 
 # Search for a skill
-hawk skills search api-testing
+graycode skills search api-testing
 
 # Install a skill
-hawk skills install python-pandas
+graycode skills install GrayCodeAI/graycode-skills python-pandas   # syntax is `install <owner/repo> [name]`
 
-# Use a skill in the hawk REPL
+# Use a skill in the graycode REPL
 /skills use python-pandas
 ```
 
@@ -96,10 +96,10 @@ gate.
 
 ## Ecosystem Boundaries
 
-- `starling` extends Hawk through public skill and plugin surfaces.
-- Do not reference support engine repos (`graycode-router`, `yaad`, `tok`, `trace`, `sight`, or `inspect`) as direct dependencies.
-- Do not reference `hawk/internal/*` or the removed legacy path `hawk/shared/types`.
-- Skills should assume Hawk is the product boundary.
+- `graycode-skills` extends Graycode through public skill and plugin surfaces.
+- Do not reference support engine repos (`graycode-router`, `harrier`, `shrike`, `swift`, `kestrel`, or `merlin`) as direct dependencies.
+- Do not reference `graycode-cli/internal/*` or the removed legacy path `graycode/shared/types`.
+- Skills should assume Graycode is the product boundary.
 
 ## Contributing
 

SECURITY.md

@@ -1,4 +1,4 @@
-# Security Policy — starling
+# Security Policy — graycode-skills
 
 ## Reporting a Vulnerability
 

api/openapi.yaml

@@ -1,20 +1,20 @@
 openapi: "3.1.0"
 info:
-  title: starling — Skill Registry Reference
+  title: graycode-skills — Skill Registry Reference
   description: |
-    Community skill packages for hawk. Each skill is a Markdown file with YAML
-    frontmatter that hawk loads into its system prompt when activated.
+    Community skill packages for Graycode. Each skill is a Markdown file with YAML
+    frontmatter that Graycode loads into its system prompt when activated.
 
     This is a skill registry — no HTTP server is exposed.
-    Skills are installed via the hawk CLI: `hawk skills install <name>`.
+    Skills are installed via the graycode CLI: `graycode skills install <owner/repo> <name>`.
   version: "0.0.1"
   license:
     name: MIT
-    url: https://github.com/GrayCodeAI/starling/blob/main/LICENSE
+    url: https://github.com/GrayCodeAI/graycode-skills/blob/main/LICENSE
   contact:
-    url: https://github.com/GrayCodeAI/starling
+    url: https://github.com/GrayCodeAI/graycode-skills
 
-# No servers — skills are installed via hawk CLI, not over HTTP.
+# No servers — skills are installed via the graycode CLI, not over HTTP.
 
 x-skill-format:
   required_frontmatter:
@@ -35,11 +35,11 @@ x-skill-format:
 
 x-cli-commands:
   install:
-    description: Install a skill into hawk
-    usage: hawk skills install <skill-name>
+    description: Install a skill into Graycode
+    usage: graycode skills install <owner/repo> <skill-name>
   search:
     description: Search the skill registry
-    usage: hawk skills search <query>
+    usage: graycode skills search <query>
   list:
     description: List installed skills
-    usage: hawk skills list
+    usage: graycode skills list

categories/ai-ml/agent-development-cli/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: agent-development-cli
+description: "Onboarding for an AI agent development CLI covering the full lifecycle: scaffold, build, evaluate, deploy, publish, and monitor agents."
+license: Apache-2.0
+tags:
+- ai
+- agents
+- cli
+- lifecycle
+---
+
+# Google Agents CLI Onboarding
+
+> [!TIP] **One-Time Setup**: To install the CLI and enable all 7 specialized
+> development skills in your coding agent, run the setup command:
+>
+> ```bash
+> uvx google-agents-cli setup
+> ```
+>
+> Alternatively, to install only the expert skills and let the agent handle
+> execution:
+>
+> ```bash
+> npx skills add google/agents-cli
+> ```
+
+## Overview
+
+This skill serves as the entrypoint for **agents-cli** — Google's toolkit for
+building, evaluating, and deploying AI agents on the Gemini Enterprise Agent
+Platform.
+
+Use this skill to perform the initial setup and identify the correct specialized
+workflows for your task.
+
+## The Agent Development Lifecycle
+
+After running the setup, the following specialized skills become available and
+will activate automatically based on your requests. Use this table to identify
+which skill to load for your current phase:
+
+| Phase | Specialized Skill | Purpose / When to Load |
+| :--- | :--- | :--- |
+| **0 — Understand** | `google-agents-cli-workflow` | **Clarify intent.** Define the agent spec in `.agents-cli-spec.md` before coding. |
+| **1 — Study** | `google-agents-cli-workflow` | **Leverage samples.** Study existing agent samples (e.g., `ambient-expense`) before scaffolding. |
+| **2 — Scaffold** | `google-agents-cli-scaffold` | **Create/Enhance.** Initialize the project structure, CI/CD, and infrastructure templates. |
+| **3 — Build** | `google-agents-cli-adk-code` | **Implement.** Write agent logic, tools, callbacks, and manage state using ADK APIs. |
+| **4 — Evaluate** | `google-agents-cli-eval` | **Validate Quality.** Run systematic evaluations (LLM-as-judge). |
+| **5 — Deploy** | `google-agents-cli-deploy` | **Go Production.** Deploy to Agent Runtime (Vertex AI), Cloud Run, or GKE. |
+| **6 — Publish** | `google-agents-cli-publish` | **Register.** Make your agent available as a tool in Gemini Enterprise. |
+| **7 — Observe** | `google-agents-cli-observability` | **Monitor.** Set up Cloud Trace, prompt-response logging, and BigQuery analytics. |
+
+## Key CLI Commands
+
+Below are the primary commands you will use throughout the development
+lifecycle:
+
+| Command | Description |
+| :--- | :--- |
+| `agents-cli setup` | Install the CLI and configure skills in your coding agent. |
+| `agents-cli scaffold <name>` | Create a new agent project from a template. |
+| `agents-cli eval run` | Run the agent and grade the traces in a single step (generate + grade). |
+| `agents-cli deploy` | Deploy your agent to Google Cloud (Agent Runtime, Cloud Run, GKE). |
+| `agents-cli publish gemini-enterprise` | Register your deployed agent with Gemini Enterprise. |
+
+*For the full list of available commands and global options, run `agents-cli
+--help`.*
+
+## Next Steps
+
+Follow this sequence to initiate the development workflow:
+
+1.  **Execute Setup:** Run the `uvx` or `npx` command in the `[!TIP]` box above
+    to install the CLI and enable the specialized skills in your environment.
+2.  **Verify Installation:** Run `agents-cli info` to confirm the installation
+    and view the active project configuration.
+3.  **Initiate Phase 0:** Ask the user for their core requirements (agent
+    purpose, external tools, deployment target) and document them in
+    `.agents-cli-spec.md` before writing any code.
+
+## Reporting Issues
+
+Report bugs or improvements at [Google Agents CLI Issues](https://github.com/google/agents-cli/issues).
+
+## Supporting Links
+
+*   [Google Agents CLI Documentation](https://github.com/google/agents-cli/tree/main/docs/src)