Feature Request: Support per-skill model selection through SKILL.md frontmatter

Abierto
  • ¿Algo no está bien?
#2,895 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java
Área
ai-infra-agents

Línea de trabajo

Start by finding SkillProviderDescriptor in the SDK and reading how the existing model field on custom agents is declared and passed through, then check how skills are loaded from SKILL.md frontmatter. The open question is whether the closed-source Copilot CLI runtime can honour a per-skill model, so the first step is a maintainer answer, not code. Done means the maintainers have agreed on an approach and a scope for the SDK-side change.

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

Descripción

Hi! I'd like to contribute support for specifying a model in a skill's SKILL.md frontmatter, similar to how custom agents support the model field.

For example:

---
name: architecture-review
description: Reviews application architecture.
model: claude-sonnet-4
---

My understanding is that this requires more than adding a model property to the SDK's SkillProviderDescriptor. The runtime must actually honour the declared model when executing the skill.

Since the Copilot CLI runtime is closed source, I'd like to clarify the intended implementation approach before proceeding.

Does the Copilot SDK already expose a mechanism that allows a skill to execute using a different model from the parent session, or would this require an internal change to the Copilot CLI runtime?

If it requires a runtime change, is there an extension point or contribution path available for external contributors to implement this?

I'd appreciate your guidance so I can work on the right part of the architecture.

Lenguaje dominante
Java
Estrellas
10.7k
Forks
1.5k
Sin PR fusionados en 30 d

Preparar el entorno

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 github/copilot-sdk

Todos los issues de github/copilot-sdk

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.