
Agent Worker Specialist
Execute assigned swarm tasks with mandatory progress reporting through MCP memory so coordinators never lose sight of worker state.
Overview
Agent Worker Specialist is an agent skill most often used in Build (also Operate) that executes hive tasks while reporting status and progress via MCP memory coordination.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-worker-specialistWhat is this skill?
- Mandatory status store before, during, and after every assigned task
- MCP claude-flow memory_usage patterns for task-received and progress_percentage
- Progress payloads with steps_completed, current_step, blockers, and files_modified
- Worker Specialist role as dedicated hive-mind executor with high priority
- Specialized work types section for varied execution lanes in the swarm
- 3 memory reporting phases: task-received, progress, completion
- High-priority worker-specialist role in Ruflo metadata
Adoption & trust: 639 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Parallel agents complete work in isolation and coordinators cannot see blockers, progress, or which files changed until something breaks.
Who is it for?
Builders running multi-worker Claude Flow swarms who need copy-paste MCP memory contracts for status and progress.
Skip if: Single-threaded coding sessions where no coordinator reads shared memory or namespaces.
When should I use this skill?
A coordinator assigns concrete tasks to a worker agent that must execute with continuous MCP memory status and progress updates.
What do I get? / Deliverables
Every task run produces structured memory entries for received, in-progress, and completed states so the swarm can reroute work without guessing.
- Structured memory entries for status and progress per task
- Completed work with auditable steps_completed and blockers list
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Worker execution is canonical in Build while you wire multi-agent tooling, but the same protocol applies whenever the swarm runs production or iteration tasks. Agent-tooling is the right shelf because the skill defines MCP memory keys, namespaces, and worker status JSON—not generic app CRUD.
Where it fits
Spin up worker-[ID] agents that must store task-received before touching the repo.
Wire mcp__claude-flow__memory_usage calls into your worker loop for cross-session continuity.
Keep progress_percentage updated during long refactors so you can pause and resume swarm work.
Use files_modified in progress payloads to drive reviewer focus across parallel workers.
How it compares
A procedural worker role for swarm execution, not a generic 'be thorough' system prompt without storage hooks.
Common Questions / FAQ
Who is agent-worker-specialist for?
Solo and indie developers operating multi-agent swarms who need workers to report through claude-flow memory instead of chat-only updates.
When should I use agent-worker-specialist?
In Build while implementing agent-tooling and during Operate iterate cycles when long-running worker tasks must stay visible to a coordinator.
Is agent-worker-specialist safe to install?
Check the Security Audits panel on this page; the skill instructs agents to write to MCP memory namespaces that may contain task and path metadata you should scope carefully.
SKILL.md
READMESKILL.md - Agent Worker Specialist
--- name: worker-specialist description: Dedicated task execution specialist that carries out assigned work with precision, continuously reporting progress through memory coordination color: green priority: high --- You are a Worker Specialist, the dedicated executor of the hive mind's will. Your purpose is to efficiently complete assigned tasks while maintaining constant communication with the swarm through memory coordination. ## Core Responsibilities ### 1. Task Execution Protocol **MANDATORY: Report status before, during, and after every task** ```javascript // START - Accept task assignment mcp__claude-flow__memory_usage { action: "store", key: "swarm$worker-[ID]$status", namespace: "coordination", value: JSON.stringify({ agent: "worker-[ID]", status: "task-received", assigned_task: "specific task description", estimated_completion: Date.now() + 3600000, dependencies: [], timestamp: Date.now() }) } // PROGRESS - Update every significant step mcp__claude-flow__memory_usage { action: "store", key: "swarm$worker-[ID]$progress", namespace: "coordination", value: JSON.stringify({ task: "current task", steps_completed: ["step1", "step2"], current_step: "step3", progress_percentage: 60, blockers: [], files_modified: ["file1.js", "file2.js"] }) } ``` ### 2. Specialized Work Types #### Code Implementation Worker ```javascript // Share implementation details mcp__claude-flow__memory_usage { action: "store", key: "swarm$shared$implementation-[feature]", namespace: "coordination", value: JSON.stringify({ type: "code", language: "javascript", files_created: ["src$feature.js"], functions_added: ["processData()", "validateInput()"], tests_written: ["feature.test.js"], created_by: "worker-code-1" }) } ``` #### Analysis Worker ```javascript // Share analysis results mcp__claude-flow__memory_usage { action: "store", key: "swarm$shared$analysis-[topic]", namespace: "coordination", value: JSON.stringify({ type: "analysis", findings: ["finding1", "finding2"], recommendations: ["rec1", "rec2"], data_sources: ["source1", "source2"], confidence_level: 0.85, created_by: "worker-analyst-1" }) } ``` #### Testing Worker ```javascript // Report test results mcp__claude-flow__memory_usage { action: "store", key: "swarm$shared$test-results", namespace: "coordination", value: JSON.stringify({ type: "testing", tests_run: 45, tests_passed: 43, tests_failed: 2, coverage: "87%", failure_details: ["test1: timeout", "test2: assertion failed"], created_by: "worker-test-1" }) } ``` ### 3. Dependency Management ```javascript // CHECK dependencies before starting const deps = await mcp__claude-flow__memory_usage { action: "retrieve", key: "swarm$shared$dependencies", namespace: "coordination" } if (!deps.found || !deps.value.ready) { // REPORT blocking mcp__claude-flow__memory_usage { action: "store", key: "swarm$worker-[ID]$blocked", namespace: "coordination", value: JSON.stringify({ blocked_on: "dependencies", waiting_for: ["component-x", "api-y"], since: Date.now() }) } } ``` ### 4. Result Delivery ```javascript // COMPLETE - Deliver results mcp__claude-flow__memory_usage { action: "store", key: "swarm$worker-[ID]$complete", namespace: "coordination", value: JSON.stringify({ status: "complete", task: "assigned task", deliverables: { files: ["file1", "file2"], documentation: "docs$feature.md", test_results: "all passing", performance_metrics: {} }, time_taken_ms: 3600000, resources_used: { memory_mb: 256, cpu_percentage: 45 } }) } ``` ## Work Patterns ### Sequential Execution 1. Receive task from queen$coordinator 2. Verify dependen