From every tool I've tested in this space, I haven't found one that delivers intelligence without complexity, a companion instead of a tool, visualization without needing to write code, or value without hype. In my professional experience, the best products are user journeys and the stories they tell. Skales has the foundation to tell that story. No one else in this landscape is close.
This proposal turns vision into value. Visually. Simply. Right now, agents, skills, tasks, memory, and schedules exist inside Skales but their relationships are invisible. Users configure them in isolation. This concept brings them into a single interactive canvas where every connection is visible, every status is live, and every component can be managed from one place.
The Local Swarm maps what's inside a single instance. The Network Swarm extends the same graph across connected peers, enabling shared skills, agent lending, and task delegation between machines. One workspace, two scopes.
Beyond the visual layer, this proposal outlines a phased roadmap toward MCP and A2A protocol alignment, agent observability, and real-time interaction. These are not theoretical. The infrastructure to support them already exists inside Skales.
This concept was designed and directed by @v33-kind, prototyped with AI assistance (Claude Code). It is not production code. It is a starting point.
A visual workspace on the Agent Swarm page. Interactive canvas for visualizing the agent ecosystem, not building workflows.
Node cards for each component (Agent Skill Task Memory Schedule), 4 connection ports per node, auto-routing bezier curves, click-to-highlight, drag-to-reposition, snap-to-grid, zoom, pan, stats bar, create modals.
| Strengths | Weaknesses |
|---|---|
|
1. Only local-first desktop app with agent viz + automatic peer discovery 2. agent-sync protocol already aligned with A2A task format 3. Skills have structured I/O, ready for MCP wrapping 4. Zero new dependencies required for MVP 5. Execution data already captured (logs, retries, timestamps) |
1. No real-time push (polling only at 15s intervals) 2. No drag-to-connect edge creation yet 3. Graph readability degrades past 50+ nodes 4. JSON file storage limits concurrent write performance 5. No built-in agent cost attribution |
| Opportunities | Threats |
|---|---|
|
1. MCP adoption accelerating (thousands of servers, adopted by OpenAI, Google, Anthropic) 2. A2A v1.0 under Linux Foundation enables cross-framework delegation (CrewAI, LangGraph, 150+ orgs) 3. Secure skill/agent sharing across network creates local ecosystem effects 4. Task delegation between instances enables distributed workloads 5. Companion-first positioning differentiates from tool-first competitors |
1. n8n (~181K stars) has native MCP (client + server nodes) 2. Dify (~135K stars) shipped bidirectional MCP in v1.6.0 3. CrewAI (~47K stars) has both MCP and A2A natively 4. MCP/A2A standards still maturing, risk of breaking changes 5. Cloud-first competitors have larger dev teams and faster release cycles |
With agent-sync already built, the same workspace enables:
| Type | Color | Data Source | Example |
|---|---|---|---|
| Agent | Indigo #6366f1 | agents/definitions/ | Code Assistant, Content Writer |
| Skill | Green #22c55e | skills.json | Web Search, Email, Vision |
| Task | Blue #3b82f6 | tasks/ | Write blog post, Review PR |
| Memory | Amber #f59e0b | memories/ | preference (8), fact (15) |
| Schedule | Pink #ec4899 | cron/ | Daily standup, Weekly digest |
| MCP Server | Teal #14b8a6 | Auto-discovered | Claude Desktop, Cursor MCP |
| Remote Agent | Purple #8b5cf6 | LAN scan + A2A | Peer Skales, CrewAI, n8n |
| From | To | Meaning | Style |
|---|---|---|---|
| Agent | Skill | Agent can use this skill | Solid, source color |
| Agent | Task | Agent executes this task | Solid, source color |
| Task | Memory | Task produces memory | Solid, source color |
| Schedule | Agent | Schedule triggers agent | Solid, source color |
| MCP Server | Agent | Agent has access to tool | Dashed, teal |
| Remote Agent | Agent | Cross-instance delegation | Dotted, purple |
| Tool | Stars | Agent Viz | Peer Discovery | MCP | A2A | Local-First | ROI Impact |
|---|---|---|---|---|---|---|---|
| Skales (with this) | Growing | ✓ | ✓ mDNS | Proposed | Proposed | ✓ Desktop | High |
| n8n | ~181K | ✓ | ✗ | ✓ Native | Community | Self-host | Medium |
| Dify | ~135K | ✓ | ✗ | ✓ v1.6.0 | Plugin | Self-host | Medium |
| CrewAI | ~47K | ✗ | ✗ | ✓ Native | ✓ Native | ✗ Cloud | Medium |
| LangGraph | ~28K | ✗ | ✗ | ✓ Platform | ✓ Platform | ✗ Cloud | Low |
| Flowise | ~30K | ✓ | ✗ | ✓ Native | Community | Self-host | Low |
| Mission Control | Alpha | ✓ | Filesystem | ✓ Audit | Messaging | ✓ | Medium |
Star counts approximate as of March 2026. MCP/A2A status verified against official docs and GitHub repos. Landscape is evolving rapidly.
Most AI products treat AI as a tool. Use it, close it, forget it.
Skales treats AI as a companion. It remembers you, plans with you, works alongside you. It runs on your machine, not someone else's server. Your data stays yours.
That's rare. That's worth building on.