How do I install the Lisa Tear Down Automations skill?

Run npx skillmds@latest add codyswanngt/lisa-tear-down-automations-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lisa Tear Down Automations safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lisa Tear Down Automations?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lisa Tear Down Automations free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lisa Tear Down Automations?

codyswanngt (@codyswanngt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lisa Tear Down Automations by codyswanngt

Name: Lisa Tear Down Automations
Author: codyswanngt

Lisa Tear Down Automations

Remove every recurring Lisa automation that /setup-automations created for this project (the lisa-auto-<project>-* set: intake-repair, intake-prd, intake-tickets, exploratory-bugs, exploratory-prds) using the CURRENT runtime's native scheduler — Codex automations or, on Claude, /schedule. This skill is a declarative specification: it identifies WHICH automations to remove; it does not run teardown scripts. Removes only this project's Lisa automations — never other projects' automations or non-Lisa ones. The inverse of /setup-automations.

codyswanngt Updated Sep 21, 2026

File contents

Tear down Lisa automations: $ARGUMENTS

This skill is a specification, not a script. It tells the current runtime which recurring Lisa automations to remove — the ones /setup-automations created for THIS project — and the runtime removes them with its native scheduling mechanism.

Runtime scheduler (branch on the current runtime)

Codex → list Codex automations and delete the lisa-auto-<project>-* set via the native automations mechanism (prefer the native delete over hand-removing ~/.codex/automations/<id>/, which is only the backing store).
Claude → use /schedule to list and remove the matching recurring routines.
Other runtimes → use the runtime's native recurring-task mechanism. If it has none, state that and stop.

Scope (remove only what setup created)

Remove the five automations /setup-automations creates for the current project, matched by the stable lisa-auto-<project>- name prefix: intake-repair, intake-prd, intake-tickets, exploratory-bugs, exploratory-prds.
Never remove automations for a different project, or any non-Lisa automation (e.g. unrelated crawlers/ingestors). Match strictly on the lisa-auto-<project>- prefix for THIS project; when in doubt about an automation's ownership, leave it and report it rather than deleting it.
Idempotent — an automation that is already absent is a no-op, not an error.

Report

List each automation removed, and any in the expected set that were already absent.

---name: lisa-tear-down-automations-2description: Remove every recurring Lisa automation that /setup-automations created for this project (the lisa-auto-<project>-* set: intake-repair, intake-prd, intake-tickets, exploratory-bugs, exploratory-prds) using the CURRENT runtime's native scheduler — Codex automations or, on Claude, /schedule. This skill is a declarative specification: it identifies WHICH automations to remove; it does not run teardown scripts. Removes only this project's Lisa automations — never other projects' automations or non-Lisa ones. The inverse of /setup-automations.---# Tear down Lisa automations: $ARGUMENTSThis skill is a **specification, not a script.** It tells the current runtime which recurring Lisaautomations to remove — the ones `/setup-automations` created for THIS project — and the runtimeremoves them with its **native** scheduling mechanism.## Runtime scheduler (branch on the current runtime)- **Codex** → list Codex automations and delete the `lisa-auto-<project>-*` set via the native automations mechanism (prefer the native delete over hand-removing `~/.codex/automations/<id>/`, which is only the backing store).- **Claude** → use **`/schedule`** to list and remove the matching recurring routines.- **Other runtimes** → use the runtime's native recurring-task mechanism. If it has none, state that and stop.## Scope (remove only what setup created)- Remove the five automations `/setup-automations` creates for the current project, matched by the stable `lisa-auto-<project>-` name prefix: `intake-repair`, `intake-prd`, `intake-tickets`, `exploratory-bugs`, `exploratory-prds`.- **Never** remove automations for a different project, or any non-Lisa automation (e.g. unrelated crawlers/ingestors). Match strictly on the `lisa-auto-<project>-` prefix for THIS project; when in doubt about an automation's ownership, leave it and report it rather than deleting it.- **Idempotent** — an automation that is already absent is a no-op, not an error.## ReportList each automation removed, and any in the expected set that were already absent.

Frequently asked questions