GTM Engineering
tech-leads-club/agent-skills
Designs go-to-market automation and AI agent workflows for revenue teams, built on the idea that architecture and context matter more than any single tool.
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).
Install Automation Instructions
$ npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install deusXmachina-dev/memorylane automation-instructions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/deusXmachina-dev/memorylane.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/memorylane/skills/automation-instructions .claude/skills/automation-instructions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "automation-instructions" agent skill from https://github.com/deusXmachina-dev/memorylane/tree/main/plugins/memorylane/skills/automation-instructions into .claude/skills/automation-instructions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-instructions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/deusXmachina-dev/memorylane/tree/main/plugins/memorylane/skills/automation-instructionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install deusXmachina-dev/memorylane automation-instructions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deusXmachina-dev/memorylane.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/memorylane/skills/automation-instructions .agents/skills/automation-instructions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "automation-instructions" agent skill from https://github.com/deusXmachina-dev/memorylane/tree/main/plugins/memorylane/skills/automation-instructions into .agents/skills/automation-instructions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-instructions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install deusXmachina-dev/memorylane automation-instructions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deusXmachina-dev/memorylane.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/memorylane/skills/automation-instructions .cursor/skills/automation-instructions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "automation-instructions" agent skill from https://github.com/deusXmachina-dev/memorylane/tree/main/plugins/memorylane/skills/automation-instructions into .cursor/skills/automation-instructions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-instructions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/deusXmachina-dev/memorylane.git --path plugins/memorylane/skills/automation-instructions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install deusXmachina-dev/memorylane automation-instructions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deusXmachina-dev/memorylane.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/memorylane/skills/automation-instructions .gemini/skills/automation-instructions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "automation-instructions" agent skill from https://github.com/deusXmachina-dev/memorylane/tree/main/plugins/memorylane/skills/automation-instructions into .gemini/skills/automation-instructions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-instructions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install deusXmachina-dev/memorylane automation-instructionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/deusXmachina-dev/memorylane.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/memorylane/skills/automation-instructions .github/skills/automation-instructions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "automation-instructions" agent skill from https://github.com/deusXmachina-dev/memorylane/tree/main/plugins/memorylane/skills/automation-instructions into .github/skills/automation-instructions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-instructions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install deusXmachina-dev/memorylane automation-instructions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/deusXmachina-dev/memorylane.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/memorylane/skills/automation-instructions .opencode/skills/automation-instructions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "automation-instructions" agent skill from https://github.com/deusXmachina-dev/memorylane/tree/main/plugins/memorylane/skills/automation-instructions into .opencode/skills/automation-instructions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-instructions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
automation-instructions- GitHub stars
- 121
- Token cost
- ~1.1k tokens
- SKILL.md length
- 535 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).
- Works in 4 steps: Get the workflow (prefer prior output) → Ask three things (one batched… → Write the instructions (tailored to the… → …
- Tasks that involve Workflow automation
- SKILL.md covers Before you start, Step 1. Get the workflow…, Step 2. Ask three things (one… and Step 3. Write the instructions…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Automation Instructions is an agent skill from deusXmachina-dev/memorylane. Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier). Best run right after discover-patterns or process-analyst.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Workflow automation. It works with n8n and Zapier. The licence is GPL-3.0.
When your agent uses it
- Tasks that involve Workflow automation
Example prompts
- “/automation-instructions”
Requirements
- Pre-approved tools (allowed-tools): AskUserQuestion, mcp__memorylane__browse_timeline, mcp__memorylane__search_context, mcp__memorylane__get_activity_details
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 16abbe0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
AskUserQuestionmcp__memorylane__browse_timelinemcp__memorylane__search_contextmcp__memorylane__get_activity_details
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Automation Instructions loads about 1.1k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 535 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from deusXmachina-dev/memorylane at commit 16abbe0, republished under its GPL-3.0 licence (© deusXmachina-dev). 535 words, ~1,142 tokens.
Download SKILL.mdSave it as
.claude/skills/automation-instructions/SKILL.md (or your agent's skills folder).- name
- automation-instructions
- description
- Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier). Best run right after discover-patterns or process-analyst.
- allowed-tools
- AskUserQuestion, mcp__memorylane__browse_timeline, mcp__memorylane__search_context, mcp__memorylane__get_activity_details
Automation Instructions
Turn one workflow into clear, build-ready instructions for a specific automation tool.
Assumes it runs after /discover-patterns or /process-analyst-new, so it reuses
their output as the source and does NOT re-mine the timeline unless nothing is supplied.
Before you start
If the browse_timeline tool is not available, stop and reply with exactly:
MemoryLane isn't connected to Claude yet. Open the MemoryLane app, go to Integrations, click Add to Claude, then restart Claude Desktop and run this again.
Do not suggest plugin settings, Retry, or toggling the plugin.
Step 1. Get the workflow (prefer prior output)
In priority order, do NOT re-derive what you already have:
- A pattern from
/discover-patterns(a selected pattern + its details) -> use it as-is. - A process from
/process-analyst-new(aprocess-analysis*.jsonledger, or a process the user points to) -> read that process's steps, apps, frequency, and automatable split. Globprocess-analysis*.jsonin the working dir; if found, use it. - A workflow the user describes in chat -> use the description as-is.
Only if NONE of the above is available, fall back to mining: search_context(query) across
~30 days for instances, browse_timeline around the strongest matches for the full sequence,
and get_activity_details(ids) on 2 to 3 clear instances for exact steps. Keep it bounded.
Step 2. Ask three things (one batched AskUserQuestion)
- Target tool - Claude, n8n, or Zapier. Drives the whole output style.
- Constraints - anything it must NOT do (no writes to prod, no emails to customers, human approval required, leave step X manual, etc.).
- Output format - text, markdown, or JSON. Assume markdown if skipped.
Respect the constraints everywhere in Step 3, and call out any step the constraints force to stay human.
Show full SKILL.md (256 more words)Show less
Step 3. Write the instructions (tailored to the tool + format)
Reconstruct the flow from trigger to done, separating variables (change each run, the inputs) from constants (fixed, hardcoded). Then write it for the chosen tool:
- Claude (Cowork / Skill) - frame as Connect, Create, Run. Which apps to connect, the Skill/agent brief and the steps Claude runs, what it drafts vs writes, and the human approval gate before anything is sent or saved.
- n8n - the trigger node, the ordered nodes with the app/action and the data mapped between them, and error/retry handling. Deterministic, so any judgment step stays a human or AI-assist node.
- Zapier - the Trigger, then one Action per step (app + action + field mapping), plus any Filter or Path for branches. Note steps Zapier cannot do that need a human or code.
Render in the chosen format: markdown = the skeleton below; text = the same content
as plain prose, no markdown; JSON = one object { name, tool, trigger, variables[], constants[], steps[{n, app, action, input, output, on_error}], human_steps[], constraints[] }.
Markdown skeleton (keep it tight, drop empty sections):
# [Workflow] - Automation instructions ([tool])
**Does:** [one line] **Trigger:** [what starts it] **Frequency:** [from the source]
**Constraints:** [what it must not do]
## Variables (inputs that change each run)
- [name]: [example]
## Constants (hardcoded)
- [name]: [value]
## Steps
1. [Action] in [app] - input [x] -> output [y]. On error: [fallback].
2. ...
## Stays human
- [step + why, incl. anything the constraints forced manual]
## Build notes ([tool])
- [trigger + key apps/nodes/actions + effort: easy/medium/hard]Step 4. Save and present
Ask where to save (default ~/Desktop/automation/[workflow-slug].md, or .txt / .json
to match the format). Create the folder if needed. Then show the path and a 2-line summary
(tool, step count, key apps). Offer to do another workflow.
Notes
- Privacy - never put passwords, API keys, or personal-message content in the output; keep only process-relevant details (app names, field labels, URLs).
- Gaps - if the source evidence is thin, say which steps are assumed and what the user should confirm before building.
© deusXmachina-dev, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/memorylane/skills/automation-instructions of deusXmachina-dev/memorylane.
Open the folder on GitHubat commit 16abbe0
Compare with similar skills
Automation Instructions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Automation Instructions this skilldeusXmachina-dev/memorylane | 121 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| GTM Engineeringtech-leads-club/agent-skills | 7k | — | ~4.8k | Automated safety check: Pass | Custom licence | |
| Automation WorkflowsCraftOS-dev/CraftBot | 392 | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Automation Flowsericrisco/rsc-harness | 174 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Lindy Migration Deep Divejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Pass | MIT | |
| Automation Strategyericrisco/rsc-harness | 174 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Automation Workflows
CraftOS-dev/CraftBot
Design and implement automation workflows to save time and scale operations as a solopreneur.
Automation Flows
ericrisco/rsc-harness
A skill your agent uses when building or fixing a no-code automation on n8n, Make, or Zapier — trigger to multi-app steps with data mapping, dedup, retries and an error path — or picking the…
Lindy Migration Deep Dive
jeremylongshore/tons-of-skills-marketplace
Advanced migration strategies for moving to Lindy AI from other platforms.
Automation Strategy
ericrisco/rsc-harness
A skill your agent uses when deciding whether a process is worth automating, sizing ROI and build-vs-buy, choosing an automation platform, or diagnosing why a fleet of automations keeps breaking —…
N8n
ericrisco/rsc-harness
A skill your agent uses when operating a live n8n instance programmatically — its REST API ({host}/api/v1, X-N8N-API-KEY) or the n8n-mcp server — to create, validate, test, activate, update, delete…
More from deusXmachina-dev/memorylane
All 9 skills in this repoMakemigrations
deusXmachina-dev/memorylane
Create SQLite migrations for MemoryLane storage schema changes.
Release
deusXmachina-dev/memorylane
Prepare a MemoryLane release by updating the version and release notes, then creating and pushing the tagged release commit that triggers CI.
Process Analyst New
deusXmachina-dev/memorylane
(new) Find a person's repeated tasks from their screen activity, and what each one is worth automating, with the time and money saved.
Discover Patterns
deusXmachina-dev/memorylane
Discover repeated workflow patterns from screen activity and suggest automations
Last 30 Minutes
deusXmachina-dev/memorylane
Summarize what you've been doing in the last 30 minutes. An agent skill from deusXmachina-dev/memorylane.
Report New
deusXmachina-dev/memorylane
(new) Turn a process analysis into a polished, client-ready report, first an HTML deck you review, then a matching PDF.
Related
Categories
Questions about Automation Instructions
What does Automation Instructions do?
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier). Automation Instructions is an agent skill from deusXmachina-dev/memorylane. Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).
When should I use Automation Instructions?
Automation Instructions fits situations like: tasks that involve Workflow automation.
How do I install Automation Instructions in Claude Code?
Run `npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a claude-code`. Or copy the skill folder (plugins/memorylane/skills/automation-instructions in deusXmachina-dev/memorylane) into .claude/skills/automation-instructions in your project. Claude Code loads it when a task matches its description.
How do I install Automation Instructions in Codex?
Run `npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a codex`. Or copy the skill folder (plugins/memorylane/skills/automation-instructions in deusXmachina-dev/memorylane) into .agents/skills/automation-instructions in your project. Codex loads it when a task matches its description.
Can I use Automation Instructions in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add deusXmachina-dev/memorylane --skill automation-instructions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/automation-instructions, .gemini/skills/automation-instructions, .github/skills/automation-instructions and .opencode/skills/automation-instructions in your project.
What does Automation Instructions need to run?
SKILL.md names no scripts, command-line tools or credentials: Automation Instructions is instructions for the agent only. Its frontmatter pre-approves these tools: AskUserQuestion, mcp__memorylane__browse_timeline, mcp__memorylane__search_context, mcp__memorylane__get_activity_details.
Does Automation Instructions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Automation Instructions safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Automation Instructions use?
Automation Instructions is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Automation Instructions use?
About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Automation Instructions?
Skills that share tags, products or a category with Automation Instructions: GTM Engineering (tech-leads-club/agent-skills, 7k stars), Automation Workflows (CraftOS-dev/CraftBot, 392 stars), Automation Flows (ericrisco/rsc-harness, 174 stars) and Lindy Migration Deep Dive (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Automation Instructions?
deusXmachina-dev (a GitHub organization) maintains it in deusXmachina-dev/memorylane, which has 121 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 8, 2026.
Source: deusXmachina-dev/memorylane on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.