@zibby/skill-ids 0.1.0

package/package.json

@@ -0,0 +1,31 @@
+{
+  "name": "@zibby/skill-ids",
+  "version": "0.1.0",
+  "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",
+  "exports": {
+    ".": "./src/index.js",
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "src"
+  ],
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "keywords": [
+    "zibby",
+    "skills",
+    "agent-workflow",
+    "constants"
+  ],
+  "author": "Zibby",
+  "license": "MIT",
+  "homepage": "https://zibby.dev",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ZibbyDev/zibby-agent"
+  },
+  "dependencies": {}
+}

package/src/index.js

@@ -0,0 +1,150 @@
+/**
+ * @zibby/skill-ids — the SINGLE authoritative skill-id map (zero-dep leaf).
+ *
+ * Well-known skill IDs live HERE, once. Everyone imports this leaf:
+ *
+ *     @zibby/skill-ids   (zero deps, bottom of the graph)
+ *        ↑            ↑         ↑          ↑
+ *     agent-workflow  core   skills   backend / frontend / templates
+ *
+ *  - `agent-workflow` (the engine) does NOT import this — it binds skills by
+ *    string id via its registry, so it stays decoupled from concrete ids.
+ *  - `@zibby/skills` re-exports `SKILL_IDS as SKILLS` (its `registerSkill()`
+ *    calls + `SKILLS.X` references resolve off this object).
+ *  - `@zibby/core` re-exports `SKILL_IDS as SKILLS`, so the ~71 templates that
+ *    `import { SKILLS } from '@zibby/core'` get the COMPLETE map — no drift.
+ *
+ * Being a zero-dependency leaf, nothing it imports can create a cycle
+ * (dep order is agent-workflow → core → skills → templates; this sits below
+ * all of them).
+ *
+ * GOVERNANCE (pin these):
+ *  - Ids are APPEND-ONLY. Never remove or rename an id — frozen template
+ *    bundles resolve `SKILLS.X` forever. Renames go through an alias here.
+ *  - This map is the union superset of every id any consumer has ever
+ *    exposed, so re-pointing a consumer's `SKILLS` export at it can only ADD
+ *    keys, never drop one (non-breaking within a caret-locked minor).
+ */
+
+export const SKILL_IDS = Object.freeze({
+  BROWSER: 'browser',
+  JIRA: 'jira',
+  GITHUB: 'github',
+  GITLAB: 'gitlab',
+  // `figma` — read-only design context over the Figma REST API (figmaSkill in
+  // @zibby/skills). OAuth integration; resolves the access token per-call via
+  // the backend. Declaring SKILLS.FIGMA gates deploy on a connected Figma
+  // (backend SKILL_INTEGRATION_MAP: 'figma' → INTEGRATIONS.FIGMA).
+  FIGMA: 'figma',
+  // `linear` — api-key paste-token issue tracker (linearSkill, served over MCP
+  // via bin/mcp-skill.mjs). Backend SKILL_INTEGRATION_MAP: 'linear' →
+  // INTEGRATIONS.LINEAR.
+  LINEAR: 'linear',
+  // `plane` — api-key issue tracker (planeSkill spawns the official
+  // plane-mcp-server).
+  PLANE: 'plane',
+  // `open-design` — design/deck authoring + export over the OpenDesign REST API
+  // (the Zibby-managed `open-design` app; the id equals the catalog appType).
+  // OPTIONAL: declaring it does NOT gate deploy (no requiresIntegration).
+  OPEN_DESIGN: 'open-design',
+  // `git` — provider-agnostic clone/list/explore tools. Auto-auths against
+  // GitHub OR GitLab depending on which token the runner injected. Backend
+  // SKILL_INTEGRATION_MAP renders this as "GitHub or GitLab" via {any:[...]}.
+  GIT: 'git',
+  // `git-write` — REQUIRED extension of `git`: the same read tools PLUS the
+  // provider-agnostic mutation tool git_open_pr. Repo-MUTATING agents declare
+  // this so deploy is gated on "GitHub OR GitLab" connected; backend maps it to
+  // REQUIRED_INTEGRATION_MAP {any:[github,gitlab]}. Read-only clone agents keep
+  // GIT. Backed by gitWriteSkill.
+  GIT_WRITE: 'git-write',
+  SLACK: 'slack',
+  LARK: 'lark',
+  // `discord` — post messages / list channels in the user's Discord server as
+  // their bot (paste-token integration, provider 'discord'). Backed by
+  // discordSkill (served over bin/mcp-skill.mjs as mcp__discord__* tools).
+  DISCORD: 'discord',
+  // Notion OAuth — multi-workspace integration. Used by notify-notion and as a
+  // destination for any report-producing parent template.
+  NOTION: 'notion',
+  // `google-docs` — create/append/read Google Docs (googleDocsSkill, served over
+  // MCP as mcp__gdocs__* tools). Backed by the drive.file-scoped 'google' OAuth;
+  // backend REQUIRED_INTEGRATION_MAP: 'google-docs' → INTEGRATIONS.GOOGLE.
+  GOOGLE_DOCS: 'google-docs',
+  // `lark-docs` — read/create/append Lark/Feishu documents (larkDocsSkill, served
+  // over MCP as mcp__larkdocs__* tools). REUSES the connected Lark app
+  // (integration 'lark'); backend REQUIRED_INTEGRATION_MAP: 'lark-docs' →
+  // INTEGRATIONS.LARK.
+  LARK_DOCS: 'lark-docs',
+  // `doc_source` — INTEGRATION-GATE MARKER (like `circleci`), not a runtime MCP
+  // skill: no skill registers under this id (the resolver warns + skips it).
+  // Declaring it gates deploy on a document source via the OR-group
+  // {any:[google, notion, lark]}. Used by the prd-review template.
+  DOC_SOURCE: 'doc_source',
+  // `linkedin` — publish to the connected PERSONAL LinkedIn profile
+  // (linkedinSkill → linkedin_publish_post).
+  LINKEDIN: 'linkedin',
+  // `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:[...]}.
+  CHAT_NOTIFY: 'chat_notify',
+  SENTRY: 'sentry',
+  MEMORY: 'memory',
+  RUNNER: 'runner',
+  SKILL_INSTALLER: 'skill-installer',
+  CORE_TOOLS: 'core-tools',
+  CHAT_MEMORY: 'chat-memory',
+  // `kv-memory` — general-purpose per-agent persistent KV. Auto-namespaces every
+  // key by WORKFLOW_TYPE so each agent gets a disjoint key space in the same
+  // per-project partition. Backed by kvMemorySkill.
+  KV_MEMORY: 'kv-memory',
+  // `dataset-store` — durable, queryable structured-record store (append rows,
+  // run SQL-style aggregations later for reports). Auths with the run's OWN
+  // project token → UNGATED, like kv-memory. Opt-in (NOT alwaysLoad). Backed by
+  // datasetStoreSkill.
+  DATASET_STORE: 'dataset-store',
+  // `chart-render` — LOCAL server-side chart rendering (ECharts SVG SSR +
+  // @resvg/resvg-js PNG). Tier ① (API-only/local) → UNGATED. Opt-in. Backed by
+  // chartRenderSkill.
+  CHART_RENDER: 'chart-render',
+  // `social-card` — LOCAL server-side branded "concept card" renderer
+  // (hand-authored SVG → PNG). Tier ① → UNGATED. Opt-in. Backed by
+  // socialCardSkill; pairs with the linkedin skill (returns a PNG `path`).
+  SOCIAL_CARD: 'social-card',
+  // `code-scan` — AGENT-DRIVEN, stack-smart deterministic linter over a
+  // checked-out repo (JS/TS→oxlint, …). Tier ① (fully local) → UNGATED. Opt-in.
+  // No-connection TOGGLEABLE (default ON). Backed by codeScanSkill.
+  CODE_SCAN: 'code-scan',
+  // `codebase-memory` — code-graph + semantic index over the checked-out repo,
+  // backed by the codebase-memory-mcp binary BAKED INTO the agent image. Fully
+  // local → UNGATED. No-connection TOGGLEABLE (default ON). Opt-in. Backed by
+  // codebaseMemorySkill.
+  CODEBASE_MEMORY: 'codebase-memory',
+  WORKFLOW_BUILDER: 'workflow-builder',
+  // `trigger-agent` — the agent-callable `trigger_agent` MCP tool
+  // (triggerAgentSkill): fire another Zibby workflow/agent run in this project
+  // (fire-and-forget, returns the executionId). Declares no requiresIntegration.
+  TRIGGER_AGENT: 'trigger-agent',
+  // `circleci` — INTEGRATION-GATE MARKER, not a runtime MCP skill: no skill
+  // registers under this id. Declaring it gates deploy on a connected CircleCI
+  // (the flaky-test-fixer pattern).
+  CIRCLECI: 'circleci',
+  // LLM-provider admin/billing skills (paste-token integrations). See
+  // @zibby/skills' llm-billing.js + backend/src/handlers/llm-billing.js.
+  OPENAI_BILLING: 'openai_billing',
+  ANTHROPIC_BILLING: 'anthropic_billing',
+  CURSOR_ADMIN: 'cursor_admin',
+  // `session` — opt-in conversation continuity for Claude-backed nodes. The
+  // skill is registered separately via `registerSkill(sessionSkill())` (from
+  // @zibby/core) and wired declaratively through `.zibby.config.mjs` `skills:`.
+  // Kept in the id map so `SKILLS.SESSION` resolves in any consumer.
+  SESSION: 'session',
+});
+
+/**
+ * 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.
+ */
+export const SKILL_META = Object.freeze({});