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

Proposal: Skills — workflow-level context for tool composition

Aperta
  • Qualcosa non va?
#161 10 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
javascript
Ambito
web-dev

Direzione di ricerca

Start with the proposal’s registerSkill() strawman API and the existing registerTool() and provideContext() behavior. There are unresolved API and semantics questions, so the first task is to identify the relevant specification section or proposal entry point and determine the intended scope; completion requires an agreed API and normative documentation, which this issue does not yet identify.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

backlog enhancement

Proposal to let pages register skills — bundling tools with structured context and workflow guidance — so agents can use a site competently, not just functionally.

Tools can tell agents what a site can do, but Skills tell agents how to do it well.

A skill bundles registered tools with structured context and optional guidance, so agents can operate competently within a domain rather than calling functions blind.

Strawman API

navigator.modelContext.registerSkill({
  name: "personal_shopper",
  description: "Shopping assistant guidance for this store",
  instructions: `
    1. Ask about occasion and budget before searching
    2. Our sizing runs small — suggest one size up
    3. For orders over $100, mention current promotion
    4. Always mention 30-day return policy before checkout
    5. Use requestUserInteraction() for payment confirmation
  `,
  tools: ["searchProducts", "showProducts", "addToCart", "applyPromoCode"],
  context: {
    currentPromotion: { code: "SPRING30", minOrder: 100, discount: "30%" },
    returnPolicy: "30-day free returns, free first exchange",
    sizingNote: "Sizes run ~1 size small vs. US standard"
  },
  annotations: { category: "commerce", version: "1.0" }
});

Tools are still registered independently via registerTool(). A skill references them by name and adds the layer of how and when to use them.

instructions is an optional hint — clients that don't interpret natural language (accessibility tools, OS assistants) can ignore it and still use the tools and structured context directly.

Problem

An e-commerce site registers searchProducts, addToCart, and applyPromoCode. An agent can call them. But it doesn't know the store's sizing runs small, there's an active promo code, it should ask about occasion before searching, or which products pair well together.

Tool descriptions can't carry this weight — they document individual functions, not workflows. The gap grows with domain complexity: travel sites need fare class knowledge, support portals need triage logic.

Design Considerations

  • Trust. Skills influence agent behavior. Safeguards: user-inspectable (like page source), domain-scoped (like tools), advisory (agents serve users first). Browsers could enforce content policies on instructions.
  • Discoverability. A .well-known/webmcp manifest could include skill declarations alongside tools.
  • Agnosticism. instructions is a hint for LLM-based agents. The structured context object and tools list are useful to any client. Non-LLM clients skip what they don't understand — same pattern as readOnlyHint.

Open Questions

  • New method (registerSkill) or extension to provideContext()?
  • Should instructions be plain text, structured steps, or both?
  • How should skills interact with the agent's own system-level constraints?

Prior Art

  • MCP prompts/resources — backend MCP's guidance and data primitives
  • MCP-B — already bridges WebMCP to full MCP including prompts and resources via npm packages
  • Claude Skills, Custom GPTs, LobeHub Skills — production patterns bundling instructions + tools + context
Lingua principale
Bikeshed
Stelle
4.7k
Fork
328
Merge medio
2g 15h
PR unite (30g)
16

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 webmachinelearning/webmcp

Tutte le issue di webmachinelearning/webmcp

Issue simili

Altre issue su Web Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.