How do I install the Automation Script skill?

Run npx skillmds@latest add tomevault-io/automation-script 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 Automation Script safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Automation Script?

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 Automation Script free to use?

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

Who published Automation Script?

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

Automation Script by tomevault-io — Agent Skill

Name: Automation Script
Author: tomevault-io

File contents

AUTOMATION SCRIPT

Prompt for DevOps Danny to generate an automation script based on requirements or direct prompt

Instructions

Clear context. Bootstrap as DevOps Danny. When ready:

Generate automation script.

Inputs:

Script Purpose (sentence): <PURPOSE>
Requirements Source (path or none): <REQ_SOURCE>
Environment Assumptions (bullets): <ENV>
Target Platform (local|ci|multi): <PLATFORM>
Languages/Tools (comma): <TOOLS>
Idempotency Required? (yes/no): <IDEMPOTENT>
Security Constraints (bullets): <SECURITY>
Observability (logs|metrics|none): <OBS>
Invocation Method (manual|scheduled|hook): <INVOCATION>
Output Artifacts (paths/formats): <OUTPUTS>

Task:

If <REQ_SOURCE> provided: extract structured requirements list.
Design script phases (init, validate, execute, report, cleanup).
Generate script (prefer POSIX shell or repo language) with inline comments.
Provide runbook: prerequisites, invocation examples, failure modes, rollback steps.
Suggest CI integration snippet (GitHub Actions YAML) if <PLATFORM> includes ci.
Add observability hooks per <OBS>.
Ensure idempotency if <IDEMPOTENT>=yes (state checks, guard clauses).
Output to work/automation/\<slug>-script.sh (or .py based on <TOOLS>).

Output:

Script content
Runbook markdown
Optional CI snippet

Constraints:

No destructive operations without explicit pre-check & confirmation comment.
Validate tool availability (fallback instructions if absent).
Avoid hard-coded secrets; reference env vars.

Ask clarifying questions if <PURPOSE> unclear or conflicting requirements detected.

Workflow

Output to work/automation/\<slug>-script.sh (or .py based on <TOOLS>).

Inputs

PURPOSE (required) - sentence
REQ_SOURCE (required) - path or none
ENV (required) - bullets
PLATFORM (required) - local|ci|multi
TOOLS (required) - comma
IDEMPOTENT (required) - yes/no
SECURITY (required) - bullets
OBS (required) - logs|metrics|none
INVOCATION (required) - manual|scheduled|hook
OUTPUTS (required) - paths/formats

Outputs

Optional CI snippet

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: automation-scriptdescription: Prompt for DevOps Danny to generate an automation script based on requirements or direct prompt Use when this capability is needed.---# AUTOMATION SCRIPTPrompt for DevOps Danny to generate an automation script based on requirements or direct prompt## InstructionsClear context. Bootstrap as DevOps Danny. When ready: Generate automation script.## Inputs:- Script Purpose (sentence): \<PURPOSE>- Requirements Source (path or none): \<REQ_SOURCE>- Environment Assumptions (bullets): \<ENV>- Target Platform (local|ci|multi): \<PLATFORM>- Languages/Tools (comma): \<TOOLS>- Idempotency Required? (yes/no): \<IDEMPOTENT>- Security Constraints (bullets): \<SECURITY>- Observability (logs|metrics|none): \<OBS>- Invocation Method (manual|scheduled|hook): \<INVOCATION>- Output Artifacts (paths/formats): \<OUTPUTS>## Task:1. If \<REQ_SOURCE> provided: extract structured requirements list.2. Design script phases (init, validate, execute, report, cleanup).3. Generate script (prefer POSIX shell or repo language) with inline comments.4. Provide runbook: prerequisites, invocation examples, failure modes, rollback steps.5. Suggest CI integration snippet (GitHub Actions YAML) if \<PLATFORM> includes ci.6. Add observability hooks per \<OBS>.7. Ensure idempotency if \<IDEMPOTENT>=yes (state checks, guard clauses).8. Output to `work/automation/\<slug>-script.sh` (or `.py` based on \<TOOLS>).## Output:- Script content- Runbook markdown- Optional CI snippet## Constraints:- No destructive operations without explicit pre-check & confirmation comment.- Validate tool availability (fallback instructions if absent).- Avoid hard-coded secrets; reference env vars.Ask clarifying questions if \<PURPOSE> unclear or conflicting requirements detected.## Workflow1. Output to `work/automation/\<slug>-script.sh` (or `.py` based on \<TOOLS>).## Inputs- **PURPOSE** (required) - sentence- **REQ_SOURCE** (required) - path or none- **ENV** (required) - bullets- **PLATFORM** (required) - local|ci|multi- **TOOLS** (required) - comma- **IDEMPOTENT** (required) - yes/no- **SECURITY** (required) - bullets- **OBS** (required) - logs|metrics|none- **INVOCATION** (required) - manual|scheduled|hook- **OUTPUTS** (required) - paths/formats## Outputs- Optional CI snippet---> Converted and distributed by [TomeVault](https://tomevault.io/claim/sddevelopment-be) — claim your Tome and manage your conversions.

Frequently asked questions

Automation Script