jat-start

Initialize JAT sessions with identity, mail checks, and task selection.

248|27|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/joewinke/jat --skill jat-start
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jat-start
Source: https://github.com/joewinke/jat/tree/main/skills/jat-start
Command: npx skills add https://github.com/joewinke/jat --skill jat-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the initial setup of a JAT session by establishing agent identity, checking Agent Mail, selecting relevant tasks, detecting conflicts, reserving files, emitting IDE signals, and preparing the workspace before work begins.

Core Features & Use Cases

  • Establish identity and session context
  • Read Agent Mail and prepare for task assignment
  • Task selection, conflict checks, and file reservation
  • Emit IDE signals to coordinate work across agents
  • Use Case: At session start, a supervising agent runs this to ensure the session is properly initialized and ready to begin work.

Quick Start

/skill:jat-start

Frequently Asked Questions about jat-start

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

FAQPage Schema
How do I initialize an agent session and establish agent identity for task work?

To initialize an agent session, you can use a session startup skill to establish agent identity, check Agent Mail, select a task, and emit IDE signals. This ensures a single-task context and reserves files before work begins.

What is conflict detection in multi-agent workspace environments?

Conflict detection in multi-agent environments identifies potential task or file overlaps before work begins. It runs during session initialization to reserve files and ensure agents operate within a single-task context without collisions.

How do I start a JAT session and prepare for task assignment?

You start a JAT session by running the initialization command, which parses arguments, establishes identity, checks Agent Mail, and selects a task. This prepares the workspace and emits work signals via jat-signal.

Can I use IDE signals to coordinate work across multiple agents?

Yes, IDE signals coordinate work across agents during session initialization. The session startup process emits these signals to establish a single-task context and ensure all agents are aware of the active work state.

Do I need to check Agent Mail before selecting a task in an automated workflow?

Checking Agent Mail before task selection is part of the session initialization process. It ensures the agent receives relevant task assignments and prepares the workspace before any file reservation or conflict detection occurs.