Agent skill
designing-syntax
Design custom syntax elements with reuse-first approach for workflow orchestration. Use when user needs custom operators, checkpoints, or syntax patterns not available in core syntax.
Install this agent skill to your Project
npx add-skill https://github.com/Sixallfaces/orkestr/tree/main/skills/designing-syntax
SKILL.md
Designing Custom Workflow Syntax
I design custom syntax elements following a reuse-first approach. Only create new syntax when existing patterns don't fit.
When I Activate
I activate when you:
- Need custom workflow operators
- Want specialized checkpoints
- Ask about extending syntax
- Need domain-specific patterns
- Say "I need a custom syntax for..."
Reuse-First Process
Before creating new syntax, I check:
- Built-in syntax -
->,||,~>,@,[...] - Global syntax library -
library/syntax/ - Template definitions - Existing workflow definitions
- Similar patterns - Adaptable existing syntax
Only create new if no match exists.
Syntax Types
Operators
Custom flow control operators.
Example: => (merge with dedup)
---
symbol: =>
description: Merge with deduplication
---
Executes left then right, removes duplicates from combined output.
Actions
Reusable sub-workflows.
Example: @deep-review
---
name: @deep-review
type: action
---
Expansion: [code-reviewer:"security" || code-reviewer:"style"] -> merge
Checkpoints
Manual approval gates with prompts.
Example: @security-gate
---
name: @security-gate
type: checkpoint
---
Prompt: Review security findings. Verify no critical vulnerabilities.
Conditions
Custom conditional logic.
Example: if security-critical
---
name: if security-critical
description: Check if changes affect security code
evaluation: Modified files in: auth/, crypto/, permissions/
---
Loops
Reusable loop patterns.
Example: retry-with-backoff(n)
---
name: retry-with-backoff
type: loop
params: [attempts]
---
Pattern: @try -> operation -> (if failed)~> wait -> @try
Design Principles
- Intuitive - Names/symbols hint at behavior
- Composable - Works with existing syntax
- Self-documenting - Clear from context
- Minimal - Only when truly needed
Best Practices
✅ DO:
- Use descriptive names (
@security-gatenot@check) - Document behavior clearly
- Provide examples
- Keep composable
❌ DON'T:
- Create for one-time use
- Make too specific
- Hide too much complexity
- Duplicate existing syntax
Library Structure
library/syntax/
├── operators/ # Flow control operators
├── actions/ # Reusable sub-workflows
├── checkpoints/ # Approval gates
├── conditions/ # Custom conditionals
├── loops/ # Loop patterns
├── aggregators/ # Result combination
└── guards/ # Pre-execution checks
Related Skills
- creating-workflows: Use custom syntax in workflows
- executing-workflows: Execute workflows with custom syntax
Need custom syntax? Describe the pattern you keep repeating!
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
managing-temp-scripts
Create and execute temporary scripts (Python, Node.js, shell) during workflow execution for API integrations, data processing, and custom tools. Use when user needs to interact with external APIs, process data with specific libraries, or create temporary executable code.
creating-workflows-from-description
Use when user describes complex multi-step tasks that could benefit from orchestration - guides natural language workflow creation
orchestration:creating-workflows
Use when user says "create workflow", "create a workflow", "design workflow", "orchestrate", "automate multiple steps", "coordinate agents", "multi-agent workflow". Creates orchestration workflows from natural language using Socratic questioning to plan multi-agent workflows with visualization.
managing-agents
Manages temporary and defined agents including creation, promotion, cleanup, and namespacing. Use when user creates custom agents, asks about agent lifecycle, temp agents, or agent management.
debugging-workflows
Debug workflow execution issues including syntax errors, agent failures, variable problems, and execution errors. Use when workflows fail, produce unexpected results, or user asks for debugging help.
orchestration:executing-workflows
Use when user provides workflow syntax with arrows (-> || ~>), says "run workflow", "execute workflow", "run this", mentions step1 -> step2 patterns. Executes orchestration workflows with real-time visualization, steering, and error recovery.
Didn't find tool you were looking for?