@groupby/ai-dev 0.5.20 → 0.5.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groupby/ai-dev",
-  "version": "0.5.20",
+  "version": "0.5.21",
   "description": "Interactive installer for Rezolve Ai development content",
   "type": "module",
   "bin": {
@@ -15,7 +15,7 @@
   "scripts": {
     "prebuild": "rm -rf skills teams toolsets && cp -r ../skills ./skills && cp -r ../teams ./teams && cp -r ../toolsets ./toolsets",
     "build": "tsup",
-    "prepublishOnly": "npm run build",
+    "prepare": "npm run build",
     "test": "vitest run",
     "test:watch": "vitest",
     "test:coverage": "vitest run --coverage"

package/skills/README.md

@@ -4,7 +4,7 @@ This folder manages all skills, archived skills, and examples/instructions on us
 
 All skills in this `skills/library/` should represent _generally useful skills_ that might be used across teams.
 
-If any particular skill goes missing, note that it may have simply been archived (see [the archive](skills/archived/)) and may no longer be recommended for use. Ideally skills are not simply deleted from this repository, since others may be expecting them to be there.
+If any particular skill goes missing, note that it may have simply been archived (see [the archive](archived/)) and may no longer be recommended for use. Ideally skills are not simply deleted from this repository, since others may be expecting them to be there.
 
 ## Usage
 
@@ -58,4 +58,45 @@ license: Complete terms in LICENSE.txt
 See `docs/ai/skills/frontend-design/SKILL.md` and follow closely.
 ```
 
+## Third-party skills
+
+Skills authored outside the company can be vendored into a team's folder under
+`teams/<team>/third-party/<lib>/<skill>/`, each with the upstream `SKILL.md`
+(vendored verbatim at a pinned commit) plus a `skill-meta.yml` provenance
+sidecar. They are curated per team by evaluation status: `evaluating`,
+`recommended`, or `deprecated`.
+
+The lifecycle is fetch, vendor, evaluate, and promote:
+
+1. **Fetch + Vendor** in one step with the authoring command — paste a GitHub
+   URL to the skill folder and it writes the pinned `SKILL.md` plus a generated
+   `skill-meta.yml`:
+   ```bash
+   npx @groupby/ai-dev vendor <github-url> --team <team>
+   ```
+   Or do it manually: fetch into a scratch directory (for example,
+   `npx skills add <owner/repo> --copy`), then copy the single skill folder into
+   `teams/<team>/third-party/<lib>/<skill>/`, recording the source, pinned
+   commit, and `status: evaluating` in `skill-meta.yml`.
+2. **Evaluate** it in a real project with
+   `npx @groupby/ai-dev install skill <skill-name>` (naming a skill installs it
+   regardless of status).
+3. **Promote** it to `status: recommended` once proven, or graduate it into
+   `skills/library/` as a first-party skill (dropping the sidecar).
+
+A `recommended` third-party skill installs with its team like any other skill;
+`evaluating` and `deprecated` skills are held back from team installs unless you
+pass `--include-evaluating` or `--include-deprecated`. Naming a skill directly
+with `install skill <name>` always installs it. If a name is shared by more than
+one skill in the same tier (for example two teams that each vendored it), the CLI
+lists the matches and asks you to scope it with `install skill <team>/<name>` or
+`--team <team>`. See
+[content conventions](../docs/content-conventions.md) for the `skill-meta.yml`
+schema and the full rules.
+
+The `skill-meta.yml` sidecar is required. A vendored skill missing it has no
+provenance or status, so `list` shows it as `[no status] unknown source`, team
+installs skip it, and installing it by name still works but prints a
+`no recorded status` note. Add the sidecar to make it a fully curated skill.
+
 Note that we MUST include the skill boilerplate in any official skills location (eg. `.github/skills/`, etc.) to enable discovery and usage. We then copy the entire skill into `docs/ai/skills/` to leave it intact, though we don't technically need the boilerplate.

package/teams/rangers/third-party/mattpocock/grilling/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: grilling
+description: Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
+---
+
+Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it.
+
+Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask _now_ without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round.
+
+Format a round like so:
+
+```
+❓ **Q1** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
+
+➡️ <your recommended answer>
+
+---
+
+❓ **Q2** - **<question title>**: <question body, might be multiple paragraphs, including multiple choices>
+
+➡️ <your recommended answer>
+```
+
+Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a _later_ round, not this one.
+
+Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a sub-agent to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. The _decisions_ are the user's: put each to them and wait.
+
+The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Do not act on it until the user confirms you have reached a shared understanding.

package/teams/rangers/third-party/mattpocock/grilling/skill-meta.yml

@@ -0,0 +1,14 @@
+source: mattpocock/skills
+upstreamName: grilling
+pinnedCommit: 6654f6b60cd9d5be8b54c6fafe44346dabeb3b76
+vendoredOn: 2026-08-24
+status: evaluating
+agents: [copilot, claude, codex]
+reviewedBy: jasonwelsh
+notes: >-
+  Vendored verbatim from skills/productivity/grilling/SKILL.md. Upstream ships a
+  nested agents/openai.yaml alongside SKILL.md; it was dropped to keep the
+  vendored skill flat (the CLI installer copies top-level files only). Overlaps
+  the first-party rangers/team-phase-planning loop and the existing grill-me
+  skills in agentic-checkout and fhr-ai-team; evaluating whether grilling
+  replaces or is an explicit non-conflict before any promotion to recommended.