Run any Skill in Manus with one click

animate-objects

Stars98

Forks12

UpdatedApril 5, 2026 at 03:15

This spell transforms inert → reactive. It does NOT create new tools, train models, run one-off fixes, or build physical systems. The key pattern: existing artifact + trigger/watcher + bounded autonomy.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Hmbown

Hmbown/Wizards-of-the-Ghosts

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	animate-objects
description	This spell transforms inert → reactive. It does NOT create new tools, train models, run one-off fixes, or build physical systems. The key pattern: existing artifact + trigger/watcher + bounded autonomy.
user-invocable	true

Animate Objects

Give agency to passive data by attaching triggers, watchers, and autonomous update logic.

Overview

Animate Objects is interpreted here as a literal spell with a prototype execution model.

Canonical source: Animate Objects (spell)

Provider target: OpenClaw

When To Use

Trigger this spell when a user asks to make an existing static artifact self-updating, reactive, or autonomous. Look for:
"make it alive", "living document", "self-updating", "auto-refresh"
References to existing files: CSV, YAML, JSON, README, config, spreadsheet, dashboard, spec, diagram
Phrases like "pulls from [source]", "watches for changes", "reconciles differences", "flags when stale"
Desire for ongoing automation attached to a specific existing artifact

Workflow

Identify the inert artifact — name the exact file, dataset, or document. Confirm it exists and is currently static.
Define the trigger — what event, schedule, or change should wake it up? (cron, file watch, API poll, git hook, webhook)
Specify the autonomous action — what exactly should it do when triggered? Keep scope narrow: update itself, flag discrepancies, regenerate derived output.
Set boundaries and kill switch — what must it NOT do? How do you revert it to passive state? Document both before implementing.
Implement minimal agency — attach the simplest trigger + action loop that satisfies the request. Prefer existing tooling (watchexec, cron, GitHub Actions, simple scripts) over custom daemons.
Verify containment — confirm the artifact only acts within its granted scope and the kill switch works.

Deliverables

A previously static artifact with autonomous update or reaction logic attached.
A clear definition of the object's granted agency and its boundaries.
A kill switch or revert path that returns the object to its inert state.

Guardrails

Scope must be explicit: a self-updating spreadsheet does not start sending emails unless approved
Always provide a documented kill switch or revert path
No write access to downstream systems without explicit user approval
Prefer read-only or self-modifying behavior over cross-system actuation
Do not use for: Training AI on data — "teach this dataset to understand queries" → ML/NLP spell
Do not use for: One-off cleanup scripts — "run once to fix stale entries" → simple scripting, no ongoing agency
Do not use for: Building new tools — "create a CLI tool" → software development, not animating existing artifact
Do not use for: Physical automation — "robot that moves objects" → hardware/IoT, out of scope
Do not use for: Syntax repair — "fix broken JSON" → data repair, no autonomy added
Do not use for: Autonomous agents — "virtual assistant that makes decisions" → agent design, not artifact animation

Default Invocation

Use $animate-objects to make this artifact self-updating, with clear agency boundaries and a kill switch.

More from this repository

same repository

mage-hand

Hmbown/Wizards-of-the-Ghosts

Use this skill for small, careful remote manipulations where dexterity matters more than force.

2026-04-0598

unseen-servant

Hmbown/Wizards-of-the-Ghosts

Use this spell when you need a tireless helper that organizes, tidies, triages, and maintains without requiring your constant attention.

2026-04-0598

arcana

Hmbown/Wizards-of-the-Ghosts

In D&D, Arcana is knowledge of magic, its traditions, symbols, and mechanisms. The real-world version is deep technical literacy: understanding how software architectures work, what protocols do at the wire level, how APIs behave beyond their documentation, and what the actual mechanisms are behind the abstractions everyone else takes on faith.

2026-04-0598

mirage-arcane

Hmbown/Wizards-of-the-Ghosts

In D&D, Mirage Arcane goes beyond Hallucinatory Terrain — the illusory terrain actually has substance. You can walk on illusory bridges, feel illusory walls. The real-world version is the deep simulation: digital twins, high-fidelity synthetic environments, test harnesses so realistic that systems under test cannot distinguish them from production. Mirage Arcane is the most dangerous illusion because its power is in being indistinguishable from reality. That same power makes it the most useful for stress testing, training, and scenario planning — but it requires the strongest labeling discipline.

2026-04-0598

project-image

Hmbown/Wizards-of-the-Ghosts

In D&D, Project Image creates an illusory copy of yourself at a distant location — you can see through its eyes, speak through its mouth, and cast spells through it. The real-world version is remote presence: avatars, recorded video stand-ins, bot representations, asynchronous video messages. Project Image is the spell for being in two places at once — attending a meeting via avatar while working on something else, leaving a recorded presence in a channel, or deploying an automated representative that speaks with your voice and authority within defined limits.

2026-04-0598

acrobatics

Hmbown/Wizards-of-the-Ghosts

Use this skill when the work is a choreography problem: brittle sequencing, async handoffs, or constrained flows that must stay upright end to end. It shines on API dances, dependency ordering, and recovery logic where grace matters more than brute force.

2026-04-0598

name	animate-objects
description	This spell transforms inert → reactive. It does NOT create new tools, train models, run one-off fixes, or build physical systems. The key pattern: existing artifact + trigger/watcher + bounded autonomy.
user-invocable	true

Animate Objects

Give agency to passive data by attaching triggers, watchers, and autonomous update logic.

Overview

Animate Objects is interpreted here as a literal spell with a prototype execution model.

Canonical source: Animate Objects (spell)

Provider target: OpenClaw

When To Use

Trigger this spell when a user asks to make an existing static artifact self-updating, reactive, or autonomous. Look for:
"make it alive", "living document", "self-updating", "auto-refresh"
References to existing files: CSV, YAML, JSON, README, config, spreadsheet, dashboard, spec, diagram
Phrases like "pulls from [source]", "watches for changes", "reconciles differences", "flags when stale"
Desire for ongoing automation attached to a specific existing artifact

Workflow

Identify the inert artifact — name the exact file, dataset, or document. Confirm it exists and is currently static.
Define the trigger — what event, schedule, or change should wake it up? (cron, file watch, API poll, git hook, webhook)
Specify the autonomous action — what exactly should it do when triggered? Keep scope narrow: update itself, flag discrepancies, regenerate derived output.
Set boundaries and kill switch — what must it NOT do? How do you revert it to passive state? Document both before implementing.
Implement minimal agency — attach the simplest trigger + action loop that satisfies the request. Prefer existing tooling (watchexec, cron, GitHub Actions, simple scripts) over custom daemons.
Verify containment — confirm the artifact only acts within its granted scope and the kill switch works.

Deliverables

A previously static artifact with autonomous update or reaction logic attached.
A clear definition of the object's granted agency and its boundaries.
A kill switch or revert path that returns the object to its inert state.

Guardrails

Scope must be explicit: a self-updating spreadsheet does not start sending emails unless approved
Always provide a documented kill switch or revert path
No write access to downstream systems without explicit user approval
Prefer read-only or self-modifying behavior over cross-system actuation
Do not use for: Training AI on data — "teach this dataset to understand queries" → ML/NLP spell
Do not use for: One-off cleanup scripts — "run once to fix stale entries" → simple scripting, no ongoing agency
Do not use for: Building new tools — "create a CLI tool" → software development, not animating existing artifact
Do not use for: Physical automation — "robot that moves objects" → hardware/IoT, out of scope
Do not use for: Syntax repair — "fix broken JSON" → data repair, no autonomy added
Do not use for: Autonomous agents — "virtual assistant that makes decisions" → agent design, not artifact animation

Default Invocation

Use $animate-objects to make this artifact self-updating, with clear agency boundaries and a kill switch.