Skip to content
ConduitConduit

Skill Packs

A skill pack is a bundle of Agent Skills — SKILL.md files that give Claude (or any Conduit-connected AI client) step-by-step instructions for a specific kind of work. Once a pack is enabled for a member, their AI client can discover and pull those instructions mid-conversation through Conduit’s MCP gateway, the same way it reaches your connected vendor tools.

The Skill Packs page

Section titled “The Skill Packs page”

Admins manage skill packs from /org/skills, in two tabs:

  • Catalog — global packs WYRE curates and keeps in sync from a public marketplace. Filterable by category, with the same card layout as /org/catalog.
  • Custom — packs your org has imported from your own GitHub repos. Each card shows a severity badge (🟢/🟡/🔴) from the security scan, an “N of M skills enabled” count, and a Review skills action that opens a drawer listing every individual skill, its grade, and what it’s flagged for.

Importing your own

Section titled “Importing your own”

Click + Import from GitHub on the Skill Packs page, then either paste a public GitHub repository (or subdirectory) URL, or drag a .zip file onto the same dialog (or click to browse for one). Both paths go through the identical scan/review pipeline — Conduit fetches or unpacks the skills, scans every one inside, and stores them disabled by default regardless of grade: nothing in an imported pack is usable until an admin reviews it. Enabling a skill the scanner flagged 🔴 requires the org owner and an explicit override.

Importing via MCP

Section titled “Importing via MCP”

Owners and admins can also import a pack without leaving their AI client, using the conduit__import_skill MCP tool — pass it a GitHub repo (or subdirectory) URL and it runs through the exact same scan/store pipeline as the web importer, landing disabled by default the same way.

To let a specific member import skills this way without making them a full org admin, use the Skill-authoring access panel at the bottom of the Custom tab: toggle Allow for everyone, or grant individual members. This grants only the ability to import a pack via MCP — reviewing and enabling what gets imported still goes through the same admin-gated flow as any Custom pack.

Governing who can use a pack

Section titled “Governing who can use a pack”

Each pack has an Edit access button on its Catalog-tab card, using the same member > team > all-members, most-specific-wins model as vendor access grants — see Managing Access for how that precedence resolves. Two differences from vendor access:

  • Skill access is all-or-nothing per pack (plus an optional list of specific skills within it), not a graded Read/Write/Delete/Admin tier — skills are read-only instructions, so there’s no write level to grant.
  • Catalog packs with no grants at all default to allowed for everyone. If a vendor-linked catalog pack has no explicit grant, a member who already has access to that vendor gets the pack too. Only when neither applies does a catalog pack fall back to open-for-everyone. Custom (org-imported) packs never default open — with no grant, they’re inaccessible until an admin grants access, keeping every import admin-reviewed.

An explicit grant at the most specific applicable level — including an explicit deny — always wins over these defaults.

Where skills show up

Section titled “Where skills show up”

There’s no separate member-facing skills page. A member’s AI client sees available skills automatically through Conduit’s MCP gateway, filtered live by the same access rules the admin page displays — what an admin sees as accessible is exactly what gets served.

How clients discover skills (SEP-2640)

Section titled “How clients discover skills (SEP-2640)”

Conduit serves skills per the MCP Skills Extension SEP, declaring io.modelcontextprotocol/skills in its initialize capabilities. A conforming client can call:

  • skills/list — paginated entries for every skill the caller can access, each with its verbatim frontmatter and a complete resources manifest ({uri, digest} for SKILL.md and every supporting file).
  • skills/get — the same entry for one skill by its skill://{pack}/{skill}/SKILL.md URI, listed or not.
  • resources/read — the content of any of those URIs, including a skill’s supporting reference files (e.g. skill://{pack}/{skill}/FIELDS.md) served as sibling resources.
  • resources/directory/read — the file listing of a skill’s root directory.

Clients that predate the extension still work: skills also appear in plain resources/list, and the conduit__list_skills / conduit__get_skill tools remain available as a compatibility bridge.

Keeping the catalog current

Section titled “Keeping the catalog current”

The global Catalog tab syncs weekly from WYRE’s plugin marketplace. The sync only adds or updates the shared catalog — it never grants a pack to any org; the access rules above still decide who can use a newly-synced pack.

Section titled “Related”