Space Coordination (POC)

Coordinate Space tasks and workflows via direct HTTP/RPC API calls from Bash.

4|1|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/lsm/HyperNeo --skill space-coordination-poc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Space Coordination (POC)
Source: https://github.com/lsm/HyperNeo/tree/main/packages/daemon/src/lib/space/skills/space-coordination
Command: npx skills add https://github.com/lsm/HyperNeo --skill space-coordination-poc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Provides a fallback for Space task/workflow coordination when MCP coordination tools are unavailable.

Core Features & Use Cases

  • Non-MCP Path: Coordinates Space tasks and workflows independently of MCP tool schemas.
  • Local API Interaction: Directly calls the local Space runtime HTTP/RPC API from Bash.
  • Use Case: Use this skill when you need to ensure Space coordination without relying on MCP tool schemas being present in the model context.

Quick Start

Use the space-coordination skill to create a new task with a specific space ID, title, and description.

Frequently Asked Questions about Space Coordination (POC)

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate Space tasks when MCP tools are unavailable?

You can coordinate Space tasks without MCP by using direct HTTP/RPC API calls from Bash. This provides a resilient fallback path for task management and workflow coordination when MCP tool schemas are missing from the model context.

What is a non-MCP workflow coordination path for Space?

A non-MCP workflow coordination path interacts directly with the local Space runtime HTTP/RPC API from Bash. It manages tasks and workflows independently, bypassing the need for MCP tool schemas to be present in the model context.

How do I create a Space task using Bash without MCP?

To create a Space task without MCP, use the space-coordination skill to make direct local API calls from Bash. You provide a specific space ID, title, and description to initialize the task within the Space runtime.

Can I manage Space workflows without relying on MCP tool schemas?

Yes, you can manage Space workflows independently of MCP tool schemas. The skill uses direct HTTP/RPC API calls from Bash to interact with the local Space runtime, ensuring task coordination remains functional.

When should I use a direct API fallback for Space task management?

Use a direct API fallback for Space task management when MCP coordination tools are inaccessible or unavailable. This ensures resilient workflow coordination by directly calling the local Space runtime HTTP/RPC API from Bash.

Does Space task coordination work without MCP dependencies?

Yes, Space task coordination works without MCP dependencies by using Bash scripts to execute direct HTTP/RPC API calls. This approach guarantees task management and workflow coordination remain operational without relying on MCP tool schemas.