Agent skill

Tick Coord

by LeoYeAI in LeoYeAI/openclaw-master-skills

Multi-agent task coordination via Git-backed Markdown (tick-md).

MITAuto-check passedAgent Workflows

Install Tick Coord

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill tick-coord -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills tick-coord --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
tick-coord
GitHub stars
2.2k
Token cost
~4.9k tokens
SKILL.md length
1,281 words
Files
3
Skills in repo
972
Repo updated
First seen
Licence
MIT

At a glance

Multi-agent task coordination via Git-backed Markdown (tick-md).

  • Works in 9 steps: User Asks You to Do Something → User Asks About Project Status → Coordination with Other Agents → …
  • Coordinating work across avatars
  • SKILL.md covers Installation, Core Concept, Quick Start and Common Workflows, plus 3 more sections
  • Calls bash, pnpm and npm; needs TICK_SYNC_KEY

What it does

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.

When your agent uses it

  • Coordinating work across avatars
  • Tracking dependencies
  • Running multi-agent workflows with TICK.md files

Example prompts

  • “/tick-coord”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. User Asks You to Do Something
  2. User Asks About Project Status
  3. Coordination with Other Agents
  4. Breaking Down Complex Work
  5. Natural Conversation First
  6. Always Use Your Agent Name
  7. Provide Context in Comments
  8. Break Down Large Tasks
  9. Check Status Before Claiming

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • bash
    • pnpm
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • npmjs.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • TICK_SYNC_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,281 words, ~4,901 tokens.

Download SKILL.mdSave it as .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.
name
tick-coord
description
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.
license
MIT

Tick Multi-Agent Coordination

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

Installation

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:

bash
# Verify CLI is available
tick --version

# Check if TICK.md exists in project
ls TICK.md

# If not, initialize
tick init

Core Concept

Tick Protocol = Git-based task coordination via TICK.md files

  • Human-readable: Standard Markdown with YAML
  • Machine-parseable: Structured for tools
  • Git-backed: Full version control and audit trail
  • Local-first: No cloud required

Quick Start

Check if Tick is initialized
bash
ls TICK.md
If not initialized
bash
tick init
Get current status
bash
tick status

Common Workflows

1. User Asks You to Do Something

User: "Can you refactor the authentication system?"

Your Actions:

bash
# 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-name
2. User Asks About Project Status

User: "What tasks are we working on?"

bash
# Get comprehensive status
tick status

# Or filter and list tasks
tick list --status in_progress
tick list --claimed-by @bot-name

Summarize the output naturally for the user.

3. Coordination with Other Agents

User: "Have the other agents finished their tasks?"

bash
# Check overall status
tick status

# List agents and their work
tick agent list --verbose

# Validate the project
tick validate
4. Breaking Down Complex Work

User: "Build a user dashboard with charts and data export"

Your Actions:

bash
# 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 graph

Command Reference

Project Management
bash
tick 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 git
Task Operations
bash
tick 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_progress
Corrections & Recovery
bash
tick 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 undone
Bulk Operations
bash
tick 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 changes
Advanced Task Listing
bash
tick 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 scripts
Dependency Visualization
bash
tick graph                         # ASCII dependency tree
tick graph --format mermaid        # Mermaid flowchart
tick graph --show-done             # Include completed tasks
Real-time Monitoring
bash
tick watch                         # Watch for changes
tick watch --interval 10           # Custom polling interval
tick watch --filter in_progress    # Only show specific status
Agent Management
bash
tick 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 status

MCP Tools (Alternative to CLI)

If using Model Context Protocol, use these tools instead of CLI commands:

Status and Inspection
  • tick_status - Get project status (agents, tasks, progress)
  • tick_validate - Validate TICK.md structure
  • tick_agent_list - List agents with optional filters
Task Management
  • tick_add - Create new task
  • tick_claim - Claim task for agent
  • tick_release - Release claimed task
  • tick_done - Complete task (auto-unblocks dependents)
  • tick_comment - Add note to task
Corrections & Recovery
  • tick_reopen - Reopen completed task
  • tick_delete - Delete a task
  • tick_edit - Direct field edit (bypasses state machine)
  • tick_undo - Undo last tick operation
Agent Operations
  • tick_agent_register - Register new agent

MCP Example:

javascript
// 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"
})

Best Practices

1. Natural Conversation First

✅ Good: User says "refactor the auth", you create task automatically ❌ Bad: Making user explicitly create tasks

2. Always Use Your Agent Name

Register once:

bash
tick agent register @your-bot-name --type bot --roles "engineer"

Then use consistently:

bash
tick claim TASK-001 @your-bot-name
tick done TASK-001 @your-bot-name
3. Provide Context in Comments
bash
# ✅ 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"
4. Break Down Large Tasks

Create subtasks with dependencies:

bash
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
5. Check Status Before Claiming
bash
# Make sure task exists and isn't claimed
tick status

# Then claim
tick claim TASK-XXX @your-name

Understanding TICK.md Structure

The file has three sections:

  1. Frontmatter (YAML): Project metadata
  2. Agents Table (Markdown): Who's working on what
  3. Task Blocks (YAML + Markdown): Individual tasks with history

Example:

markdown
---
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...

Advanced Features

Automatic Dependency Unblocking

When you complete a task, dependent tasks automatically unblock:

bash
# TASK-002 depends on TASK-001
# TASK-002 status: blocked

tick done TASK-001 @bot
# TASK-002 automatically changes to: todo
Circular Dependency Detection

Validation catches circular dependencies:

bash
tick validate
# Error: Circular dependency detected: TASK-001 → TASK-002 → TASK-003 → TASK-001
Smart Commit Messages
bash
tick sync --push
# Automatically generates: "feat: complete TASK-001, TASK-002; update TASK-003"
Reopening Completed Tasks

If a task was marked done prematurely:

bash
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
Fixing Mistakes
bash
# 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 urgent
Batch Operations

For multiple changes without individual commits:

bash
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 changes
Real-time Monitoring
bash
tick 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 → done

Quick Reference Card

Workflow:      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 --push

Key Reminders

  1. Users interact with YOU, not with Tick directly
  2. YOU maintain the TICK.md transparently
  3. Dashboard is for inspection, not primary interaction
  4. Always use your agent name consistently
  5. Comment frequently to show progress
  6. Validate before syncing
  7. Check status before claiming
  8. Break down complex work into subtasks

Project Board (Web Dashboard)

The 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.

Launch Project Board

When the user says "launch project board", "launch kanban", "show me the board", "open dashboard", or similar:

bash
# 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" stop

Default port is 3000. Override with TICK_BOARD_PORT=8080.

The board fetches live data from the Convex deployment and auto-refreshes every 30 seconds.

Running the Dev Server (Important)

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:

bash
# 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.0

Always use the script or the setsid pattern. Never run the dev server as a foreground exec command.

Accessing the Dashboard

The dev server binds to 0.0.0.0, making it available on all network interfaces:

Access methodURLWhen to use
Localhttp://localhost:3000/Same machine
LANhttp://<machine-ip>:3000/Devices on same network
Tailscalehttp://<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.

🔒 Security Notice

The dev server is a development tool with no built-in authentication or encryption. When exposing it on a network:

  • LAN access exposes the dashboard to anyone on your local network
  • Tailscale is the recommended remote access method (encrypted, authenticated by default)
  • Do not expose the dev server to the public internet (no port forwarding, no 0.0.0.0 on public-facing machines without a reverse proxy + auth)
  • The dashboard is read-only (no write operations), but task data may contain sensitive project information
  • For production/team use, deploy to Cloudflare Pages (or similar) with proper auth instead of running the dev server

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.

Show full SKILL.md (499 more words)Show less
Syncing Tasks to the Dashboard

After adding/updating tasks in TICK.md, sync to Convex so the dashboard reflects current state:

bash
CONVEX_SITE_URL=https://<your-convex-deployment>.convex.site \
TICK_SYNC_KEY=<your-sync-key> \
bash "$SKILL_DIR/scripts/tick-sync.sh"
Dashboard Features
  • Project list with task counts
  • Kanban board with status columns (Backlog → Todo → In Progress → Review → Done)
  • Task detail slide-out with full history timeline
  • Priority and tag filters
  • Regen/Dark/Light theme toggle
  • Auto-refresh every 30s

Resources


Tag Conventions

For multi-agent setups, use structured tag conventions to enable domain ownership and project tracking:

  • Project tags: project:<name> — group tickets under efforts
  • Category tags: category:<type> — classify by domain (tech, product, marketing, sales, founder, community, ops)

See docs/tag-conventions.md for full details, usage examples, and migration guide.


Multi-Avatar Coordination (OpenClaw)

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.

Agent Identity

Each avatar uses a consistent @agent-name for all tick operations. This is set per-avatar in their workspace:

  • Register on first use: tick agent register @your-name --type bot --roles "your,roles"
  • Use the same @name in every command: tick claim TASK-XXX @your-name
  • Never use another avatar's name

If your workspace has TICK_AGENT_ID set in environment or defined in AGENTS.md, use that as your identity.

TICK.md Location

Each project has its own TICK.md in its root directory. Before running tick commands, cd into the correct project:

bash
cd ~/path/to/project && tick status

If TICK.md doesn't exist yet, initialize: tick init

Handoff Protocol

When you complete a task that unblocks work for another avatar:

  1. Complete your task with a descriptive comment:

    bash
    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."
  2. The completing agent's comment should include:

    • What was done (brief summary)
    • Any decisions made and why
    • What the next avatar needs to know to pick up dependent work
  3. Dependent tasks auto-unblock when blockers complete. The next avatar checks:

    bash
    tick list --status todo --assigned-to @their-name
Orchestrator Pattern (CEO → Specialist)

The main/CEO avatar delegates work by:

  1. Creating tasks with assignments:

    bash
    tick add "Design database schema" --priority high --assigned-to @cto --tags engineering
  2. Spawning the specialist via OpenClaw:

    sessions_spawn(agentId: "cto", task: "Check TICK.md for assigned tasks. Claim, complete, and comment on each.")
  3. The specialist avatar:

    • Runs tick list --assigned-to @cto to find work
    • Claims each task before starting
    • Comments with progress on longer tasks
    • Marks done when complete
    • Its completion summary announces back to the orchestrator's session
  4. The orchestrator checks results:

    bash
    tick status
Conflict Prevention
  • OpenClaw serializes agent sessions (maxConcurrent controls parallelism)
  • tick-md uses file locking (.tick/lock) to prevent simultaneous writes
  • If a lock conflict occurs, retry after a brief pause
  • Use tick validate to check for structural issues after any unexpected state
What NOT to Do
  • Don't claim tasks assigned to other avatars without explicit delegation
  • Don't modify another avatar's comments or history
  • Don't run tick init in a project that already has TICK.md
  • Don't skip the comment when completing — future context depends on it

License

MIT

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/tick-coord of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • _meta.json
  • skill.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

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.

Tick Coord compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tick Coord this skillLeoYeAI/openclaw-master-skills2.2k—~4.9kAutomated safety check: PassMIT
Huashu Agent Swarmalchaincyf/huashu-skills1.7k1 repos~576Automated safety check: PassMIT
Foremergenaw103/foremerge537—~2.4kAutomated safety check: PassApache-2.0
Puppetmaster Agent Orchestrationprofessorpalmer/Puppetmaster467—~3.2kAutomated safety check: PassMIT
Agtx Task Sweepfynnfluegge/agtx1.7k—~1.7kAutomated safety check: PassApache-2.0
Cas Supervisorcodingagentsystem/cas176—~1.8kAutomated safety check: PassMIT

Similar skills

  • Huashu Agent Swarm

    alchaincyf/huashu-skills

    多Agent蜂群并行协作,纯git自组织,适合大型项目开发。当用户提到"蜂群模式"、"多agent"、"并行开发"、"agent swarm"时使用。

    1.7k GitHub starsUsed in 1 repo~576 tokens
    Agent WorkflowsAuto-check passed
  • Foremerge

    naw103/foremerge

    Coordinate parallel coding agents with Foremerge's local Git-compatible CLI and MCP server.

    537 GitHub stars~2.4k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed
  • Puppetmaster Agent Orchestration

    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.

    467 GitHub stars~3.2k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agtx Task Sweep

    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.

    1.7k GitHub stars~1.7k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Cas Supervisor

    codingagentsystem/cas

    Factory supervisor guide for multi-agent EPIC orchestration.

    176 GitHub stars~1.8k tokensUpdated 7 mo ago
    Agent WorkflowsAuto-check passed
  • Run Wave

    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.

    207 GitHub stars~4.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 972 skills in this repo
  • DevOps Pipeline Management

    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.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    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.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    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.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    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.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    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.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    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.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Tick Coord

What does Tick Coord do?

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).

When should I use Tick Coord?

Tick Coord fits situations like: coordinating work across avatars; tracking dependencies; running multi-agent workflows with TICK.md files.

How do I install Tick Coord in Claude Code?

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.

How do I install Tick Coord in Codex?

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.

Can I use Tick Coord in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Tick Coord need to run?

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.

Does Tick Coord access the network?

SKILL.md names 2 domains. As links in the text: npmjs.com and github.com. This is read from the text; nothing was executed.

Is Tick Coord safe to install?

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.

What licence does Tick Coord use?

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.

How many tokens does Tick Coord use?

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.

What are the alternatives to Tick Coord?

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.

Who maintains Tick Coord?

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.