skilldrop-cli 0.13.8 → 0.13.9

package/README.md

@@ -22,7 +22,7 @@ Install one pack. Every role pack also brings `core` (intake, critique, review c
 - **Explaining things to decision-makers:** `stakeholder-comms` — audience profiles, exec summaries, decision logs, guides. [Open pack](https://sananthanarayan.github.io/skilldrop/packs/stakeholder-comms/)
 - **On-brand decks and flyers:** `design` — capture your brand once, then build `.pptx` decks and print-ready flyers with your logo, colours and fonts. [Open pack](https://sananthanarayan.github.io/skilldrop/packs/design/)
 - **Adopting and building AI:** `ai-engineering` — readiness, use-case triage, policy, agent loops, budgets, agent threat models, evals. [Open pack](https://sananthanarayan.github.io/skilldrop/packs/ai-engineering/)
-- **Building on the Claude API:** `claude-api` — prompt caching, token budgets, eval generation, tool schemas. [Open pack](https://sananthanarayan.github.io/skilldrop/packs/claude-api/)
+- **Building on the Claude API:** `api-builder` — prompt caching, token budgets, eval generation, tool schemas. [Open pack](https://sananthanarayan.github.io/skilldrop/packs/api-builder/)
 - **Everyone:** `core` on its own. [Open pack](https://sananthanarayan.github.io/skilldrop/packs/core/)
 
 ## Start in one command

package/bin/skilldrop.js

@@ -879,11 +879,23 @@ function removeHooksFor(skill, dest, ide) {
 
 /* ---------- commands ---------- */
 
+/* Packs that were renamed, so an old command or script keeps working. claude-api became
+   api-builder in 0.13.9: Claude Code reserves plugin names that start with "claude-". */
+const PACK_ALIASES = { "claude-api": "api-builder" };
+function packAlias(flags, ps) {
+  const n = flags.pack;
+  if (n && ps && !ps[n] && PACK_ALIASES[n] && ps[PACK_ALIASES[n]]) {
+    console.error(`note: pack '${n}' is now '${PACK_ALIASES[n]}' — use --pack ${PACK_ALIASES[n]}`);
+    flags.pack = PACK_ALIASES[n];
+  }
+}
+
 function expandNames(args, cat) {
   if (args.flags.all) return skillsIn(cat);
   if (args.flags.pack) {
     const ps = packsOf(cat);
     if (!ps) die(`catalog '${cat.source}' defines no packs — install skills by name`);
+    packAlias(args.flags, ps);
     const p = ps[args.flags.pack];
     if (!p) die(`unknown pack '${args.flags.pack}' in catalog '${cat.source}'`);
     return packMembers(ps, args.flags.pack, "skills");
@@ -1535,6 +1547,7 @@ function installLoops(args) {
   if (!names.length && args.flags.pack) {
     const ps = packsOf(cat);
     if (!ps) die(`catalog '${cat.source}' defines no packs`);
+    packAlias(args.flags, ps);
     const pk = ps[args.flags.pack];
     if (!pk) die(`unknown pack '${args.flags.pack}' in catalog '${cat.source}'`);
     names = packMembers(ps, args.flags.pack, "loops");
@@ -1693,6 +1706,7 @@ function firstValueLines(p) {
 function infoPack(args) {
   const cat = resolveCatalog(args.flags.from);
   const ps = packsOf(cat) || die(`catalog '${cat.source}' has no packs`);
+  packAlias(args.flags, ps);
   const name = args.flags.pack;
   const p = ps[name] || die(`unknown pack '${name}' — available: ${Object.keys(ps).join(", ")}`);
   if (args.flags.json)

package/catalogue.json

@@ -1,7 +1,7 @@
 {
   "$comment": "RFC-0034. The catalogue index: pack display order and the outcome browse axis (RFC-0026). Pack metadata lives in packs/<pack>/pack.json; membership is the folders — a skill is in a pack because it sits at packs/<pack>/skills/<name>/.",
   "version": "1.0.0",
-  "packs": ["core", "solution-architect", "product-manager", "dev-team", "sre-oncall", "stakeholder-comms", "design", "ai-engineering", "claude-api"],
+  "packs": ["core", "solution-architect", "product-manager", "dev-team", "sre-oncall", "stakeholder-comms", "design", "ai-engineering", "api-builder"],
   "outcomes": {
     "decide-what-to-build": {
       "for": "Product managers · founders · strategists",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skilldrop-cli",
-  "version": "0.13.8",
+  "version": "0.13.9",
   "description": "Portable AI-agent skills for the deliverables knowledge workers ship \u2014 diagrams, ADRs, PRDs, runbooks, decks, reviews \u2014 installable into Claude Code, Cursor, Kiro, and any IDE that takes custom instructions. One command per skill or per role-based pack.",
   "author": {
     "name": "Sanjay Ananthanarayan",

package/packs/{claude-api → api-builder}/pack.json

@@ -1,9 +1,9 @@
 {
   "description": "Skills for teams building on the Anthropic API — prompt caching, token budgeting, eval generation for skills, and tool-use schema writing.",
-  "display_name": "Claude API",
+  "display_name": "API builder",
   "keywords": ["anthropic", "prompt-caching", "tokens", "tool-use", "evals"],
   "links": {
-    "documentation": "https://sananthanarayan.github.io/skilldrop/packs/claude-api/"
+    "documentation": "https://sananthanarayan.github.io/skilldrop/packs/api-builder/"
   },
   "maintainers": [
     {

package/packs/dev-team/skills/contribution-wizard/SKILL.md

@@ -18,7 +18,7 @@ Ask these questions in a single block — not one at a time:
 > 1. **Purpose**: what does this skill do in one sentence?
 > 2. **Input**: what does the agent receive? (paste, file, structured data, conversational context)
 > 3. **Output**: what does the agent produce? (artifact type, format, length)
-> 4. **Pack**: which role pack does it belong to? (solution-architect / product-manager / dev-team / sre-oncall / stakeholder-comms / ai-engineering / claude-api / new pack)
+> 4. **Pack**: which role pack does it belong to? (solution-architect / product-manager / dev-team / sre-oncall / stakeholder-comms / ai-engineering / api-builder / new pack)
 > 5. **Is it a gate?** Does it emit a pass/fail verdict, or generate an artifact?
 > 6. **Related skills**: which existing skills does it complement or hand off to?
 > 7. **External deps**: does it need API keys, npm packages, or pip libraries?

package/packs/dev-team/skills/contribution-wizard/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "contribution-wizard",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Guides an author through creating a new skilldrop skill from scratch — generates the manifest, SKILL.md, eval cases, and skill-catalogue entry from a plain-language description of the skill's purpose. Use when authoring a new skill for this repo or a private fork, ensuring a new skill meets the schema and validation requirements before submission.",
   "entrypoint": "SKILL.md",
   "deps": { "npm": [], "pip": [] },

package/profiles.json

@@ -16,7 +16,7 @@
     },
     "full": {
       "description": "The complete catalogue: every pack, every reviewer agent, every loop.",
-      "packs": ["core", "solution-architect", "product-manager", "dev-team", "sre-oncall", "stakeholder-comms", "design", "ai-engineering", "claude-api"],
+      "packs": ["core", "solution-architect", "product-manager", "dev-team", "sre-oncall", "stakeholder-comms", "design", "ai-engineering", "api-builder"],
       "agents": ["devils-advocate", "security-reviewer", "code-quality"],
       "loops": ["discover", "design", "build", "release", "operate", "ship-a-draft"]
     }