/analyze-task
Check OSWorld tasks. Validate the evaluation function, verify that the instruction is feasible given the task setup and agent-visible files, inspect setup artifacts when needed, and produce both markdown and structured JSON reports.
$ npx -y skills add AMAP-ML/LongHorizon-Harness --skill analyze-task --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/analyze-task
Context preview
The summary Claude sees to decide when to auto-load this skill.
Check OSWorld tasks. Validate the evaluation function, verify that the instruction is feasible given the task setup and agent-visible files, inspect setup artifacts when needed, and produce both markdown and structured JSON reports.
SKILL.md
analyze-task.SKILL.mdname: analyze-task description: "Check OSWorld tasks. Validate the evaluation function, verify that the instruction is feasible given the task setup and agent-visible files, inspect setup artifacts when needed, and produce both markdown and structured JSON reports."
If only one task is issued, analyze it directly with instruction: [analyze-single-task.md](prompts/analyze-single-task.md).
If multiple tasks are issued, use subagents to analyze them in parallel (one agent for each task) and save reports under `check/<task_id>/`. Do not analyze them sequentially by yourself. DO NOT tell it what to do. Just ask the subagent to analyze the task in target directory and use this skill (analyze-task) to do the analysis. Pass any user instructions to every subagent.
After the subagents finish, do nothing but report to user that the check is done and where to find the reports.
The long-horizon computer-use harness. Run AI agents across desktop apps and the CLI for extended periods while preserving task state and making reliable progress on complex workflows. Features fresh-context execution, durable verified state, independent auditing, recoverable progress, and native Claude Code / Codex / OpenClaw integration.
Repo: AMAP-ML/LongHorizon-Harness
Other skills on longhorizon-harness.
- /analyze-traj
Analyze OSWorld-V2 agent trajectory logs and task results to produce actionable insights. Use this skill whenever the user wants to understand agent performance on OSWorld tasks — including analyzing trajectories, reviewing task results, finding error patterns, comparing code vs
Open skill - /migrate-osworld-agent
Migrate an agent from upstream OSWorld into this OSWorld-V2 repository, add matching evaluation entrypoints, and verify the integration.
Open skill - /setup-osworld
Provision and verify an OSWorld-V2 checkout after clone. Use when the user asks for OSWorld-V2 setup, installation, onboarding, AWS provider setup, Docker provider setup, mocked website server setup, GitLab server setup, gated task download, CUA-Harness hybrid experiment setup,
Open skill - /weavebench-cua-reproduce
Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout. Use when the user wants an AI coding agent to set up dependencies, download WeaveBench assets, prepare the 120G VM, configure Qwen/Anthropic-compatible APIs, run smoke tests, launch full or subset
Open skill