wiki-handoff

Write a session bridge Markdown page to .omc/wiki before /compact or /clear.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HelloWorldSungin/ark-skills --skill wiki-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-handoff
Source: https://github.com/HelloWorldSungin/ark-skills/tree/main/skills/wiki-handoff
Command: npx skills add https://github.com/HelloWorldSungin/ark-skills --skill wiki-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of a session bridge page to capture current session state before disassembly/cleanup, ensuring continuity of context across subsequent steps.

Core Features & Use Cases

  • Writes a properly formatted session-bridge Markdown page under .omc/wiki/ with chain and session metadata.
  • Validates inputs to avoid generic placeholders and enforces scenario slug rules; handles filename collisions.
  • Use Case: before executing /compact or /clear in a multi-step workflow, generate a persistent, taggable bridge page that records task details, open threads, next steps, and summary.

Quick Start

Run the wiki-handoff tool to generate a session-bridge page from the current workflow state.

Frequently Asked Questions about wiki-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve session context before running /compact or /clear in a multi-step workflow?

A session bridge page captures current session state in Markdown before /compact or /clear, recording task details, open threads, and next steps under .omc/wiki/ to ensure continuity across subsequent multi-step workflow stages.

What is a wiki session bridge and when do I need it in an Ark workflow?

A wiki session bridge is a persistent Markdown file written to .omc/wiki that captures chain and session metadata during Ark workflows. You need it before context disassembly or cleanup to enable recovery from handoffs across steps.

How to write a session bridge page that validates workflow inputs and avoids filename collisions?

Writing a session bridge page involves enforcing input validation for chain-id, task-text, and scenario slugs while rejecting generic placeholders. The process handles filename collisions and returns status 0, 2, or 3 to indicate success or validation failures.

Does the session bridge validation enforce specific rules for chain-id and scenario slugs?

Yes, session bridge validation enforces specific rules for chain-id, task-text, and scenario slugs to avoid generic placeholders. It processes inputs, handles filename collisions, and returns statuses 0, 2, or 3 based on validation outcomes.

What are the limitations of using Markdown session bridge pages for context recovery?

Markdown session bridge pages are limited to capturing text-based context state, chain metadata, and task summaries under .omc/wiki. They enforce input validation and handle filename collisions but rely on the directory structure for retrieval.