What makes taskforce-loop-engineering notable?

1.9K downloads. Trust evidence available

How should taskforce-loop-engineering be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

taskforce-loop-engineering

Durable explicit task/project loops with verification, revisions, live progress, and governed completion.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.9k

Updated

Oct 9, 2026

Version

0.15.21

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.9K downloads reported by the source. Last updated 10/9/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 9, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 9, 2026
Adoption signal: 1.9K downloadsadoption · observed Oct 9, 2026
Latest release: 0.15.21release · observed Sep 30, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s176403v6056szwqp2hd324dpx857gdh:taskforce-loop-engineering

Install using `clawhub skill install s176403v6056szwqp2hd324dpx857gdh:taskforce-loop-engineering` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/ambitioncn/taskforce-loop-engineering before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-ambitioncn-taskforce-loop-engineering/snapshot"

Documentation

CLAWHUB

149,893 characters of source documentation, loaded on request.

Extracted files

4 files captured from the source.

SKILL.md

---
name: "taskforce-loop-engineering"
description: "Durable explicit task/project loops with verification, revisions, live progress, and governed completion."
---

# Taskforce Loop Engineering

Use this skill only when the user explicitly invokes Loop Engineering, says `走 loop`, `loop engineering`, `丢进 Ironman loop`, `loop Ironman`, `task-runner`, names a loop queue, or asks to operate an existing loop.

Do not route ordinary chat, research, explanations, or simple direct tasks into a loop unless the user explicitly invokes it.

## Distribution and CLI Installation

A skill installation may provide only this `SKILL.md`; it does **not** prove that the Loop Engineering CLI or an OpenClaw/Hermes integration is installed. Before running loop commands, check the deployment explicitly:

```bash
command -v loop-engineering
loop-engineering --help
```

Official distribution:

- npm package: `taskforce-loop-engineering`
- GitHub repository: `https://github.com/ambitioncn/taskforce-loop-engineering`
- ClawHub skill: `https://clawhub.ai/ambitioncn/skills/taskforce-loop-engineering`
- license: Apache-2.0
- runtime requirement: Node.js 22 or newer

Install the CLI globally from npm:

```bash
node --version
npm install -g taskforce-loop-engineering
loop-engineering --help
```

For a temporary read-only invocation without a global install:

```bash
npx -p taskforce-loop-engineering loop-engineering --help
```

For source-based development, clone the official repository and install its dependencies:

```bash
git clone https://github.com/ambitioncn/taskforce-loop-engineering.git
cd taskforce-loop-engineering
npm install
npm run check
node bin/loop-engineering.mjs --help
```

Do not guess a workspace source path. Use `node packages/loop-engineering/bin/loop-engineering.mjs ...` only after confirming that exact path exists in the current workspace.

### OpenClaw Integration

Installing the npm package exposes the CLI, but it does not automatically route conversations, select a worker agent, or create queue wrappers. First generate a read-only installation plan:

```bash
loop-engineering-openclaw-install \
  --root /path/to/openclaw/workspace \
  --queue agent-tasks
```

Review the installation confirmation summary before proceeding. It must show the target platform, absolute platform CLI path, workspace, queue, scheduler, notification routing, and `writes enabled: no (plan only)`. If any field identifies the wrong platform or destination, stop. Then install with an existing worker-agent id:

```bash
loop-engineering-openclaw-install \
  --root /path/to/openclaw/workspace \
  --queue agent-tasks \
  --worker-agent main \
  --confirm-install
```

The confirmed install also creates `loop-engineering-dashboard.service` on port `4174` and couples it to `openclaw-gateway.service`. Dashboard listening defaults to local-only `127.0.0.1`. To permit Tailnet clients, pass `--dashboard-listen tailscale`; the installer resolves `tailscale ip -4`, binds only that `100.x` addres

_meta.json

{
  "ownerId": "kn72t03qbte90ag4sev5yhkg1185722d",
  "slug": "taskforce-loop-engineering",
  "version": "0.15.21",
  "publishedAt": 1790788211202
}

references/npm-package.md

# npm Package

Package name: `taskforce-loop-engineering`
Version: `0.15.19`

Install from npm:

```bash
npm install -g taskforce-loop-engineering
```

Hermes Agent integration commands:

```bash
loop-engineering-hermes-install --root /path/to/hermes/workspace --queue agent-tasks
loop-engineering-hermes-install --root /path/to/hermes/workspace --queue agent-tasks --confirm-install
loop-engineering-hermes-doctor --root /path/to/hermes/workspace --queue agent-tasks
loop-engineering-hermes-smoke --root /path/to/hermes/workspace --queue agent-tasks
```

Installed commands:

```bash
loop-engineering init --root /path/to/workspace
loop-engineering verify --root /path/to/workspace
loop-engineering run --root /path/to/workspace --config configs/loops/<id>.json
loop-engineering status --root /path/to/workspace
loop-engineering doctor --root /path/to/workspace
loop-engineering summarize --root /path/to/workspace --limit 20
loop-engineering project-intake --root /path/to/workspace --name <project> --brief "Project brief"
loop-engineering project-plan --root /path/to/workspace --project <project>
loop-engineering project-status --root /path/to/workspace --project <project>
loop-engineering enqueue --root /path/to/workspace --queue <queue> --title "Title" --task "Task body"
loop-engineering queue-init --root /path/to/workspace --queue <queue>
loop-engineering code-queue-init --root /path/to/workspace --queue <queue>
loop-engineering run-queue --root /path/to/workspace --config configs/loops/queues/<queue>.json
loop-engineering queue-status --root /path/to/workspace --queue <queue>
loop-engineering queue-scheduler-tick --root /path/to/workspace --config configs/loops/queues/<queue>.json
loop-engineering queue-peek --root /path/to/workspace --queue <queue>
loop-engineering queue-cancel --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering queue-requeue --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering queue-revision-next --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering queue-lineage --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering queue-lineage-bundle --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering queue-human-decision --root /path/to/workspace --queue <queue> --task-id <id> --decision approve|request_changes|reject
loop-engineering code-worktree-list --root /path/to/workspace --queue <queue>
loop-engineering code-worktree-inspect --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering code-worktree-diff --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering code-worktree-export --root /path/to/workspace --queue <queue> --task-id <id>
loop-engineering code-patch-verify --root /path/to/workspace --patch runtime/loops/<queue>/patches/<id>.patch
loop-engineering code-patch-apply-plan --root /path/to/workspace --patch runtime/loops/<queue>/patches/<id>.patch
loop-engineering code-patch-apply --root /path/to/wor

skill-card.md

## Description:

Durable explicit task/project loops with verification, revisions, live progress, and governed completion.

This skill is ready for commercial/non-commercial use.

## Publisher:

[ambitioncn](https://clawhub.ai/user/ambitioncn)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and other users explicitly invoking a task or project loop use this skill to coordinate queued work, track progress, verify outcomes, and manage revisions and approval gates.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Installing the CLI or integration can change workspace files, scheduler configuration, and dashboard availability.

Mitigation: Trust and pin a reviewed package version; inspect the installation plan and confirm changes only for the intended workspace and host account.

Risk: An active loop may perform work beyond what the user intended.

Mitigation: Require explicit loop invocation and separate approval for external communication, destructive actions, sensitive changes, and spending beyond an established budget.

## Reference(s):

- [ClawHub skill release](https://clawhub.ai/ambitioncn/skills/taskforce-loop-engineering)
- [npm Package](artifact/references/npm-package.md)

## Skill Output:

**Output Type(s):** [Guidance, Shell commands, Configuration instructions]

**Output Format:** [Markdown with inline shell commands]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May include task status, verification evidence, and next actions.]

## Skill Version(s):

0.15.21 (source: server-resolved release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 9h agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.