kj-aiml/heli-harness/concurrent-upgrade

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Use when an embedded compatibility workspace still has shared legacy task state and needs migration to the embedded concurrent task/session/lease layout; linked v0.11 projects use resource-scoped authority instead.

Install

npx vskill@latest install kj-aiml/heli-harness/concurrent-upgrade

SKILL.md

concurrent-upgrade

Scope

This skill is embedded compatibility only.

Do not use it as the authority model for a linked v0.11 project. Linked projects use project binding plus execution-local resource authority.

Problem

An older embedded workspace may still use one shared .heli-harness/state/current-task.md:

  • two agents can race on the same shared state;
  • session context may report Workspace mode: legacy;
  • embedded task/session/lease isolation has not been initialized.

When to migrate

Use this skill when all of the following are true:

  • the project is intentionally using the embedded .heli-harness/ layout;
  • heli status reports embedded legacy mode;
  • multiple agents/sessions may write or durable compatibility task isolation is required.

If .heli/workspace.json exists, stop and use linked resource authority instead.

Upgrade steps

  1. Confirm the embedded workspace root.
  2. Check mode:

``bash heli status ``

  1. Migrate singular compatibility state or create a fresh compatibility task:

``bash heli task migrate-legacy --id <task-id> # or heli task create <task-id> --work-item <key> --repo <name> ``

  1. Claim compatibility write authority and bind the session:

``bash heli task claim <task-id> --mode write # export HELI_SESSION_ID=... from command output ``

  1. Prefer a separate git worktree per parallel task.
  2. Use distinct task/session identity for a second writer or keep it review/observe only.
  3. After concurrent mode is active, task-local state under .heli-harness/tasks/<task-id>/ is authoritative for this embedded compatibility workflow; shared state/current-task.md is not.

Rules

  • Do not invent ownership in prose.
  • YOLO does not bypass compatibility write ownership.
  • Hook/plugin absence means enforcement may be advisory, but state transitions should still use the CLI.
  • Future heli update preserves embedded compatibility state; it does not convert the workspace into linked v0.11 topology.

Output after upgrade

text
Layout: embedded compatibility
Mode: concurrent
Task id:
Session id:
Compatibility write authority: yes|no
Worktree:
Other active tasks:

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/kj-aiml/heli-harness/concurrent-upgrade/badge)](https://verified-skill.com/skills/kj-aiml/heli-harness/concurrent-upgrade)

Something wrong with this skill or its page? Tell us.