Huashu Agent Swarm
alchaincyf/huashu-skills
多Agent蜂群并行协作,纯git自组织,适合大型项目开发。当用户提到"蜂群模式"、"多agent"、"并行开发"、"agent swarm"时使用。
Multi-agent task coordination via Git-backed Markdown (tick-md).
$ npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tick-coord --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tick-coord .claude/skills/tick-coord && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tick-coord" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tick-coord into .claude/skills/tick-coord/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tick-coord", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tick-coordType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tick-coord --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tick-coord .agents/skills/tick-coord && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tick-coord" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tick-coord into .agents/skills/tick-coord/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tick-coord", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tick-coord --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tick-coord .cursor/skills/tick-coord && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tick-coord" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tick-coord into .cursor/skills/tick-coord/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tick-coord", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/tick-coord--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tick-coord --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tick-coord .gemini/skills/tick-coord && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tick-coord" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tick-coord into .gemini/skills/tick-coord/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tick-coord", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills tick-coordInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tick-coord .github/skills/tick-coord && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tick-coord" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tick-coord into .github/skills/tick-coord/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tick-coord", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills tick-coord --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tick-coord .opencode/skills/tick-coord && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tick-coord" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/tick-coord into .opencode/skills/tick-coord/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tick-coord", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
tick-coordMulti-agent task coordination via Git-backed Markdown (tick-md).
Tick Coord is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent task coordination via Git-backed Markdown (tick-md). Use when coordinating work across avatars or agents, managing tasks, tracking dependencies, or running multi-agent workflows with TICK.md files.
Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `_meta.json` and `skill.json`).
It sits in Agent Workflows, covering Multi-agent orchestration and Git workflow. It works with Git and Model Context Protocol. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
bashpnpmnpmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
npmjs.comgithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
TICK_SYNC_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Tick Coord loads about 4.9k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 1,281 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,281 words, ~4,901 tokens.
.claude/skills/tick-coord/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Coordinate work across human and AI agents using structured Markdown files. Users interact naturally with you, and you maintain tasks transparently in TICK.md.
Source: Built and linked from
~/clawd/projects/tick-md/cli. To rebuild after changes:cd ~/clawd/projects/tick-md/cli && npm run build
Prerequisites: The Tick CLI and MCP server should already be installed and configured by your environment.
First time setup? See INSTALL.md for editor-specific installation instructions.
Quick Check:
# Verify CLI is available
tick --version
# Check if TICK.md exists in project
ls TICK.md
# If not, initialize
tick initTick Protocol = Git-based task coordination via TICK.md files
ls TICK.mdtick inittick statusUser: "Can you refactor the authentication system?"
Your Actions:
# 1. Create task
tick add "Refactor authentication system" --priority high --tags backend,security
# 2. Register yourself (first time only)
tick agent register @your-name --type bot --roles "engineer,refactoring"
# 3. Claim the task
tick claim TASK-XXX @your-name
# 4. Work on it (do the actual work)
# 5. Add progress comments
tick comment TASK-XXX @your-name --note "Analyzing current auth flow"
tick comment TASK-XXX @your-name --note "Refactored to use JWT tokens"
# 6. Mark complete
tick done TASK-XXX @your-nameUser: "What tasks are we working on?"
# Get comprehensive status
tick status
# Or filter and list tasks
tick list --status in_progress
tick list --claimed-by @bot-nameSummarize the output naturally for the user.
User: "Have the other agents finished their tasks?"
# Check overall status
tick status
# List agents and their work
tick agent list --verbose
# Validate the project
tick validateUser: "Build a user dashboard with charts and data export"
Your Actions:
# Create parent task
tick add "Build user dashboard" --priority high --tags frontend
# Create subtasks with dependencies
tick add "Design dashboard layout" --priority high --tags frontend,design
tick add "Implement data charts" --priority medium --tags frontend,charts --depends-on TASK-XXX
tick add "Add CSV export" --priority low --tags frontend,export --depends-on TASK-XXX
# Visualize dependencies
tick graphtick init # Initialize new project
tick status # View project overview
tick list # List tasks with filters
tick graph # Visualize dependencies
tick watch # Monitor changes in real-time
tick validate # Check for errors
tick sync --push # Commit and push to gittick add "Task title" \
--priority high \ # urgent|high|medium|low
--tags backend,api \ # Comma-separated tags
--assigned-to @agent \ # Assign to agent
--depends-on TASK-001 \ # Dependencies
--estimated-hours 4 # Time estimate
tick claim TASK-001 @agent # Claim task (sets in_progress)
tick release TASK-001 @agent # Release task (back to todo)
tick done TASK-001 @agent # Complete task
tick reopen TASK-001 @agent # Reopen completed task
tick delete TASK-001 # Delete a task
tick comment TASK-001 @agent \ # Add note
--note "Progress update"
tick edit TASK-001 \ # Direct field edit
--title "New title" \
--priority high \
--status in_progresstick reopen TASK-001 @agent # Reopen completed task
tick reopen TASK-001 @agent \ # Reopen and re-block dependents
--re-block
tick delete TASK-001 # Delete task, cleans up deps
tick delete TASK-001 --force # Delete even if has dependents
tick edit TASK-001 --title "X" # Change title
tick edit TASK-001 --priority high # Change priority
tick edit TASK-001 --status todo # Change status directly
tick edit TASK-001 --tags a,b,c # Replace tags
tick edit TASK-001 --add-tag new # Add tag
tick edit TASK-001 --remove-tag old # Remove tag
tick edit TASK-001 \ # Edit dependencies
--depends-on TASK-002,TASK-003
tick undo # Undo last tick operation
tick undo --dry-run # Preview what would be undonetick import tasks.yaml # Import tasks from YAML file
tick import - < tasks.yaml # Import from stdin
tick import tasks.yaml --dry-run # Preview import
tick batch start # Begin batch mode (no auto-commit)
tick batch status # Check batch status
tick batch commit # Commit all batched changes
tick batch abort # Discard batched changestick list # All tasks, grouped by status
tick list --status blocked # Only blocked tasks
tick list --priority urgent # High-priority tasks
tick list --assigned-to @alice # Tasks for specific agent
tick list --tag backend # Tasks with tag
tick list --json # JSON output for scriptstick graph # ASCII dependency tree
tick graph --format mermaid # Mermaid flowchart
tick graph --show-done # Include completed taskstick watch # Watch for changes
tick watch --interval 10 # Custom polling interval
tick watch --filter in_progress # Only show specific statustick agent register @name \ # Register new agent
--type bot \ # human|bot
--roles "dev,qa" \ # Comma-separated roles
--status idle # working|idle|offline
tick agent list # List all agents
tick agent list --verbose # Detailed info
tick agent list --type bot # Filter by type
tick agent list --status working # Filter by statusIf using Model Context Protocol, use these tools instead of CLI commands:
tick_status - Get project status (agents, tasks, progress)tick_validate - Validate TICK.md structuretick_agent_list - List agents with optional filterstick_add - Create new tasktick_claim - Claim task for agenttick_release - Release claimed tasktick_done - Complete task (auto-unblocks dependents)tick_comment - Add note to tasktick_reopen - Reopen completed tasktick_delete - Delete a tasktick_edit - Direct field edit (bypasses state machine)tick_undo - Undo last tick operationtick_agent_register - Register new agentMCP Example:
// Create task via MCP
await tick_add({
title: "Refactor authentication",
priority: "high",
tags: ["backend", "security"],
assignedTo: "@bot-name"
})
// Claim it
await tick_claim({
taskId: "TASK-023",
agent: "@bot-name"
})✅ Good: User says "refactor the auth", you create task automatically ❌ Bad: Making user explicitly create tasks
Register once:
tick agent register @your-bot-name --type bot --roles "engineer"Then use consistently:
tick claim TASK-001 @your-bot-name
tick done TASK-001 @your-bot-name# ✅ Good - explains what and why
tick comment TASK-005 @bot --note "Switched from REST to GraphQL for better type safety and reduced over-fetching"
# ❌ Bad - too vague
tick comment TASK-005 @bot --note "Updated API"Create subtasks with dependencies:
tick add "Set up CI/CD pipeline" --priority high
tick add "Configure GitHub Actions" --depends-on TASK-010
tick add "Add deployment scripts" --depends-on TASK-011
tick add "Set up staging environment" --depends-on TASK-011# Make sure task exists and isn't claimed
tick status
# Then claim
tick claim TASK-XXX @your-nameThe file has three sections:
Example:
---
project: my-app
schema_version: "1.0"
next_id: 5
---
# Agents
| Name | Type | Roles | Status | Working On |
|------|------|-------|--------|------------|
| @alice | human | owner | working | TASK-003 |
| @bot | bot | engineer | idle | - |
# Tasks
\```yaml
id: TASK-001
title: Build authentication
status: done
priority: high
claimed_by: null
# ... more fields
history:
- ts: 2026-02-07T10:00:00Z
who: @bot
action: created
- ts: 2026-02-07T14:00:00Z
who: @bot
action: done
\```
Implemented JWT-based authentication with token refresh...When you complete a task, dependent tasks automatically unblock:
# TASK-002 depends on TASK-001
# TASK-002 status: blocked
tick done TASK-001 @bot
# TASK-002 automatically changes to: todoValidation catches circular dependencies:
tick validate
# Error: Circular dependency detected: TASK-001 → TASK-002 → TASK-003 → TASK-001tick sync --push
# Automatically generates: "feat: complete TASK-001, TASK-002; update TASK-003"If a task was marked done prematurely:
tick reopen TASK-001 @bot
# Sets status back to in_progress, records in history
tick reopen TASK-001 @bot --re-block
# Also re-blocks any tasks that depend on this one# Undo the last tick operation
tick undo
# Preview what would be undone first
tick undo --dry-run
# Direct field edits (bypasses state machine)
tick edit TASK-001 --status todo --priority urgentFor multiple changes without individual commits:
tick batch start
# Now make multiple changes...
tick add "Task 1" --priority high
tick add "Task 2" --priority medium
tick claim TASK-001 @bot
# ...
tick batch commit # Single commit for all changes
# Or: tick batch abort # Discard all changestick watch
# [10:23:45] ✓ Added: TASK-015 - Implement user search
# [10:24:12] 🔒 TASK-015 claimed by @bot
# [10:26:33] ⟳ TASK-015: in_progress → doneWorkflow: init → add → claim → work → comment → done → sync
Essential: status | add | claim | done | list | graph
Corrections: reopen | delete | edit | undo
Bulk: import | batch start/commit/abort
Coordination: agent register | agent list | validate | watch
Git: sync --pull | sync --pushThe tick-coord skill includes a built-in web dashboard for visualizing task state. It's an on-demand Astro + React app that reads from the Convex API, similar to how Prisma Studio or Drizzle Studio work. Spin it up when you need to inspect the board, stop it when you're done.
When the user says "launch project board", "launch kanban", "show me the board", "open dashboard", or similar:
# SKILL_DIR should resolve to wherever tick-coord is installed
SKILL_DIR="<tick-coord-install-path>"
# Start the dashboard
bash "$SKILL_DIR/scripts/tick-board.sh" start
# Check if it's running
bash "$SKILL_DIR/scripts/tick-board.sh" status
# Stop when done
bash "$SKILL_DIR/scripts/tick-board.sh" stopDefault port is 3000. Override with TICK_BOARD_PORT=8080.
The board fetches live data from the Convex deployment and auto-refreshes every 30 seconds.
The dashboard dev server must run as a detached background process to avoid being killed by exec tool timeouts. The tick-board.sh script handles this automatically using setsid and a PID file, but if you need to start it manually:
# CORRECT — detached, survives exec timeout
cd "$SKILL_DIR/web"
setsid pnpm dev --port 3000 --host 0.0.0.0 </dev/null > /tmp/tick-board.log 2>&1 &
echo $! > /tmp/tick-board.pid
# WRONG — will be killed when exec times out
pnpm dev --port 3000 --host 0.0.0.0Always use the script or the setsid pattern. Never run the dev server as a foreground exec command.
The dev server binds to 0.0.0.0, making it available on all network interfaces:
| Access method | URL | When to use |
|---|---|---|
| Local | http://localhost:3000/ | Same machine |
| LAN | http://<machine-ip>:3000/ | Devices on same network |
| Tailscale | http://<tailscale-ip>:3000/ | Remote access via Tailnet |
To find available IPs, check the dev server output or run hostname -I.
For Tailscale users: Use the Tailscale IP (usually 100.x.x.x) to access from any device on your Tailnet. Run tailscale ip to find it.
The dev server is a development tool with no built-in authentication or encryption. When exposing it on a network:
This is a development inspection tool, not a production server. Use it like you'd use Prisma Studio: locally, temporarily, on trusted networks. We provide this as-is for convenience; securing your network and access is your responsibility.
After adding/updating tasks in TICK.md, sync to Convex so the dashboard reflects current state:
CONVEX_SITE_URL=https://<your-convex-deployment>.convex.site \
TICK_SYNC_KEY=<your-sync-key> \
bash "$SKILL_DIR/scripts/tick-sync.sh"~/clawd/projects/tick-mdFor multi-agent setups, use structured tag conventions to enable domain ownership and project tracking:
project:<name> — group tickets under effortscategory:<type> — classify by domain (tech, product, marketing, sales, founder, community, ops)See docs/tag-conventions.md for full details, usage examples, and migration guide.
This section covers patterns for multi-avatar deployments where one OpenClaw instance runs multiple agents (e.g., CEO + CTO) sharing task state via TICK.md.
Each avatar uses a consistent @agent-name for all tick operations. This is set per-avatar in their workspace:
tick agent register @your-name --type bot --roles "your,roles"@name in every command: tick claim TASK-XXX @your-nameIf your workspace has TICK_AGENT_ID set in environment or defined in AGENTS.md, use that as your identity.
Each project has its own TICK.md in its root directory. Before running tick commands, cd into the correct project:
cd ~/path/to/project && tick statusIf TICK.md doesn't exist yet, initialize: tick init
When you complete a task that unblocks work for another avatar:
Complete your task with a descriptive comment:
tick done TASK-001 @cto
tick comment TASK-001 @cto --note "Auth system built with JWT. Endpoint: /api/auth. CTO handoff: ready for product review."The completing agent's comment should include:
Dependent tasks auto-unblock when blockers complete. The next avatar checks:
tick list --status todo --assigned-to @their-nameThe main/CEO avatar delegates work by:
Creating tasks with assignments:
tick add "Design database schema" --priority high --assigned-to @cto --tags engineeringSpawning the specialist via OpenClaw:
sessions_spawn(agentId: "cto", task: "Check TICK.md for assigned tasks. Claim, complete, and comment on each.")The specialist avatar:
tick list --assigned-to @cto to find workThe orchestrator checks results:
tick statusmaxConcurrent controls parallelism).tick/lock) to prevent simultaneous writestick validate to check for structural issues after any unexpected statetick init in a project that already has TICK.mdMIT
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files in skills/tick-coord of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Tick Coord next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tick Coord this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Huashu Agent Swarmalchaincyf/huashu-skills | 1.7k | 1 repos | ~576 | Automated safety check: Pass | MIT | |
| Foremergenaw103/foremerge | 537 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Puppetmaster Agent Orchestrationprofessorpalmer/Puppetmaster | 467 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Agtx Task Sweepfynnfluegge/agtx | 1.7k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Cas Supervisorcodingagentsystem/cas | 176 | — | ~1.8k | Automated safety check: Pass | MIT |
alchaincyf/huashu-skills
多Agent蜂群并行协作,纯git自组织,适合大型项目开发。当用户提到"蜂群模式"、"多agent"、"并行开发"、"agent swarm"时使用。
naw103/foremerge
Coordinate parallel coding agents with Foremerge's local Git-compatible CLI and MCP server.
professorpalmer/Puppetmaster
Operates and supervises Puppetmaster, a multi-agent orchestrator, through its MCP tools or CLI, picking the right verb for edits, reviews, audits and long-running jobs.
fynnfluegge/agtx
Breaks a conversation's results into feature-level tasks and pushes them to the agtx kanban board, where each task gets its own worktree and agent session.
codingagentsystem/cas
Factory supervisor guide for multi-agent EPIC orchestration.
jpicklyk/task-orchestrator
Resolves ready MCP work items into a run plan, shows it to you, then executes it through the Workflow tool or direct subagent dispatch, with post-run verification.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Works with
Categories
Multi-agent task coordination via Git-backed Markdown (tick-md). Tick Coord is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent task coordination via Git-backed Markdown (tick-md).
Tick Coord fits situations like: coordinating work across avatars; tracking dependencies; running multi-agent workflows with TICK.md files.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a claude-code`. Or copy the skill folder (skills/tick-coord in LeoYeAI/openclaw-master-skills) into .claude/skills/tick-coord in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a codex`. Or copy the skill folder (skills/tick-coord in LeoYeAI/openclaw-master-skills) into .agents/skills/tick-coord in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tick-coord, .gemini/skills/tick-coord, .github/skills/tick-coord and .opencode/skills/tick-coord in your project.
Going by SKILL.md and its folder, Tick Coord needs the command-line tools its instructions call (bash, pnpm and npm) and credentials named TICK_SYNC_KEY.
SKILL.md names 2 domains. As links in the text: npmjs.com and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Tick Coord is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.9k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Tick Coord: Huashu Agent Swarm (alchaincyf/huashu-skills, 1.7k stars), Foremerge (naw103/foremerge, 537 stars), Puppetmaster Agent Orchestration (professorpalmer/Puppetmaster, 467 stars) and Agtx Task Sweep (fynnfluegge/agtx, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.