@zibby/skill-ids 0.1.0 → 0.2.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zibby/skill-ids",
-  "version": "0.1.0",
+  "version": "0.2.1",
   "description": "Single authoritative Zibby skill-id map (zero-dep leaf). The one source of truth for well-known skill ids — every consumer (agent-workflow, core, skills, backend, templates) imports it, so the ids can never drift.",
   "type": "module",
   "main": "src/index.js",

package/src/index.js

@@ -83,6 +83,14 @@ export const SKILL_IDS = Object.freeze({
   // `linkedin` — publish to the connected PERSONAL LinkedIn profile
   // (linkedinSkill → linkedin_publish_post).
   LINKEDIN: 'linkedin',
+  // `hubspot` — HubSpot CRM (contacts/companies/deals/tickets/notes/tasks/
+  // feedback_submissions/custom) over the HubSpot REST API. OAuth 2.0
+  // integration: the user connects HubSpot in Integrations; the backend
+  // (handlers/hubspot.js) auto-refreshes the access token and the skill
+  // resolves it via resolveIntegrationToken('hubspot'). Declaring SKILLS.HUBSPOT
+  // gates deploy on a connected HubSpot (backend SKILL_INTEGRATION_MAP:
+  // 'hubspot' → INTEGRATIONS.HUBSPOT). Backed by hubspotSkill in @zibby/skills.
+  HUBSPOT: 'hubspot',
   // `chat_notify` — provider-agnostic chat notification. Routes to Slack OR Lark
   // depending on which integration the project has connected. Backend renders
   // this as "Slack OR Lark" via {any:[...]}.
@@ -142,9 +150,67 @@ export const SKILL_IDS = Object.freeze({
 
 /**
  * SKILL_META — pure-data static metadata per id (toggleable / requiresIntegration
- * / tier / display / binary). STUB for now: Phase 2 of the skills-platform
- * migration populates this and points each skill object's `meta` at
- * SKILL_META[id]. Exported empty today so P2 can fill it without another wiring
- * change. See strategy/skills-platform-architecture.md.
+ * / tier / display / binary). Phase 2 of the skills-platform migration.
+ *
+ * This is the SINGLE SOURCE OF TRUTH for a skill's toggle metadata. Every one of
+ * the five toggle surfaces derives from here:
+ *   1. engine gate      — the skill object sets `meta = SKILL_META[id]` by
+ *                         reference (@zibby/skills), and claude-strategy's
+ *                         isToggleableOff() reads `skill.meta.toggleable`.
+ *   2. backend registry — a build-emitted JSON manifest (backend cannot ESM-
+ *                         import() this ESM leaf: it's CJS, this isn't a backend
+ *                         dep, and the .jsc control-plane can't dynamic-import) —
+ *                         see backend/scripts/gen-skill-meta.mjs →
+ *                         backend/src/services/skill-meta.json.
+ *   3. cloud marketplace sync, 4. self-host deploy, 5. self-host catalog list —
+ *                         all flow from the backend registry (#2).
+ *
+ * Shape per id:
+ *   { toggleable, requiresIntegration, tier, display:{ name, description },
+ *     binary?:{ name, version, sha256 } }
+ *
+ * A skill absent from this map is "not toggleable" (the default for everything
+ * except the two no-connection toggleable skills). Ids are append-only (see the
+ * governance note above). Objects are DEEP-frozen so a skill object that shares a
+ * `meta` reference cannot mutate the static map.
+ *
+ * NOTE (byte-identical contract): `display.name`/`display.description` MUST equal
+ * the strings the backend previously hardcoded in NO_INTEGRATION_TOGGLEABLE_SKILLS
+ * (skill-integrations.js) — the backend now derives that map from here, so any
+ * edit changes the marketplace/status display. See strategy/skills-platform-architecture.md.
  */
-export const SKILL_META = Object.freeze({});
+const deepFreeze = (o) => {
+  if (o && typeof o === 'object' && !Object.isFrozen(o)) {
+    Object.values(o).forEach(deepFreeze);
+    Object.freeze(o);
+  }
+  return o;
+};
+
+export const SKILL_META = deepFreeze({
+  'codebase-memory': {
+    toggleable: true,
+    requiresIntegration: false,
+    tier: 2,
+    display: {
+      name: 'Codebase memory',
+      description:
+        'Code-graph + semantic index over the checked-out repo (architecture map, '
+        + 'dependency/call-path tracing, change detection). Runs locally on the '
+        + 'agent image — no connection required.',
+    },
+  },
+  'code-scan': {
+    toggleable: true,
+    requiresIntegration: false,
+    tier: 2,
+    display: {
+      name: 'Code scan',
+      description:
+        'Stack-smart deterministic linter (oxlint for JS/TS, …). Detects the repo\'s '
+        + 'stack and runs the matching baked linter over the changed code, feeding '
+        + 'structured findings to the reviewer. Runs locally on the agent image — '
+        + 'no connection required.',
+    },
+  },
+});