Skip to content

Clarify whether nested skills are allowed #137

@PaulRBerg

Description

@PaulRBerg

Problem

The current docs and spec don't clarify whether a skill can reference and invoke other skills by name. For example, can a skill's prompt tell the agent to "run the /foo skill" as part of its workflow?

It's unclear if:

  • A skill can instruct the agent to execute another skill by name (e.g., "now run the code-review skill")
  • There are any conventions for skill-to-skill delegation or chaining
  • The agent is expected to resolve skill references within a skill's prompt and invoke them via the Skill tool

Related: #95

Solution

Add a section to the docs that explicitly addresses:

  1. Whether skills can reference other skills by name and instruct the agent to invoke them
  2. If supported, the recommended syntax or convention for cross-skill references
  3. Any limitations or caveats (e.g., circular references, execution order, context sharing between chained skills)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions