-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Describe the feature or problem you'd like to solve
Every time I start Copilot CLI, I get 20+ "unknown field ignored" warnings from skills and commands in installed plugins. Most of these fields are either defined in the Agent Skills spec (like license) or widely used across the plugin ecosystem (like argument-hint in commands). The warnings are noisy and there's nothing I can do about them as a user — the fields come from published plugins.
Proposed solution
Unknown frontmatter fields in SKILL.md and command .md files should be silently ignored (or logged at --log-level debug only), not warned to the user on every startup. This is how VS Code Copilot Chat already handles them (see #951).
Specifically:
- Spec-defined fields like
license,metadata, andcompatibilityshould be recognized without warnings per the Agent Skills spec. (allowed-toolsis already handled correctly — nice work!) - Command frontmatter fields like
argument-hintandhide-from-slash-command-tool— used byclaude-plugins-officialitself — should be recognized. - Any other unknown field should be silently skipped for forward-compatibility as the spec and plugin ecosystem evolve.
This is related to #894 (license required when spec says optional) and #951 (metadata as last field breaks skill discovery).
Example prompts or workflows
-
Install
claude-plugins-officialandhashicorp-agent-skillsplugins. Startcopilot. Observe 20+ warning lines before the prompt appears —tools,version,license,mcpServersfrom skills andargument-hintfrom 15+ command files. -
A skill with
metadataas the last frontmatter field isn't discovered at all (Skills withmetadataas last frontmatter field are not discovered #951):--- name: my-skill description: A skill. metadata: author: me ---
-
A command using
argument-hint(from GitHub's ownclaude-plugins-official):--- description: Create a new SDK app argument-hint: [project-name] ---
Warns "unknown field ignored: argument-hint" on every startup.
-
Skills shared across Copilot CLI, Claude Code, and Gemini CLI use the Agent Skills spec as a common format. Harness-specific fields (e.g.
tools,mcpServers) from other tools shouldn't produce warnings in Copilot CLI. -
Plugin authors shouldn't need to maintain separate skill/command files per harness to avoid warnings.
Additional context
- Copilot CLI version: 0.0.414
- OS: Windows 11 (x86_64)
- Related issues: Skill validation requires 'license' in SKILL.md frontmatter (spec says optional) #894, Skills with
metadataas last frontmatter field are not discovered #951 - Plugins that trigger warnings:
claude-plugins-official(tools,version,license,argument-hint,hide-from-slash-command-tool),hashicorp-agent-skills(mcpServers),leefowlercu-agent-kit(argument-hintin 8+ commands) allowed-toolsin SKILL.md is now working correctly (observed viathrashr888-agent-kit) — only the command-level variant still warns