Longrunning Agent

Enables AI agents to work on long-running projects across multiple sessions. Use when starting complex projects, resuming work on existing projects, managing...

Security Scan

The skill's instructions mostly match a long-running workflow, but there are some mismatches and missing declarations (undeclared external dependencies and unspecified network integration) that merit user review before installing.

Purpose & Capability

The SKILL.md describes a project/workflow manager and the instructions (task.json, progress.txt, working on one task, git commits) are coherent with that purpose. However the manifest lists 'tools': ["gh"] and the README tells you to ensure the Claude Code CLI is installed — yet required binaries/env vars are empty. This mismatch between declared requirements and the instructions is unexpected.

Instruction Scope

Runtime instructions are focused on reading/writing local workflow files, optionally running an init.sh, running lint/build/tests, and making git commits — all reasonable for this purpose. The instructions also claim integration with an 'Agent Workflow Web App' (tasks sync with web database, session output logged) but provide no endpoints, credentials, or steps for that sync; that unspecified network behavior is worth flagging.

Install Mechanism

This is an instruction-only skill with no install script or downloaded code. The manifest's install destination is just a copy location. No archive downloads or third‑party packages are pulled by the skill itself.

Credentials

The skill does not request any environment variables or credentials, but the SKILL.md requires external tools (Claude Code CLI) and references syncing to a web database. If those integrations require API keys or tokens, they are not declared here — the omission reduces transparency and could lead to unexpected credential use by supporting tooling or templates.

Persistence & Privilege

The skill does not request always:true or other elevated persistence. It does not declare modifications to other skills or system-wide settings. Normal autonomous invocation is allowed (platform default).

What to consider before installing

This skill appears to implement a sensible long-running project workflow, but it has a few transparency issues you should check before installing: 1) Verify external dependencies: the SKILL.md asks you to have the Claude Code CLI configured and the manifest lists the GitHub CLI ('gh') — install and configure these yourself, and ensure you trust them. 2) Inspect any init.sh or template files before running them (they can execute arbitrary code). 3) Ask the author or inspect the referenced repository for details about the 'Agent Workflow Web App' integration — who hosts the web database, what endpoints are used, and what credentials (if any) are required. 4) Prefer skills that explicitly declare required binaries and environment variables; absence of those declarations here is the main reason for caution. If you can review the upstream repository or get confirmation about the web sync behavior and any required credentials, the risk assessment can be raised to higher confidence.

OpenClaw Long-Running Agent Skill

This skill enables AI agents to work on long-running projects across multiple sessions.

Purpose

The longrunning-agent skill provides a structured workflow for:

• Tracking progress across sessions
• Managing task lists with priorities and dependencies
• Making incremental, atomic progress on complex projects
• Ensuring continuity when resuming work

Installation

1. Copy this skill directory to your OpenClaw skills folder
2. Ensure Claude Code CLI is installed and configured
3. Create a project directory with the workflow files

Usage

Initialize a New Project

# Create project directory
mkdir my-project && cd my-project

# Initialize workflow files
claude -p "Initialize this project using the longrunning-agent workflow"

Workflow Files

The skill expects these files in the project directory:

• CLAUDE.md - Project instructions and workflow guide
• task.json - Task list with priorities and dependencies
• progress.txt - Log of work completed
• init.sh - Environment setup script (optional)

Task Format

{
  "tasks": [
    {
      "id": "task-1",
      "description": "Set up project structure",
      "priority": 1,
      "dependencies": [],
      "passes": false
    },
    {
      "id": "task-2",
      "description": "Implement core features",
      "priority": 2,
      "dependencies": ["task-1"],
      "passes": false
    }
  ]
}

Progress Format

[2024-01-15 10:30:00] Started session
[2024-01-15 10:35:00] Completed task: Set up project structure
[2024-01-15 10:40:00] Milestone: Core features implemented

Workflow Steps

1. Read Progress - Check progress.txt for recent work
2. Select Task - Find next passes: false task with met dependencies
3. Initialize - Run init.sh if needed
4. Implement - Work on one task incrementally
5. Test - Run lint, build, and tests
6. Document - Update progress.txt
7. Mark Complete - Set passes: true in task.json
8. Commit - Make atomic git commit

Best Practices

• Work on ONE task per session
• Make commits after each task completion
• Keep progress.txt concise but informative
• Use dependencies to manage task order
• Test thoroughly before marking passes: true

Integration with Web UI

This skill integrates with the Agent Workflow Web App:

• Tasks sync with the web database
• Progress entries are captured
• Session output is logged
• Git commits are tracked

Templates

Templates for workflow files are in the templates/ directory:

• CLAUDE.md.tpl - Project template
• task.json.tpl - Task list template