Agent skill · Audited from source
create-workflow-command
skill · neolabhq/context-engineering-kitGPL-3.0 licenceAudited 13 Nov 2026 · source c64c9eb3b29e
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit c64c9eb3b29e and found no filesystem, network or shell access and no hard-coded secrets. What it does: Create a workflow command that orchestrates multi-step execution through sub-agents with file-based task prompts
Cite
Cite this page
ModelsAtlas. “create-workflow-command (neolabhq/context-engineering-kit)”. Retrieved 13 Nov 2026. https://modelsatlas.com/skills/neolabhq/create-workflow-command
Trust audit
Audit 0.4.1 · source read 13 Nov 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha c64c9eb3b29e · 13 Nov 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherneolabhq GitHub organizationOwner of the repository this skill is read from
- Source folderneolabhq/context-engineering-kit/skills/create-workflow-commandThe exact folder we audited
- LicenceGPL-3.0As the repository states it
- Commit pinned for this verdictc64c9eb3b29eA new audit runs when the source changes
- Repository statusNot archivedLast push 78 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Create a workflow command that orchestrates multi-step execution through sub-agents with file-based task prompts
---
name: create-workflow-command
description: Create a workflow command that orchestrates multi-step execution through sub-agents with file-based task prompts
---
# Create Workflow Command
Create a command that orchestrates multi-step workflows by dispatching sub-agents with task-specific instructions stored in separate files.
## User Input
```text
Workflow Name: $1
Description: $2
```
## Architecture Overview
Workflow commands solve the **context bloat problem**: instead of embedding detailed step instructions in the main command (polluting orchestrator context), store them in separate task files that sub-agents read on-demand.
```
plugins/<plugin-name>/
├── commands/
│ └── <workflow>.md # Lean orchestrator (~50-100 tokens per step)
├── agents/ # Optional: reusable executor agents
│ └── step-executor.md # Custom agent with specific tools/behavior
└── tasks/ # All task instructions directly here
├── step-1-<name>.md # Full instructions (~500+ tokens each)
├── step-2-<name>.md
├── step-3-<name>.md
└── common-context.md # Shared context across workflows
```
## Key Principles
### 1. Context Isolation
Each sub-agent gets its own isolated context window. The main orchestrator stays lean while sub-agents load detailed instructions from files.
| Component | Context Cost | Purpose |
|-----------|--------------|---------|
| Orchestrator command | ~50-100 tokens/step | Dispatch and coordinate |
| Task file | ~500+ tokens | Detailed step instructions |
| Sub-agent base | ~294 tokens | System prompt overhead |
### 2. Sub-Agent Capabilities
Sub-agents spawned via Task tool:
| Capability | Available | Notes |
|------------|-----------|-------|
| Read tool | ✅ Yes | Can read any file |
| Write tool | ✅ Yes | If not restricted |
| Grep/Glob | ✅ Yes | For code search |
| Skills loading | ❌ No | Skills don't auto-load in sub-agents |
| Spawn sub-agents | ❌ No | Cannot nest Task tool |
| Resume context | ✅ Yes | Via `resume` parameter |
### 3. File Reference Pattern
Use `${CLAUDE_PLUGIN_ROOT}` for portable paths within plugin:
```markdown
Read ${CLAUDE_PLUGIN_ROOT}/tasks/step-1-workflow-name.md and execute.
```
Sub-agent will use Read tool to fetch the file content.
## Implementation Process
### Step 1: Gather Requirements
Ask user (if not provided):
1. **Workflow name**: kebab-case identifier (e.g., `feature-implementation`)
2. **Description**: What the workflow accomplishes
3. **Steps**: List of discrete steps with:
- Step name
- Step goal
- Required tools
- Expected output
4. **Execution mode**: Sequential or parallel steps
5. **Agent type**: `general-purpose` or custom agent
### Step 2: Create Directory Structure
```bash
# Create tasks directory (if it doesn't exist)
mkdir -p ${CLAUDE_PLUGIN_ROOT}/tasks
# Optional: Create agents directory (if using custom agents)
mkdir -p ${CLAUDE_PLUGIN_ROOT}/agents
```
**Note**: All task files (both workflow-specific steps and shared context) are placed directly in `tasks/` without subdirectories.
### Step 3: Create Task Files
For each step, create a task file with this structure:
```markdown
# Step N: <Step Name>
## Context
You are executing step N of the <workflow-name> workflow.
## Goal
<Clear, specific goal for this step>
## Input
<What this step receives from previous steps or user>
## Instructions
1. <Specific action>
2. <Specific action>
3. <Specific action>
## Constraints
- <Limitation or boundary>
- <What NOT to do>
## Expected Output
<What to return to orchestrator>
## Success Criteria
- [ ] <Measurable outcome>
- [ ] <Measurable outcome>
```
### Step 4: Create Orchestrator Command
Create the main command file with this pattern:
```markdown
---
description: <Workflow description>
argument-hint: <Required arguments>
allowed-tools: Task, Read
model: sonnet
---
# <Workflow Name>
## User Input
\`\`\`text
$ARGUMENTS
\`\`\`
## Workflow Execution
### Step 1: <Step Name>
Launch general-purpose agent:
- **Description**: "<3-5 word summary>"
- **Prompt**:
\`\`\`
Read ${CLAUDE_PLUGIN_ROOT}/tasks/step-1-<workflow>-<name>.md and execute.
Context:
- TARGET: $1
- MODE: $2
\`\`\`
**Capture**: <What to extract from result>
### Step 2: <Step Name>
Launch general-purpose agent:
- **Description**: "<3-5 word summary>"
- **Prompt**:
\`\`\`
Read ${CLAUDE_PLUGIN_ROOT}/tasks/step-2-<workflow>-<name>.md and execute.
Context from Step 1:
- <Key data from previous step>
\`\`\`
### Step 3: <Step Name>
[Continue pattern...]
## Completion
Summarize workflow results:
1. <What was accomplished>
2. <Key outputs>
3. <Next steps if any>
```
#### Frontmatter Options
| Field | Purpose | Default |
|-------|---------|---------|
| `description` | Brief description of workflow purpose | Required |
| `argument-hint` | Expected arguments description | None |
| `allowed-tools` | Tools the command can use | Inherits from conversation |
| `model` | Specific Claude model (sonnet, opus, haiku) | Inherits from conversation |
**Model selection**:
- `haiku` - Fast, efficient for simple workflows
- `sonnet` - Balanced performance (recommended default)
- `opus` - Maximum capability for complex orchestration
## Execution Patterns
### Pattern A: Sequential Steps (Default)
Each step depends on previous step's output:
```markdown
### Step 1: Analyze
Launch agent → Get analysis result
### Step 2: Plan (uses Step 1 result)
Launch agent with Step 1 context → Get plan
### Step 3: Execute (uses Step 2 result)
Launch agent with Step 2 context → Complete
```
### Pattern B: Parallel Independent Steps
Steps can run concurrently:
```markdown
### Analysis Phase (Parallel)
Launch 3 agents simultaneously:
1. Agent 1: Security analysis → Read ${CLAUDE_PLUGIN_ROOT}/tasks/step-1a-security.md
2. Agent 2: Performance analysis → Read ${CLAUDE_PLUGIN_ROOT}/tasks/step-1b-performance.md
3. Agent 3: Code quality analysis → Read ${CLAUDE_PLUGIN_ROOT}/Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit c64c9eb
git clone https://github.com/neolabhq/context-engineering-kit git -C context-engineering-kit checkout c64c9eb3b29e
The author documents no install command, so this uses the repository directly. Our verdict covers commit c64c9eb3b29e only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
c64c9eb3b29e
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/neolabhq/create-workflow-command/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All automation skills →neolabhq/context-engineering-kit
Comprehensive multi-perspective review using specialized judges with debate and consensus building
neolabhq/context-engineering-kit
Guide for creating effective skills. This command should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool…
neolabhq/context-engineering-kit
Create pull requests using GitHub CLI with proper templates and formatting
neolabhq/context-engineering-kit
Use when found gap or repetative issue, that produced by you or implemenataion agent. Esentially use it each time when you say "You absolutly right, I should have done it differently." -> need create rule for this issue…
neolabhq/context-engineering-kit
Create and configure git hooks with intelligent project analysis, suggestions, and automated testing
neolabhq/context-engineering-kit
Generate ideas in one shot using creative sampling
Add this badge to your README
[](https://modelsatlas.com/skills/neolabhq/create-workflow-command/)
<a href="https://modelsatlas.com/skills/neolabhq/create-workflow-command/"><img src="https://modelsatlas.com/skills/neolabhq/create-workflow-command/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about create-workflow-command
What does the create-workflow-command skill do?
Is create-workflow-command safe to install?
What can create-workflow-command access on my machine?
How current is this page?
Sources
- github.com/neolabhq/context-engineering-kit/tree/master/skills/c — the audited source at commit c64c9eb3b29e and every finding aboveObserved · 13 Nov 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the create-workflow-command skill do?
- Is create-workflow-command safe to install?
- What can create-workflow-command access on my machine?