Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Proposal: Skills — workflow-level context for tool composition

Abierto
  • ¿Algo no está bien?
#161 10 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
javascript
Área
web-dev

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
Bikeshed
Estrellas
4.7k
Forks
328
Merge medio
2 d 15 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de webmachinelearning/webmcp

Todos los issues de webmachinelearning/webmcp

Issues similares

Más issues de Web Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.