Delegate Tasks to OpenSpace#

OpenSpace is connected as an MCP server. You have 4 tools available: execute_task, search_skills, fix_skill, upload_skill.

When to use#

• You lack the capability — the task requires tools or capabilities beyond what you can access
• You tried and failed — you produced incorrect results; OpenSpace may have a tested skill for it
• Complex multi-step task — the task involves many steps, tools, or environments that benefit from OpenSpace's skill library and orchestration
• User explicitly asks — user requests delegation to OpenSpace

Tools#

execute_task#

Delegate a task to OpenSpace. It will search for relevant skills, execute, and auto-evolve skills if needed.

text

execute_task(task="Monitor Docker containers, find the highest memory one, restart it gracefully", search_scope="all")

ParameterRequiredDefaultDescriptiontaskyes—Task instruction in natural languagesearch_scopeno"all"Local + cloud; falls back to local-only if no API keymax_iterationsno20Max agent iterations — increase for complex tasks, decrease for simple ones

Check response for evolved_skills. If present with upload_ready: true, decide whether to upload (see "When to upload" below).

json

{
  "status": "success",
  "response": "Task completed successfully",
  "evolved_skills": [
    {
      "skill_dir": "/path/to/skills/new-skill",
      "name": "new-skill",
      "origin": "captured",
      "change_summary": "Captured reusable workflow pattern",
      "upload_ready": true
    }
  ]
}

search_skills#

Search for available skills before deciding whether to handle a task yourself or delegate.

text

search_skills(query="docker container monitoring", source="all")

ParameterRequiredDefaultDescriptionqueryyes—Search query (natural language or keywords)sourceno"all"Local + cloud; falls back to local-only if no API keylimitno20Max resultsauto_importnotrueAuto-download top cloud skills locally

fix_skill#

Manually fix a broken skill.

text

fix_skill(
  skill_dir="/path/to/skills/weather-api",
  direction="The API endpoint changed from v1 to v2, update all URLs and add the new 'units' parameter"
)

ParameterRequiredDescriptionskill_diryesPath to skill directory (must contain SKILL.md)directionyesWhat's broken and how to fix — be specific

Response has upload_ready: true → decide whether to upload.

upload_skill#

Upload a skill to the cloud community. For evolved/fixed skills, metadata is pre-saved — just provide skill_dir and visibility.

text

upload_skill(
  skill_dir="/path/to/skills/weather-api",
  visibility="public"
)

For new skills (no auto metadata — defaults apply, but richer metadata improves discoverability):

text

upload_skill(
  skill_dir="/path/to/skills/my-new-skill",
  visibility="public",
  origin="imported",
  tags=["weather", "api"],
  created_by="my-bot",
  change_summary="Initial upload of weather API skill"
)

ParameterRequiredDefaultDescriptionskill_diryes—Path to skill directory (must contain SKILL.md)visibilityno"public"``"public" or "private"``originnoautoHow the skill was createdparent_skill_idsnoautoParent skill IDstagsnoautoTagscreated_bynoautoCreatorchange_summarynoautoWhat changed

When to upload#

SituationActionSkill was originally from the cloudUpload back as "public" — return the improvement to the communityFix/evolution is generally usefulUpload as "public"Fix/evolution is project-specificUpload as "private", or skipUser says to shareUpload with the visibility the user wants

Notes#

• execute_task may take minutes — this is expected for multi-step tasks.
• upload_skill requires a cloud API key; if it fails, the evolved skill is still saved locally.
• After every OpenSpace call, tell the user what happened: task result, any evolved skills, and your upload decision.