@axiom-lattice/core 2.1.83 → 2.1.84

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -22036,7 +22036,7 @@ You have nine tools for agent management:
22036
22036
  - **list_tools** \u2014 See all available tools that can be assigned to agents
22037
22037
  - **get_agent** \u2014 View the full configuration of a specific agent
22038
22038
  - **create_agent** \u2014 Create a REACT or DEEP_AGENT agent
22039
- - **create_workflow** \u2014 Create a WORKFLOW agent from a concise DSL (load create-workflow skill first)
22039
+ - **create_workflow** \u2014 Create a WORKFLOW agent from a concise DSL (load create-workflow skill + task-relevant domain skills first)
22040
22040
  - **validate_workflow** \u2014 Validate a workflow agent's DSL
22041
22041
  - **update_workflow** \u2014 Update a workflow agent's DSL or config
22042
22042
  - **update_agent** \u2014 Modify an existing REACT or DEEP_AGENT agent's configuration
@@ -22133,14 +22133,23 @@ Use this when the process is fully known. A workflow is a deterministic LangGrap
22133
22133
  | needs + if model (YAML DSL) | Single orchestrator delegates linearly |
22134
22134
  | No LLM routing decisions | Orchestrator uses LLM to route |
22135
22135
 
22136
- ### Phase 0: Load the Skill
22136
+ ### Phase 0: Load Skills
22137
22137
 
22138
- **BEFORE designing, you MUST load the create-workflow skill:**
22138
+ **BEFORE designing, you MUST load relevant skills:**
22139
+
22140
+ 1. **Always load** the \`create-workflow\` skill \u2014 it teaches the YAML DSL syntax, step format, and design patterns:
22139
22141
 
22140
22142
  \`\`\`
22141
22143
  skill(skill_name: "create-workflow")
22142
22144
  \`\`\`
22143
22145
 
22146
+ 2. **Determine and load task-relevant domain skills** \u2014 do NOT skip this step:
22147
+ a) **First, scan** the \`<available_skills>\` section above. For each skill, read its name and description to determine if it relates to the user's task domain (e.g., financial analysis, sales, data processing, reporting)
22148
+ b) **Then, load each relevant skill** by calling \`skill(skill_name: "<skill-name>")\` \u2014 call this once per relevant skill, NOT in a batch
22149
+ c) Read the loaded skill content for domain-specific workflow patterns, reusable sub-workflows, and DSL best practices
22150
+
22151
+ **If you skip step 2, you will miss critical domain knowledge and produce a suboptimal design.**
22152
+
22144
22153
  ### Phase 1: Design
22145
22154
 
22146
22155
  1. **Analyze the process.** Map every step, branch, data dependency.
@@ -22255,7 +22264,7 @@ All fields except name, type, and prompt are optional.
22255
22264
 
22256
22265
  ### create_workflow (WORKFLOW)
22257
22266
 
22258
- Creates a WORKFLOW agent from a YAML linear DSL. Before calling, load the \`create-workflow\` skill. Must pass \`skillLoaded: true\`.
22267
+ Creates a WORKFLOW agent from a YAML linear DSL. Before calling, load the \`create-workflow\` skill plus any task-relevant domain skills. Must pass \`skillLoaded: true\`.
22259
22268
 
22260
22269
  \`\`\`typescript
22261
22270
  {
@@ -22570,6 +22579,14 @@ var agentArchitectConfig = {
22570
22579
  ],
22571
22580
  internalSubAgents: [agentReviewerConfig],
22572
22581
  middleware: [
22582
+ {
22583
+ id: "filesystem",
22584
+ type: "filesystem",
22585
+ name: "Filesystem",
22586
+ description: "Read, write, edit, list, search files",
22587
+ enabled: true,
22588
+ config: {}
22589
+ },
22573
22590
  {
22574
22591
  id: "skill",
22575
22592
  type: "skill",