init

Initialize a dotagent session by claiming session state with a valid session_id.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Koryto/dotagent --skill init-koryto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/Koryto/dotagent/tree/main/.agent/skills/init
Command: npx skills add https://github.com/Koryto/dotagent --skill init-koryto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a dotagent session from within a supported runtime, ensuring the agent initializes through the framework's controlled startup sequence and maintains correct session state.

Core Features & Use Cases

  • Enforces framework-first startup by loading the active session, project state, and workflow contracts in the defined order.
  • Supports resuming an in-progress session or starting a new one based on the bound session state and active workflow.
  • Provides a stable native entrypoint for runtime integrations, ensuring human ownership and traceable session management.

Quick Start

Run the runtime entrypoint with a valid session_id to claim the session and start a properly initialized dotagent workflow.

Frequently Asked Questions about init

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

FAQPage Schema
How do I initialize a dotagent session from within a runtime?

To initialize a dotagent session within a runtime, run the native entrypoint with a valid session_id to claim the session state and load the workflow context. This ensures the agent starts correctly through the framework's controlled startup sequence.

What is the correct startup order for loading dotagent session state?

The correct startup order for loading dotagent session state is hot, warm, and cold context. This prescribed sequence is enforced by the claim-state binding to ensure the agent properly initializes the active workflow and project state.

Can I resume an in-progress dotagent workflow using a session_id?

Yes, you can resume an in-progress dotagent workflow by providing a valid session_id. The claim-state mechanism binds the active session state, allowing the agent to pick up the existing workflow rather than starting a new one.

Does the dotagent init skill require a project to already be initialized?

Yes, the dotagent init skill requires a project to already be initialized. It is designed to apply to scenarios where the agent must start from the framework correctly by claiming the session state and surfacing the active workflow.

Why does my dotagent runtime integration fail to load the active workflow?

A dotagent runtime integration fails to load the active workflow if a valid session_id is not provided. Without claiming the session state via dotagent claim-state, the framework cannot bind the session or load the hot, warm, and cold context.