clawlist

MUST use for any multi-step project, long-running task, or infinite monitoring workflow. Plan, execute, track, and verify tasks with checkpoint validation. For projects, automation, and ongoing operations.

Security Scan

The skill's files and runtime instructions are coherent with its stated purpose (planning, executing, tracking long-running and infinite tasks) but there are minor omissions and operational risks you should understand before enabling it.

Purpose & Capability

Name/description match the actual instructions: the skill orchestrates brainstorming → plan → execute → verify and manages long-running/infinite tasks. However, the SKILL.md repeatedly refers to persistent agent memory files (e.g., memory/tasks/ongoing-tasks.md, memory/plans/...) and to platform features (heartbeat, sessions_spawn) while the skill metadata declares no required config paths or platform permissions. That omission is an inconsistency to be aware of.

Instruction Scope

Instructions tell the agent to read project state (files, docs, commits), write and update persistent memory files, spawn subagents, and let a heartbeat process read ongoing-tasks.md to execute due tasks. All of that is in-scope for a task-orchestration skill, but it does mean the agent will access and persist project data and may act repeatedly over time—so check whether you want those filesystem/memory operations and any automated dispatching of subagents.

Install Mechanism

Instruction-only skill with no install spec or code files to run. Lowest-risk install surface—nothing is downloaded or written by an installer.

Credentials

The skill requests no environment variables or external credentials, which is proportional to its stated purpose. Note: it implicitly relies on the agent's persistent memory and platform features (heartbeat, session spawning) but does not request additional secrets.

Persistence & Privilege

The skill is not force-included (always:false) but is designed for long-running and infinite tasks and instructs the agent to update persistent memory and rely on a heartbeat to execute tasks. Autonomous invocation is allowed (disable-model-invocation:false) — typical for skills, but because this one is intended to schedule/drive repeated actions and spawn subagents, it raises operational risk if you don't want ongoing automated behavior.

Assessment

This skill appears to do what it says: orchestrate multi-step and long-running workflows. Before installing, consider: 1) The skill reads and writes agent memory files (memory/tasks/ongoing-tasks.md, memory/plans/...), but the metadata doesn't declare those config paths — confirm your platform's memory policy and whether you consent to those persistent writes. 2) It expects to spawn subagents and rely on a heartbeat to run recurring tasks; if you don't want autonomous or frequent background actions, do not enable autonomous invocation or set limits. 3) Because it can read project files and commits, avoid using it on repositories containing secrets unless you trust its behavior and storage. 4) Test with a non-sensitive project first, monitor the agent's actions and memory writes, and set explicit boundaries (frequency, scope, and allowed outputs) for infinite/long-running tasks.

Clawlist - Task Mastery

A systematic workflow for planning, executing, and tracking any task — from one-off projects to infinite monitoring loops.

When to Use This Skill

ALWAYS use clawlist when:

• Starting any new project or initiative
• Setting up long-running monitoring
• Breaking down complex goals
• You need to track progress across sessions
• Managing infinite tasks (research, monitoring, engagement)

Long-Running & Infinite Task Examples

Example: Moltbook Engagement (Infinite)

• Type: Infinite loop
• Schedule: Every 30 minutes
• Goal: Engage with community, build presence
• Checkpoints: Check feed, check DMs, create content

Example: GitHub Monitoring (Long-Running)

• Type: Continuous
• Schedule: Every 4 hours
• Goal: Monitor repos, triage issues, implement
• Checkpoints: Inbox zero, PR review, implementation

The Clawlist Workflow

Uses standalone skills in sequence:

1. brainstorming → Clarify intent, explore approaches
2. write-plan → Create detailed plan with checkpoints
3. doing-tasks → Execute with skill discipline
4. verify-task → Confirm completion

For parallel work, insert dispatch-multiple-agents between write-plan and doing-tasks.

Ongoing Tasks File

Location: memory/tasks/ongoing-tasks.md

Tracks all long-running and infinite tasks. Updated by heartbeat to:

• Check task health
• Detect blockers
• Execute due tasks
• Summarize status

Task Types

Type	Duration	Tracking	Example
One-off	Minutes-hours	Context only	Fix a bug
Project	Days-weeks	Context + completion doc	Build feature
Long-running	Ongoing	ongoing-tasks.md	GitHub monitoring
Infinite	Forever	ongoing-tasks.md	Moltbook engagement

Integration with Heartbeat

Heartbeat reads ongoing-tasks.md every check to:

• Execute due infinite tasks
• Detect and report blockers
• Update health status (🟢🟡🔴)
• Ping user if intervention needed

Quick Reference

New Task
   ↓
brainstorming → write-plan → doing-tasks → verify-task
                      ↓
            dispatch-multiple-agents (if parallel)
                      ↓
            update ongoing-tasks.md (if long-running)

Sub-Skills

• brainstorming - Phase 1: Clarify
• write-plan - Phase 2: Plan
• doing-tasks - Phase 3: Execute
• dispatch-multiple-agents - Parallel execution
• verify-task - Phase 4: Verify