From bcb0c3fb0034de72de83d16e21a61a470c897865 Mon Sep 17 00:00:00 2001 From: HiranoMasaaki Date: Wed, 4 Mar 2026 17:16:23 +0000 Subject: [PATCH] fix: add delegate expert key example with @ prefix to definition-writer schema reference The definition-writer LLM was generating delegate expert keys without the @ prefix (e.g., "aigaming/gamedesigner" instead of "@aigaming/gamedesigner") because the schema reference only showed coordinator examples. Added a concrete delegate TOML example and clarified the TOML syntax rules to explicitly require the @ prefix for delegate keys. Co-Authored-By: Claude Opus 4.6 --- definitions/create-expert/perstack.toml | 24 +++++++++++++++++++----- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/definitions/create-expert/perstack.toml b/definitions/create-expert/perstack.toml index 23c49b0c..536dc98e 100644 --- a/definitions/create-expert/perstack.toml +++ b/definitions/create-expert/perstack.toml @@ -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. @@ -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. @@ -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" @@ -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 @@ -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