← Back to Skills Marketplace
cjboy007

Auto Revolution

by Jaden's built a claw · GitHub ↗ · v2.0.2 · MIT-0
cross-platform ⚠ suspicious
127
Downloads
0
Stars
1
Active Installs
2
Versions
Install in OpenClaw
/install auto-revolution
Description
Safe publishing variant of Auto Revolution. Provides structured task templates, review prompts, safety scanning, task state updates, and logging for human su...
README (SKILL.md)

Auto Revolution

This is the ClawHub publishing variant.

Use this skill for

  • creating structured task JSON files
  • activating queued tasks whose dependencies are complete
  • scanning proposed instruction text for risky shell patterns
  • applying review JSON back into a task file
  • logging workflow events in JSONL
  • generating a review prompt for manual or supervised review

Do not use this package for

  • autonomous cron loops
  • unsupervised background execution
  • direct execution of arbitrary shell instruction strings
  • remote agent spawning from bundled scripts

Files to use

  • task-schema.json for task structure reference
  • config/models.json for example role configuration
  • scripts/create-task.js to create a task interactively
  • scripts/activate-queued-tasks.js to move ready tasks from queued to pending
  • scripts/security-scan.js to scan instruction text or a task review block
  • scripts/trigger-review.js to generate a review prompt for supervised review
  • scripts/apply-review.js to write a review result back into a task JSON file
  • scripts/log-event.js to append JSONL audit events
  • scripts/atomic-lock.sh, scripts/force-unlock.sh, scripts/unblock-task.sh for task lock maintenance

Minimal workflow

  1. Create or edit a task JSON.
  2. If the task depends on other tasks, run scripts/activate-queued-tasks.js when dependencies may be complete.
  3. Generate a review prompt with scripts/trigger-review.js.
  4. Obtain a supervised review result as JSON.
  5. Apply that result with scripts/apply-review.js.
  6. If you need to inspect instruction text, run scripts/security-scan.js before any manual execution.

Safety rules

  • Keep a human in the loop for any real execution.
  • Treat generated instructions as untrusted until reviewed.
  • Prefer structured task updates over free form shell execution.
  • Do not add scripts that call execSync on model generated instruction strings in the publishing package.

Notes

This package is intentionally minimal for publication. Internal development documents, autonomous heartbeat runners, and direct execution engines belong in the private local version, not the published package.

Usage Guidance
This package broadly matches a supervised task-review/publishing helper, but proceed cautiously: - Do not assume the package is a drop-in complete system: several scripts referenced in README/SKILL.md are missing (start-reviewer.js, start-executor.js, iron-heartbeat.js) — the README and some outputs point to workflows that rely on external components not bundled here. - Inspect and fix shell scripts before running: force-unlock.sh and unblock-task.sh appear to contain a stray trailing '}' and other minor syntax issues; test them in a safe environment first. - Beware of implicit automation suggestions: trigger-review.js recommends using sessions_spawn (automatic invocation) as 'recommended'. If you want a strictly supervised flow, avoid using sessions_spawn or any automatic runner that would feed model output back without human review. - The security scanner is helpful (security-scan.js), but it is pattern-based and not foolproof. Always review any generated 'next_instructions' yourself before executing them. - Run the scripts in an isolated environment (sandbox/container) with backed-up task/log directories the first time, and validate behavior on sample tasks. If you plan to use this in production or link it to hosted LLMs, ask the publisher for the missing runner scripts or documentation about the intended orchestration and ensure platform credentials are stored and used outside this package. Fix the reported script syntax issues and verify that automatic invocation paths are intentionally enabled and audited before enabling them.
Capability Analysis
Type: OpenClaw Skill Name: auto-revolution Version: 2.0.2 The 'auto-revolution' skill bundle is a task management framework designed for human-supervised workflows. It provides structured utilities for creating tasks, managing state transitions (queued, pending, reviewing), and implementing file-based concurrency locking via 'scripts/atomic-lock.sh'. A key security feature is 'scripts/security-scan.js', which uses regex patterns to proactively detect dangerous shell commands like RCE payloads or unauthorized file deletions. The code is well-documented, lacks autonomous execution capabilities, and contains no evidence of data exfiltration or malicious intent.
Capability Assessment
ℹ Purpose & Capability
The skill's name, description, and included scripts (task creation, queued activation, security scanning, review trigger, apply-review, logging, lock helpers) align with the advertised 'safe publishing' / supervised-review purpose. It does not request environment credentials or external config. Note: the package references LLM role names (e.g. advanced-model/sonnet, anthropic/claude-sonnet-4-6) but does not request or document API keys — this is plausible for a publishing bundle that expects a platform-level agent, but users should be aware it assumes an external agent/model infrastructure.
⚠ Instruction Scope
SKILL.md and scripts otherwise stay within the stated supervised workflow boundaries, but multiple instructions reference scripts or behaviors that are not present (e.g., create-task.js and README mention node scripts/start-reviewer.js and node scripts/start-executor.js; apply-review.js and create-task.js mention node scripts/iron-heartbeat.js). trigger-review.js explicitly recommends an 'automatic (recommended) sessions_spawn' flow to call Sonnet and then auto-apply results — this encourages autonomous invocation despite the package's repeated claim that it avoids autonomous background execution. These inconsistencies grant the agent/user broad discretion and could mislead someone expecting a purely manual, audited flow.
✓ Install Mechanism
No install spec is provided (instruction-only publish bundle). All code is bundled in the package; nothing is downloaded or executed automatically during install, which is the lowest-risk install behavior.
✓ Credentials
The skill requires no environment variables, credentials, or external config paths. It references model names only in config/models.json and prompts; these do not themselves require secrets in the bundle. This is proportionate to a local publishing helper package, but if you intend to integrate with hosted models you will need platform credentials that are not requested here.
✓ Persistence & Privilege
The package does not request always:true or any persistent system-level privileges. It reads/writes files under local tasks/ and logs/ directories only. That level of persistence is expected for a task management helper and is consistent with the stated purpose.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install auto-revolution
  3. After installation, invoke the skill by name or use /auto-revolution
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.2
Publish safe minimal ClawHub variant with supervised workflow helpers only. Removed autonomous heartbeat runners, direct execution engine, review runner, internal design docs, and test scripts.
v2.0.1
Auto Revolution Skill 2.0.1 is a sanitized (脱敏) release. - Public release with sensitive information removed. - No functional or workflow changes since 2.0.0. - Documentation improvements for clarity and safety.
Metadata
Slug auto-revolution
Version 2.0.2
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 2
Frequently Asked Questions

What is Auto Revolution?

Safe publishing variant of Auto Revolution. Provides structured task templates, review prompts, safety scanning, task state updates, and logging for human su... It is an AI Agent Skill for Claude Code / OpenClaw, with 127 downloads so far.

How do I install Auto Revolution?

Run "/install auto-revolution" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Auto Revolution free?

Yes, Auto Revolution is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Auto Revolution support?

Auto Revolution is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Auto Revolution?

It is built and maintained by Jaden's built a claw (@cjboy007); the current version is v2.0.2.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments