This is a guide to configuring several types of patterns that Skills may be configured to support within Agents.
After Skills are developed and deployed with named inputs and outputs, you configure the skill pattern in Agent Composer.
In general the output of a Skill is mapped by the agent to provide the input for another Skill through the synapse. The Skill output names are used to orchestrate the pattern or flow through a Skill.
In this Skill pattern all the Skill outputs names may be the same or different. The three Skills are executed once each in sequence. A single output is generated by the Agent.
Two Skills without Routing
In this Skill pattern the Skills are executed simultaneously. The Skill outputs may have the same or different names. Each Skill produces a different output, so the Agent output generated is in the form of an array with both outputs returned.
Four Skills without Routing
In this pattern the Skill output names are all the same name, so there is no routing. Skills A, B, and C execute once and Skill D executes twice, producing two outputs in the form of an array with both outputs present.
Four Skills with Routing
In this pattern Skill A produces two outputs: left and right. Skills A, B, and D execute once each, and Skill C is NOT executed. Only one output is produced by this Agent.
Skills with Conditions
In this pattern, Skill A is executed if a condition is met. If Skill A is executed and a second condition is met, Skill B is executed. If Skill B is executed, then Skill C is executed, and the Agent produces a single output. If the conditions are not met then the Agent is COMPLETED with no output.
Many other Skill patterns are possible using Skill output names and mapping the flow through the Agent in Agent Composer.
This Agent uses the system-skill "Merge Skill" to combine the outputs of two Skills into a single results set. The "Merge Skill" comes loaded in Agent Composer.
The Skill pattern can be better understood by looking at the inputs an outputs of an example Agent.
The file below
agent.yaml is not a file type users typically interact with in Fabric. It is built and run under the covers.)