How do I install the Complyctl skill?

Run npx skillmds@latest add tomevault-io/complyctl in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Complyctl safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Complyctl?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Complyctl free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Complyctl?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Complyctl by tomevault-io — Agent Skill

Name: Complyctl
Author: tomevault-io

File contents

Forge Coordination

Patterns for coordinating parallel agent work.

Coordinator Protocol

Initialize: comms_init(project_path=".", task_description="...")
Check learnings: hivemind_find(query="<task keywords>")
Select strategy: forge_get_strategy_insights(task="<task>")
Decompose: forge_decompose(task="<task>", context="<learnings>")
Create epic: org_create_epic(epic_title="<task>", subtasks=[...])
Spawn workers: forge_spawn_subtask(bead_id, epic_id, subtask_title, files)
Monitor: comms_inbox() + forge_status(epic_id, project_key)
Review: forge_review(task_id, files_touched) for each worker
Complete: forge_complete(bead_id, summary, files_touched)
Learn: hivemind_store(information="...", tags="forge,<topic>")

Worker Protocol

Initialize: comms_init(project_path=".", task_description="...")
Check learnings: hivemind_find(query="<task keywords>")
Reserve files: comms_reserve(paths=[...], reason="...")
Implement: Make changes to reserved files
Report progress: forge_progress(bead_id, progress_percent, status)
Store learnings: hivemind_store(information="...", tags="...")
Complete: forge_complete(bead_id, summary, files_touched)

File Reservation Rules

Workers MUST reserve files before editing
Coordinators NEVER reserve files
Use comms_reserve(paths=[...], exclusive=true) for exclusive access
Release files when done: comms_release(paths=[...])
Emergency release: comms_release_all() (coordinator only)

Progress Reporting

Report at milestones: 25%, 50%, 75%, 100%

forge_progress(
  project_key="replicator",
  agent_name="worker-1",
  bead_id="<id>",
  status="in_progress",
  progress_percent=50,
  message="Implemented core logic, starting tests"
)

Conflict Resolution

If a file reservation fails:

Check who holds the reservation
Send a message via comms_send to negotiate
Wait for release or escalate to coordinator

Source: complytime/complyctl — distributed by TomeVault.

---name: complyctldescription: Multi-agent coordination patterns for forge sessions Use when this capability is needed.---# Forge CoordinationPatterns for coordinating parallel agent work.## Coordinator Protocol1. **Initialize**: `comms_init(project_path=".", task_description="...")`2. **Check learnings**: `hivemind_find(query="<task keywords>")`3. **Select strategy**: `forge_get_strategy_insights(task="<task>")`4. **Decompose**: `forge_decompose(task="<task>", context="<learnings>")`5. **Create epic**: `org_create_epic(epic_title="<task>", subtasks=[...])`6. **Spawn workers**: `forge_spawn_subtask(bead_id, epic_id, subtask_title, files)`7. **Monitor**: `comms_inbox()` + `forge_status(epic_id, project_key)`8. **Review**: `forge_review(task_id, files_touched)` for each worker9. **Complete**: `forge_complete(bead_id, summary, files_touched)`10. **Learn**: `hivemind_store(information="...", tags="forge,<topic>")`## Worker Protocol1. **Initialize**: `comms_init(project_path=".", task_description="...")`2. **Check learnings**: `hivemind_find(query="<task keywords>")`3. **Reserve files**: `comms_reserve(paths=[...], reason="...")`4. **Implement**: Make changes to reserved files5. **Report progress**: `forge_progress(bead_id, progress_percent, status)`6. **Store learnings**: `hivemind_store(information="...", tags="...")`7. **Complete**: `forge_complete(bead_id, summary, files_touched)`## File Reservation Rules- Workers MUST reserve files before editing- Coordinators NEVER reserve files- Use `comms_reserve(paths=[...], exclusive=true)` for exclusive access- Release files when done: `comms_release(paths=[...])`- Emergency release: `comms_release_all()` (coordinator only)## Progress ReportingReport at milestones: 25%, 50%, 75%, 100%```forge_progress( project_key="replicator", agent_name="worker-1", bead_id="<id>", status="in_progress", progress_percent=50, message="Implemented core logic, starting tests")```## Conflict ResolutionIf a file reservation fails:1. Check who holds the reservation2. Send a message via `comms_send` to negotiate3. Wait for release or escalate to coordinator---> Source: [complytime/complyctl](https://github.com/complytime/complyctl) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Complyctl