Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

add first-class support for skills extension in McpServer

Aperta
  • Qualcosa non va?
#10,016 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@effect-bot ci sta già lavorando.

Dal 27/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement
What is the problem this feature would solve?

Effect MCP servers can publish tools, prompts, and resources, but authors have no dedicated API for publishing Agent Skills. Registering a SKILL.md resource alone does not provide skill discovery, metadata lookup, or a complete file manifest.

Mcp spec already has an extension for this: SEP-2640 which is Final. Implementation should target the maintained Skills extension specification.

What is the feature you are proposing to solve the problem?

Add a skill definition and registration API alongside McpServer.resource. Skills would have dedicated discovery through skills/list and skills/get, while their instructions and supporting files continue to use resources/read.

The API should derive frontmatter, file sizes, and SHA-256 digests from the same immutable content served to clients. Server authors should not need to calculate manifests or register discovery handlers themselves.

Proposed API:

const RefundsSkill = McpServer.skill({
  uri: "skill://billing/refunds/SKILL.md",
  frontmatter: {
    name: "refunds",
    description: "Process refunds using the billing tools"
  },
  instructions: String.stripMargin(`
      |Read references/policy.md before issuing a refund.
      |Use the billing tools to inspect the payment and submit the refund.
    `),
  files: {
    "references/policy.md": {
      mimeType: "text/markdown",
      content: "Refunds above CHF 500 require manager approval.\n"
    }
  }
})

const McpLive = Layer.mergeAll(
  RefundsSkill,
  // PolicyResource
).pipe(
  Layer.provide(
    McpServer.layerHttp({
      name: "billing",
      version: "1.0.0",
      path: "/mcp",
      protocols: [McpProtocol.v2026_07_28]
    })
  )
)

McpServer.skill would return a composable registration Layer, suitable for combining with existing tool, prompt, and resource registrations. There can then be sensible fallbacks to use this as a resource when capability of the client is missing or the protocol version is mismatched for extensions

What alternatives have you considered?

with a lot of the extensions (like Task) there are new rpc routes to handle so the only other way would be to allow some sort of hook into what routes can be defined so the author of the server can define the extension spec themselves.

This build on learnings and experiments from #8631

Lingua principale
TypeScript
Stelle
16.7k
Fork
808
Merge medio
10h 49m
PR unite (30g)
846

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Effect-TS/effect

Tutte le issue di Effect-TS/effect

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.