kli-team

Coordinate AI agents by bridging in-session tools with a persistent task graph.

26|3|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/kleisli-io/kli --skill kli-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kli-team
Source: https://github.com/kleisli-io/kli/tree/main/plugin/skills/kli-team
Command: npx skills add https://github.com/kleisli-io/kli --skill kli-team

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill bridges the gap between in-session AI team coordination and a persistent, shared task graph, ensuring seamless collaboration and knowledge persistence across AI agents and sessions.

Core Features & Use Cases

  • Team Coordination: Facilitates communication, task assignment, and conflict resolution among AI teammates.
  • Task Graph Integration: Connects in-session activities with a persistent knowledge base for context, history, and future learning.
  • Use Case: When leading a team of AI agents to implement a new software feature, use this Skill to bootstrap context from previous work, assign specific files to agents, monitor for overlapping edits, and aggregate findings into the task graph upon completion.

Quick Start

Use the kli-team skill to bootstrap context for task ID 'task-123' before spawning your team.

Frequently Asked Questions about kli-team

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

FAQPage Schema
How do I coordinate multiple AI agents on a shared task graph?

To coordinate AI agents on a shared task graph, this Skill bridges in-session communication with a persistent, event-sourced knowledge base. It manages team dynamics and task lifecycles for complex, collaborative workflows.

How does multi-agent knowledge management persist context across sessions?

Multi-agent knowledge management persists context by connecting in-session activities to an event-sourced task graph. This ensures shared history and future learning are aggregated across different AI sessions.

What is the best way to bootstrap context before spawning an AI team?

The best way to bootstrap context is using the Skill to load persistent task graph history for a specific ID. This provides the required background before spawning agents for collaborative work.

Can I use this to detect overlapping edits when assigning files to AI teammates?

Yes, you can detect overlapping edits. The Skill monitors team dynamics and facilitates conflict resolution among AI teammates to prevent overlapping edits during task assignment.

Does multi-agent coordination work without external dependencies?

Yes, multi-agent coordination works without external dependencies. The Skill relies on orchestrating internal team and MCP tools to manage communication and record observations.

When should I not use an event-sourced task graph for AI collaboration?

You should not use an event-sourced task graph if your workflow requires no persistent history or conflict detection. It demands careful orchestration of tools, which adds overhead for simple, non-collaborative tasks.