Coordinate Combyne-driven tasks across agents via the Combyne API.
npx skills add https://github.com/krishsharma1008/ADE --skill combyne
Please help me install this Agent Skill. Skill: combyne Source: https://github.com/krishsharma1008/ADE/tree/main/skills/combyne Command: npx skills add https://github.com/krishsharma1008/ADE --skill combyne
Interacts with the Combyne control plane API to coordinate tasks, manage assignments, and enforce governance. Use when you need to check assignments, update task statuses, delegate work, post comments, or call any Combyne API endpoint. Do NOT use for domain-specific work — only for coordination.
Trigger a heartbeat for your Combyne agent to fetch tasks, act on them within the moment's window, and post results back to the issue tracker.
High-intent search queries and answers about installing and using this skill.
The heartbeat pattern coordinates AI agent tasks by triggering agents to fetch assignments, execute work within a time window, and post results back to the issue tracker. This cycle repeats to manage execution and ensure continuous task coordination.
To authenticate API calls for AI agent governance and issue management, you configure the environment variables COMBYNE_API_KEY and COMBYNE_RUN_ID. These variables authenticate requests to the control plane API for issues, comments, approvals, and workspace data.
Yes, you can use this approach to delegate work and manage subtasks across teams. The API workflow supports cross-team delegation, approvals, comments, and governance enforcement alongside standard issue management functions.
The best way to update task statuses and post comments for automated agents is using the control plane API endpoints. You call the API to update task statuses, post comments, and enforce governance within the heartbeat execution window.
Yes, this task coordination method supports creating workspaces and project instructions. You can create and manage workspaces, projects, and agent instruction paths directly via the control plane API endpoints.
You should not use an API coordination layer for AI agents when performing domain-specific work. It is designed strictly for coordination, governance, and task management, not for executing the actual domain tasks themselves.
navyapdh11Coordinate multi-agent tasks via heartbeat API calls to the Paperclip control plane.
logikwiseManage task assignments, statuses, comments, and routines via the Paperclip control plane API.
khoabdOrchestrate task workflows and approvals via the Paperclip control plane API.
LiamFuller07Coordinate tasks, decisions, and memory via The Molt Company API.
