Skip to content

fix: add delegate key @ prefix example to create-expert definition-writer #704

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
FL4TLiN3 merged 1 commit into from
Mar 4, 2026
Merged

fix: add delegate key @ prefix example to create-expert definition-writer #704

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 19 additions & 5 deletions definitions/create-expert/perstack.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ providerName = "anthropic"

[experts."create-expert"]
defaultModelTier = "high"
version = "1.0.3"
version = "1.0.4"
description = "Creates and modifies Perstack expert definitions in perstack.toml"
instruction = """
You are the coordinator for creating Perstack expert definitions.
Expand Down Expand Up @@ -201,7 +201,7 @@ pick = ["searchMcpRegistry", "getMcpServerDetail"]

[experts."@create-expert/definition-writer"]
defaultModelTier = "low"
version = "1.0.0"
version = "1.0.1"
description = """
Writes Perstack expert definitions in perstack.toml from a design plan. Provide: path to the plan file (e.g. plan.md). \
Optionally include: (1) feedback from a previous test round to address, (2) path to skill-report.md with MCP registry findings.
Expand All @@ -220,7 +220,7 @@ model = "claude-sonnet-4-5"
providerName = "anthropic" # or "openai", "google", etc.
envPath = [".env"]

# Expert definition
# Coordinator expert definition
[experts."expert-name"]
version = "1.0.0"
description = "Brief description of what this expert does"
Expand All @@ -240,6 +240,20 @@ pick = ["tool1", "tool2"] # optional, include specific tools
# omit = ["tool3"] # optional, mutually exclusive with pick
# requiredEnv = ["ENV_VAR"] # optional, required environment variables
# rule = "Usage instructions" # optional, guidance for using this skill

# Delegate expert definition — key MUST start with @ and use the format @coordinator/delegate-name
[experts."@expert-name/delegate"]
version = "1.0.0"
description = "Brief description of what this delegate does"
instruction = \"\"\"
Domain knowledge and guidelines for the delegate.
\"\"\"

[experts."@expert-name/delegate".skills."@perstack/base"]
type = "mcpStdioSkill"
command = "npx"
packageName = "@perstack/base"
pick = ["tool1", "tool2"]
```

## Instruction Writing Guidelines
Expand All @@ -262,8 +276,8 @@ pick = ["tool1", "tool2"] # optional, include specific tools
## TOML Syntax Rules

- Use triple-quoted strings for multi-line instructions
- Expert keys: kebab-case (my-expert-name)
- Delegate keys: @coordinator/delegate-name
- Coordinator expert keys: kebab-case (my-expert-name), used in [experts."my-expert-name"]
- Delegate expert keys: MUST start with @ — format is @coordinator/delegate-name, used in [experts."@coordinator/delegate-name"]. Never omit the @ prefix.
- The @perstack/base skill key MUST be exactly `"@perstack/base"` — never `"base"` or other aliases. The runtime looks up this exact key. Other skill keys can be any name.
- Always include version, description, instruction for each expert
- Produce valid TOML — no syntax errors
Expand Down