[FEATURE] Programmatic org-skill deployment for support tier workflows via GitHub Actions

Resolved 💬 1 comment Opened Jun 25, 2026 by vfantauzzo Closed Jun 28, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Organization-level skills can only be uploaded through the admin UI, blocking CI-CD automation. Teams managing tiered support skills (L1, L2, L3) need to version-control skill definitions in Git, review changes via PR, and auto-deploy on merge without manual admin intervention.

Proposed Solution

Extend the /v1/skills API to support org-level skill CRUD with API key authentication. Include endpoints to create, update, list, and delete org skills, plus metadata for assigning skills to user groups or roles.

Alternative Solutions

Support skill assignment rules based on user group or SSO attributes so org skills auto-surface in Claude.ai for targeted tiers without requiring programmatic deployment.

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

Support team maintains L1, L2, L3 skills in a GitHub repo with Datadog, Atlassian, and documentation connectors scoped per tier. On PR merge to main, a GitHub Action deploys the updated skill to the org so all L1 engineers see their tier's skill immediately in Claude.ai without admin clicks. Marketing maintains brand voice skills; engineering maintains investigation methodologies.

Additional Context

The admin UI uses session cookie auth, unsuitable for headless CI-CD. Workspace-scoped /v1/skills API exists but doesn't surface in Claude.ai UI for end users. This blocks orgs from treating skills like versioned, governed infrastructure.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗