Undocumented `skill:` frontmatter field in commands - does command-to-skill delegation exist?

Resolved 💬 4 comments Opened Feb 22, 2026 by nathanvale Closed Mar 22, 2026

Summary

Several community examples and skill templates use a skill: frontmatter field in command files (.claude/commands/*.md) to delegate execution to a named skill. This field is not documented and does not appear in the official frontmatter field list.

Example

# .claude/commands/dojo.md
---
description: Query the Agentic Dojo for pattern knowledge
argument-hint: "e.g. 'explain wave computation'"
model: sonnet
skill: agentic-dojo
---

$ARGUMENTS

The assumption is that skill: agentic-dojo would delegate execution to .claude/skills/agentic-dojo/SKILL.md.

Questions

  1. Does skill: exist as a frontmatter field? It's not in the documented list (name, description, argument-hint, disable-model-invocation, user-invocable, allowed-tools, model, context, agent, hooks).
  1. Is command-to-skill delegation a supported pattern? The docs state "Custom slash commands have been merged into skills" -- meaning a command file IS a skill. If there's no delegation mechanism, the correct approach is to put all logic directly in the SKILL.md and use name: to control the slash command name.
  1. If skill: is not supported, what's the recommended pattern for a thin wrapper that invokes a richer skill? Current workaround: just use the skill directly with name: dojo in SKILL.md frontmatter to get /dojo.

Documented Frontmatter Fields

From https://code.claude.com/docs/en/skills:

  • name, description, argument-hint, disable-model-invocation, user-invocable, allowed-tools, model, context, agent, hooks

skill: is not in this list.

Environment

  • Claude Code CLI
  • macOS Tahoe 26.2
  • 2026-02-22

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗