handoff-state

Name: handoff-state
Author: ynotfins

Shared operating pattern for documenting current state, evidence, blockers, and next actions between employees.

by ynotfins(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from ynotfins/open--claw (open-claw/AI_Employee_knowledgebase/AI_employees/code-reviewer/skills/handoff-state/SKILL.md). Install upstream with npx skills add ynotfins/open--claw --skill handoff-state. Copyright stays with the author.

Handoff State

Status: READY

Purpose

Reduce context loss between employees by making state, blockers, and evidence explicit.

Required Handoff Fields

Goal
Current status
Evidence produced
Open blockers or risks
Recommended next action
Owner of the next action

Rule

If it is not written down, it does not count as handed off.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Installed into a catalogue, chosen by a router

Install handoff-state and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

ynotfins-open-claw-handoff-state.ocm.jsonjson

{
  "ocm": "1",
  "id": "ynotfins-open-claw-handoff-state",
  "kind": "skill",
  "name": "handoff-state",
  "description": "Shared operating pattern for documenting current state, evidence, blockers, and next actions between employees.",
  "publisher": "ynotfins",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Shared operating pattern for documenting current state, evidence, blockers, and next actions between employees."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/ynotfins/open--claw",
      "path": "open-claw/AI_Employee_knowledgebase/AI_employees/code-reviewer/skills/handoff-state/SKILL.md",
      "ref": "7437c0fd769e8ba45197b10e13c60278538f2d43",
      "url": "https://github.com/ynotfins/open--claw/blob/7437c0fd769e8ba45197b10e13c60278538f2d43/open-claw/AI_Employee_knowledgebase/AI_employees/code-reviewer/skills/handoff-state/SKILL.md",
      "key": "ynotfins/open--claw/open-claw/AI_Employee_knowledgebase/AI_employees/code-reviewer/skills/handoff-state/SKILL.md"
    }
  },
  "instructions": "# Handoff State\n\n## Status: READY\n\n## Purpose\nReduce context loss between employees by making state, blockers, and evidence explicit.\n\n## Required Handoff Fields\n- Goal\n- Current status\n- Evidence produced\n- Open blockers or risks\n- Recommended next action\n- Owner of the next action\n\n## Rule\nIf it is not written down, it does not count as handed off.",
  "cost": {
    "context_tokens": 88
  }
}

Fetch it by URL: GET /api/v1/registry/ynotfins-open-claw-handoff-state/manifest?version=1.0.0