agentleFS
RoentekRoentek/Claude_Code_Boilerplate_Framework/.claude/skills/delegate-task/SKILL.md

delegate-task

Skill4 starsChanged 6 months agoMITView on GitHub

Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check response for evolved_skills.

    line 33
  2. Distinctive:

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

    line 53
  3. Very specific:

    If execute_task times out, first check the host's MCP timeout settings.

    line 130
  4. Distinctive:

    After every OpenSpace call, tell the user what happened: task result, any evolved skills, and your upload decision.

    line 132

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Delegate Tasks to OpenSpace

OpenSpace is connected as an MCP server. Whether the host uses stdio, sse, or streamable-http, you have the same 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.

execute_task(task="Monitor Docker containers, find the highest memory one, restart it gracefully", search_scope="all")
ParameterRequiredDefaultDescription
taskyes—Task instruction in natural language
search_scopeno"all"Local + cloud; falls back to local-only if no API key
max_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).

{
  "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.

search_skills(query="docker container monitoring", source="all")
ParameterRequiredDefaultDescription
queryyes—Search query (natural language or keywords)
sourceno"all"Local + cloud; falls back to local-only if no API key
limitno20Max results
auto_importnotrueAuto-download top cloud skills locally

fix_skill

Manually fix a broken skill.

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"
)
ParameterRequiredDescription
skill_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.

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

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

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"
)
ParameterRequiredDefaultDescription
skill_diryes—Path to skill directory (must contain SKILL.md)
visibilityno"public""public" or "private"
originnoautoHow the skill was created
parent_skill_idsnoautoParent skill IDs
tagsnoautoTags
created_bynoautoCreator
change_summarynoautoWhat changed

When to upload

SituationAction
Skill was originally from the cloudUpload back as "public" — return the improvement to the community
Fix/evolution is generally usefulUpload as "public"
Fix/evolution is project-specificUpload as "private", or skip
User says to shareUpload with the visibility the user wants

Notes

  • execute_task may take minutes — this is expected for multi-step tasks.
  • If execute_task times out, first check the host's MCP timeout settings. Changing from stdio to HTTP (sse or streamable-http) does not remove host-side per-call time limits.
  • 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.