New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tide Watch

by LeoYeAI in LeoYeAI/openclaw-master-skills

Proactive session capacity monitoring and management for OpenClaw.

MITAuto-check passedAgent Workflows

Install Tide Watch

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill tide-watch -a claude-code

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

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills tide-watch --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/tide-watch .claude/skills/tide-watch && 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
tide-watch
GitHub stars
2.2k
Token cost
~4.6k tokens
SKILL.md length
1,694 words
Files
53
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Proactive session capacity monitoring and management for OpenClaw.

  • Works in 3 steps: Add Monitoring Directive to AGENTS.md → Add Heartbeat Task to HEARTBEAT.md → Configure Settings (Optional)
  • Working on long-running projects
  • SKILL.md covers ⚠️ Security & Architecture…, What It Does, Installation and Usage, plus 5 more sections
  • Calls npm and git

What it does

Tide Watch is an agent skill from LeoYeAI/openclaw-master-skills. Proactive session capacity monitoring and management for OpenClaw. Prevents context window lockups by warning at configurable thresholds (75%, 85%, 90%, 95%), automatically backing up sessions before resets, and managing session resumption prompts. Use when working on long-running projects, managing multiple conversation channels (Discord, Telegram, webchat), or preventing lost work from full context windows. Includes CLI tools for capacity checks, cross-session dashboards, archive management, and session…

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 52 other files (for example `CHANGELOG.md`, `CLAWHUB-SCANNER-RESPONSE.md` and `INSTALLATION.md`).

It sits in Agent Workflows, covering Context engineering and Session handoff. It works with Discord, Telegram and Node.js. 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

  • Working on long-running projects
  • Managing multiple conversation channels (Discord
  • Preventing lost work from full context windows

Example prompts

  • “/tide-watch”

Requirements

  • Node.js

Workflow steps

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

  1. Add Monitoring Directive to AGENTS.md
  2. Add Heartbeat Task to HEARTBEAT.md
  3. Configure Settings (Optional)

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:

    • npm
    • git

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

    • github.com
    • clawhub.ai

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

  • Credentials

    Names no API keys, tokens, secrets or passwords.

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

Context cost

Tide Watch loads about 4.6k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 1,694 words of instructions outside code blocks.

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

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,694 words, ~4,552 tokens.

Download SKILL.mdSave it as .claude/skills/tide-watch/SKILL.md (or your agent's skills folder). This skill also uses 52 other files; get the full folder from GitHub.
name
tide-watch
description
Proactive session capacity monitoring and management for OpenClaw. Prevents context window lockups by warning at configurable thresholds (75%, 85%, 90%, 95%), automatically backing up sessions before resets, and managing session resumption prompts. Use when working on long-running projects, managing multiple conversation channels (Discord, Telegram, webchat), or preventing lost work from full context windows. Includes CLI tools for capacity checks, cross-session dashboards, archive management, and session resumption. Supports any model or provider.
author
Chris Giddings
homepage
https://github.com/chrisagiddings/openclaw-tide-watch
repository
https://github.com/chrisagiddings/openclaw-tide-watch

Tide Watch 🌊

Proactive session capacity monitoring for OpenClaw.

⚠️ Security & Architecture Notice

Tide Watch is a HYBRID SKILL with two operational modes:

Description: AGENTS.md and HEARTBEAT.md directives only
Code Execution: NONE - Uses OpenClaw's built-in tools only (no CLI installation)
File Access: Reads OpenClaw session files via agent's built-in tools
Installation: Copy template directives to workspace config files
Security: Lowest risk - no code installation or execution required

What it does:

  • ✅ Monitors session capacity via session_status tool
  • ✅ Warns at thresholds (75%, 85%, 90%, 95%)
  • ✅ Auto-loads resumption prompts on session reset
  • ✅ All operations through OpenClaw's native tools
Mode 2: CLI Tools (Optional)

Description: Node.js command-line tools for manual management
Code Execution: YES - Executable JavaScript code
File Access: Direct read/write to ~/.openclaw/agents/main/sessions/
Installation: git clone + npm link (requires Node.js)
Security: Moderate risk - requires code inspection before install

What it does:

  • CLI commands: tide-watch status, tide-watch dashboard, etc.
  • Manual capacity checks
  • Session archive management
  • Resumption prompt editing (⚠️ see CVE-2026-001 below)
Mode Comparison
FeatureDirectives-OnlyCLI Tools
Node.js required?❌ No✅ Yes (14+)
InstallationCopy templatesnpm link
Code execution❌ None✅ JavaScript
File accessVia built-in toolsDirect filesystem
Security riskLowestModerate
Use casePassive monitoringActive management

Choose Directives-Only if: You only need capacity warnings and resumption prompts.
Choose CLI Tools if: You need manual session management, archiving, or dashboard views.

🚨 CRITICAL SECURITY NOTICE: CVE-2026-001

Vulnerability: Shell injection in editResumePrompt function
Affected Version: v1.0.0 ONLY
Current Version: v1.0.1 (PATCHED)
Severity: HIGH (CVSS 7.8)
Status: ✅ FIXED

Summary: v1.0.0 contained a shell injection vulnerability in the CLI's resume-prompt edit command. An attacker who could control the --session parameter could execute arbitrary commands. This has been fixed in v1.0.1 by replacing execSync with spawnSync.

If you installed v1.0.0: Update immediately to v1.0.1.

Full disclosure: See SECURITY-ADVISORY-CVE-2026-001.md

Security Best Practices

For Directives-Only Mode (Safest):

  1. ✅ Copy AGENTS.md.template and HEARTBEAT.md.template to workspace
  2. ✅ No code installation required
  3. ✅ No npm dependencies
  4. ✅ Lowest security surface

For CLI Tools Mode (If Needed):

  1. ⚠️ Verify version 1.0.1 or later (tide-watch --version)
  2. ⚠️ Inspect code before installing:
    • Review lib/capacity.js and lib/resumption.js
    • Check package.json for install hooks (should have none)
    • Run npm test to verify behavior (113 tests)
  3. ⚠️ Only use UUID session IDs with --session flag
  4. ⚠️ Avoid untrusted input to CLI commands
  5. ⚠️ Review backups location (~/.openclaw/agents/main/sessions/archive/)

Operation Types:

Read-Only Operations (✅ Safe, no modifications):

  • tide-watch status - Check current session count
  • tide-watch check --session <id> - View specific session capacity
  • tide-watch check --current - Auto-detect and check current session (v1.3.4+)
  • tide-watch dashboard - Visual capacity overview
  • tide-watch dashboard --watch - Live updating dashboard
  • tide-watch dashboard --raw-size - Show full precision token counts (v1.3.2+)
  • tide-watch report - List sessions above threshold
  • tide-watch resume-prompt show --session <id> - View resumption prompt

Modifying Operations (⚠️ Moves/creates files):

  • tide-watch archive --older-than <time> - Moves sessions to archive/ (time-based)
  • tide-watch archive --session <id> - Archive specific session (v1.3.3+)
  • tide-watch archive --session <id1> --session <id2> - Archive multiple sessions (v1.3.3+)
  • tide-watch resume-prompt edit --session <id> - Opens editor (CVE patched in v1.0.1)
  • tide-watch resume-prompt delete --session <id> - Deletes resumption prompt file

New Flags (v1.3.2+):

  • --raw-size - Show full precision token counts (e.g., 18,713/128,000 instead of 18.7k/128k)
  • --current - Auto-detect current session via OPENCLAW_SESSION_ID environment variable (v1.3.4+)
  • --session (enhanced) - Supports partial IDs, multiple sessions for archive, labels/channels (v1.3.3+)

File System Access:

  • Reads: ~/.openclaw/agents/main/sessions/*.jsonl (session data)
  • Writes: ~/.openclaw/agents/main/sessions/resume-prompts/*.md (resumption prompts)
  • Moves: ~/.openclaw/agents/main/sessions/archive/ (archived sessions)

Network Activity: NONE - All operations are local filesystem only.

CLI Reference

Complete flag and option documentation:

Display Options:

  • --raw-size - Show full precision token counts with commas (v1.3.2+)

    • Default: Human-readable (e.g., 18.7k/128k, 20.6k/1M)
    • With flag: Full precision (e.g., 18,713/128,000, 20,631/1,000,000)
    • Use case: When exact token counts needed
    • Example: tide-watch dashboard --raw-size

  • --json - Output as JSON instead of formatted table

    • Example: tide-watch check --session abc123 --json
    • Useful for scripting and parsing

  • --pretty - Pretty-print JSON output (requires --json)

    • Example: tide-watch report --json --pretty

Session Selection:

  • --session <key> - Target specific session (enhanced in v1.3.3+)

    • Full UUID: --session 17290631-42fe-40c0-bd23-c5da511c6f7b
    • Partial UUID: --session 17290631-4 (v1.3.3+)
    • Label: --session "#navi-code-yatta" (v1.3.3+)
    • Channel: --session discord (v1.3.3+)
    • Channel + label: --session "discord/#navi-code" (v1.3.3+)
    • Multiple (archive only): --session abc123 --session def456 (v1.3.3+)

  • --current - Auto-detect current session (v1.3.4+)

    • Requires: OPENCLAW_SESSION_ID environment variable
    • Example: tide-watch check --current
    • Use case: Heartbeat monitoring (check THIS session)
    • Fallback: Graceful error with helpful message if env var not set

Filtering:

  • --all - Show all sessions regardless of capacity
  • --threshold <num> - Filter sessions above percentage (default: 75)
  • --active <hours> - Only show sessions active within N hours
  • --agent <id> - Filter to specific agent (multi-agent setups)
  • --exclude-agent <id> - Exclude specific agent (can use multiple times)

Archive Options:

  • --older-than <time> - Archive sessions older than time

    • Examples: 4d, 2w, 1mo, 3months
    • Mutually exclusive with --session

  • --dry-run - Preview archive without making changes

    • Example: tide-watch archive --older-than 7d --dry-run

  • --exclude-channel <name> - Exclude channel from archiving

    • Example: tide-watch archive --older-than 30d --exclude-channel discord

  • --min-capacity <num> - Only archive sessions below capacity threshold

    • Example: tide-watch archive --older-than 7d --min-capacity 50

Live Monitoring:

  • --watch - Live updating dashboard (refreshes every 10s)
    • Example: tide-watch dashboard --watch
    • Press Ctrl+C to exit

Multi-Agent:

  • --all-agents - Multi-agent discovery mode (default, auto-discovers agents)
  • --single-agent-only - Single-agent mode (main agent only)

Configuration Override:

  • --refresh-interval <seconds> - Dashboard refresh interval (1-300)
  • --gateway-interval <seconds> - Gateway status check interval (5-600)
  • --gateway-timeout <seconds> - Gateway command timeout (1-30)
  • --session-dir <path> - Custom session directory

Usage Examples:

bash
# Human-readable vs full precision
tide-watch dashboard                    # 18.7k/128k (easy to scan)
tide-watch dashboard --raw-size         # 18,713/128,000 (exact)

# Auto-detect current session (v1.3.4+)
export OPENCLAW_SESSION_ID="17290631-4"
tide-watch check --current              # Check THIS session
tide-watch check --current --json       # JSON for heartbeat scripts

# Session-specific archiving (v1.3.3+)
tide-watch archive --session abc123 --dry-run    # Preview
tide-watch archive --session abc123              # Archive one
tide-watch archive --session a --session b       # Archive multiple

# Partial ID matching (v1.3.3+)
tide-watch check --session 17290631-4   # Matches 17290631-42fe-40c0-...

# Multi-agent filtering
tide-watch dashboard --agent kintaro    # Kintaro sessions only
tide-watch report --exclude-agent main  # All except main
Runtime Requirements

Mode 1 (Directives-Only):

  • Node.js: Not required
  • npm: Not required
  • Dependencies: None
  • Binary: None
  • Installation: Copy templates to workspace config files

Mode 2 (CLI Tools - Optional):

  • Node.js: v14.0.0 or later required
  • npm: Any recent version
  • Dependencies:
    • Development: jest@^30.2.0 (for testing only)
    • Runtime: None (zero production dependencies)
  • Binary: tide-watch (installed globally via npm link)
  • Installation: git clone + npm link

Why zero runtime dependencies?

  • Uses only Node.js built-in modules (fs, path, child_process)
  • No external API clients
  • No network libraries
  • Minimal attack surface
Recommendation

Most users should use Directives-Only Mode. This provides automatic capacity monitoring without installing any code. Only install CLI tools if you specifically need manual capacity management features.

What It Does

Monitors your OpenClaw session context windows and warns you before they overflow:

  • 🟡 75% — Heads up, consider wrapping up soon
  • 🟠 85% — Recommend finishing current task and resetting
  • 🔴 90% — Session will lock soon, ready to reset
  • 🚨 95% — Critical! Save to memory NOW

Installation

Show full SKILL.md (686 more words)Show less
Step 1: Add Monitoring Directive to AGENTS.md

Copy the directive template from AGENTS.md.template and add it to your workspace AGENTS.md file:

bash
# From your workspace root (~/clawd or similar)
cat skills/tide-watch/AGENTS.md.template >> AGENTS.md

Or manually add the monitoring section from the template.

This tells me (your agent) what to look for and when to warn you.

Step 2: Add Heartbeat Task to HEARTBEAT.md

Copy the heartbeat template from HEARTBEAT.md.template and add it to your workspace HEARTBEAT.md file:

bash
# From your workspace root (~/clawd or similar)
cat skills/tide-watch/HEARTBEAT.md.template >> HEARTBEAT.md

Or manually add the Tide Watch heartbeat section from the template.

This tells me to check capacity automatically on a schedule.

Step 3: Configure Settings (Optional)

Default settings work for most users, but you can customize in your AGENTS.md:

Warning thresholds (when to warn):

  • Adjust percentages (default: 75/85/90/95)
  • Range: 50-99%, ascending order, 2-6 thresholds

Check frequency (how often to monitor):

  • Adjust interval (default: Every 1 hour)
  • Options: 15min, 30min, 1hr, 2hr, or 'manual'
  • Range: 5 minutes to 6 hours

Auto-backup:

  • Enable/disable automatic backups (default: enabled)
  • Set which thresholds trigger backups (default: [90, 95])
  • Configure retention (default: 7 days)
  • Enable compression to save disk space (default: off)

Channel-specific overrides (advanced):

  • Different settings per channel (Discord vs. webchat vs. DM)

Usage

Once installed, I will:

  1. Check capacity hourly during active conversations
  2. Warn at thresholds (75%, 85%, 90%, 95%)
  3. Suggest actions:
    • Save important context to memory
    • Switch to lower-usage channels
    • Provide session reset commands
    • Generate session resumption prompts
Manual Check

Ask me to check session status anytime:

What's my current session capacity?
Check context usage
Run session_status
Reset Session with Context Preservation

When warned about high capacity:

Help me reset this session and preserve context

I'll:

  1. Save current work to memory
  2. Backup the session file (if not already backed up)
  3. Provide a session resumption prompt
  4. Reset the session
Load Session from Backup

If you need to load a previous session state from backup:

Show me available backups for this session
Load session from 90% backup

I'll:

  1. List available backups with timestamps and sizes
  2. Load the selected backup
  3. Guide you through reconnecting to load the session

Backup locations:

  • Path: ~/.openclaw/agents/main/sessions/backups/
  • Format: <session-id>-<threshold>-<timestamp>.jsonl[.gz]
  • Retention: Configurable (default: 7 days)

How It Works

Automatic Monitoring (Heartbeat)

When you add Tide Watch to your HEARTBEAT.md, I automatically:

  1. Parse your configuration (from AGENTS.md)

    • Check frequency: How often to monitor
    • Warning thresholds: When to warn you
    • Backup settings: When to backup, retention, compression
    • See PARSING.md for detailed parsing logic

  2. Check capacity on schedule (default: every hour)

    • Run session_status to get token usage
    • Calculate percentage: (tokens_used / tokens_max) * 100

  3. Compare against your thresholds

    • Use your configured thresholds (not hardcoded defaults)
    • Determine which threshold(s) have been crossed
    • Assign severity dynamically based on position (first=🟡, last=🚨)

  4. Warn you (once per threshold)

    • Issue warning message for new threshold crossings
    • Track which thresholds already warned this session
    • Don't repeat warnings if capacity stays at same level

  5. Auto-backup (if enabled and triggered)

    • Check if capacity crossed any backup trigger thresholds
    • Create backup: ~/.openclaw/agents/main/sessions/backups/<session-id>-<threshold>-<timestamp>.jsonl
    • Verify backup integrity
    • Log backup completion
    • Track which thresholds backed up (don't duplicate)

  6. Suggest actions

    • Save context to memory
    • Switch to lower-usage channel
    • Provide session reset commands
    • Generate session resumption prompts

  7. Cleanup old backups

    • Remove backups older than retention period (default: 7 days)

  8. Return to silent mode

    • If capacity is below all thresholds, return HEARTBEAT_OK
    • No output, no interruption
Manual Checks

You can also ask me to check anytime:

What's my current session capacity?
Check context usage
Run session_status
Key Features
  • Model-agnostic: Works with any provider (Anthropic, OpenAI, DeepSeek, etc.)
  • Non-intrusive: Silent checks, only speaks up at thresholds
  • Configurable: Adjust thresholds, frequency, and actions to your workflow
  • Stateful: Tracks which thresholds warned, resets tracking when session resets

Why You Need This

Problem: Context windows fill up silently. Once at 100%, sessions lock and stop responding. You lose work mid-task.

Solution: Proactive monitoring catches capacity issues early, giving you time to save work, switch channels, or reset cleanly.

Real incident: Discord #navi-code-yatta hit 97% capacity and locked mid-task (2026-02-23). Had to manually reset, losing conversation context.

Configuration Examples

Conservative (early warnings)
markdown
Warning thresholds: 60%, 70%, 80%, 90%
Check frequency: Every 30 minutes
Aggressive (maximize usage)
markdown
Warning thresholds: 85%, 92%, 96%, 98%
Check frequency: Every 2 hours
Channel-specific
markdown
Discord channels: 75%, 85%, 90%, 95% (default)
Webchat: 85%, 95% (lighter warnings)
DM: 90%, 95% (minimal warnings)

Future Features

  • CLI tool for capacity reports
  • Automatic session backups at thresholds
  • Historical capacity tracking
  • Cross-session capacity reports
  • Integration with heartbeat monitoring
  • Email/notification warnings
  • Smart session rotation suggestions

Requirements

  • OpenClaw with session_status tool support
  • Workspace with AGENTS.md file
  • Active monitoring directive in agent instructions

Support

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 52 other files in skills/tide-watch of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • CHANGELOG.md
  • CLAWHUB-SCANNER-RESPONSE.md
  • INSTALLATION.md
  • PARSING.md
  • README.md
  • RESEARCH-ANYBINS-PATTERN.md
  • SECURITY-ADVISORY-CVE-2026-001.md
  • SECURITY-ANALYSIS.md
  • SECURITY-ASSESSMENT-ISSUE-35.md
  • SECURITY-ASSESSMENT-ISSUE-36.md
  • SECURITY-ASSESSMENT-v1.1.0.md
  • SECURITY-ASSESSMENT-v1.1.2.md
  • SECURITY-ASSESSMENT-v1.1.3.md
  • SECURITY-ASSESSMENT-v1.1.4.md
  • SECURITY-ASSESSMENT-v1.1.5.md
  • SECURITY-ASSESSMENT-v1.1.6.md
  • SECURITY-ASSESSMENT-v1.2.0.md
  • SECURITY-ASSESSMENT-v1.2.1.md
  • SECURITY-ASSESSMENT-v1.3.0.md
  • SECURITY-ASSESSMENT-v1.3.2.md
  • … and 32 more

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Tide Watch 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.

Tide Watch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tide Watch this skillLeoYeAI/openclaw-master-skills2.2k—~4.6kAutomated safety check: PassMIT
Better Notifybetter-notify/better-notify313—~783Automated safety check: PassMIT
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence
Session Handoff Documentthedotmack/claude-mem99k—~1.4kAutomated safety check: PassApache-2.0
Planning with FilesOthmanAdi/planning-with-files27k—~2.9kAutomated safety check: PassMIT
Context RecoverySakuraByteCore/codexmate354—~964Automated safety check: PassApache-2.0

Similar skills

  • Better Notify

    better-notify/better-notify

    End-to-end typed notification infrastructure for Node.js — typed catalog of email, SMS, push, web push, WhatsApp, Slack, Discord, Telegram, and GitHub notifications with provider-agnostic transports.

    313 GitHub stars~783 tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed

  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check: notes

  • Session Handoff Document

    thedotmack/claude-mem

    Writes a HANDOFF.md capturing goal, state, files, failed attempts and next steps so a fresh agent session can continue exactly where this one stopped.

    99k GitHub stars~1.4k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check passed

  • Planning with Files

    OthmanAdi/planning-with-files

    Keeps a task plan, findings and progress log in markdown files on disk so long agent tasks survive context resets, with Gemini hooks and helper scripts.

    27k GitHub stars~2.9k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Context Recovery

    SakuraByteCore/codexmate

    Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions.

    354 GitHub stars~964 tokensUpdated today
    Agent WorkflowsAuto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Agent WorkflowsAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,200 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

Works with

Categories

Questions about Tide Watch

What does Tide Watch do?

Proactive session capacity monitoring and management for OpenClaw. Tide Watch is an agent skill from LeoYeAI/openclaw-master-skills. Proactive session capacity monitoring and management for OpenClaw.

When should I use Tide Watch?

Tide Watch fits situations like: working on long-running projects; managing multiple conversation channels (Discord; preventing lost work from full context windows.

How do I install Tide Watch in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill tide-watch -a claude-code`. Or copy the skill folder (skills/tide-watch in LeoYeAI/openclaw-master-skills) into .claude/skills/tide-watch in your project. Claude Code loads it when a task matches its description.

How do I install Tide Watch in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill tide-watch -a codex`. Or copy the skill folder (skills/tide-watch in LeoYeAI/openclaw-master-skills) into .agents/skills/tide-watch in your project. Codex loads it when a task matches its description.

Can I use Tide Watch 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 tide-watch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tide-watch, .gemini/skills/tide-watch, .github/skills/tide-watch and .opencode/skills/tide-watch in your project.

What does Tide Watch need to run?

Going by SKILL.md and its folder, Tide Watch needs the command-line tools its instructions call (npm and git). Our summary lists: Node.js.

Does Tide Watch access the network?

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

Is Tide Watch 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 Tide Watch use?

Tide Watch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tide Watch use?

About 4.6k tokens (SKILL.md is roughly 18k 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 Tide Watch?

Skills that share tags, products or a category with Tide Watch: Better Notify (better-notify/better-notify, 313 stars), Memori Long-Term Memory (MemoriLabs/Memori, 17k stars), Session Handoff Document (thedotmack/claude-mem, 99k stars) and Planning with Files (OthmanAdi/planning-with-files, 27k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tide Watch?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 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.