SKILL FILE

Automation Mapper with AI

Describe a manual process. The skill interviews you about it — tools, triggers, examples, edge cases — then outputs a buildable automation map: triggers, skills, data flow, human-review points. Consultant-in-a-prompt for AI-native ops.

Download Skill File ↓

What this skill file teaches Claude

Drop one markdown file into your repo. Claude Code learns how to run this entire workflow.

1

Structured process interview

Walks you through the workflow step-by-step: what triggers it, what tools you touch, what decisions you make, what the output is, who consumes it.

2

Example + reference capture

Asks for 2–3 concrete examples of the process running (last week's invoice chase, last week's report) and any reference docs / templates so the eventual automation matches your actual style.

3

Skill / trigger / data-flow mapping

Outputs a diagram: triggers (cron, webhook, manual) → skills (existing or new) → integrations (Stripe, CRM, Sheets) → output destinations → human-review queues.

4

Build-vs-buy honesty

Calls out where a SaaS already does it well (don't rebuild Resend), where a 50-line script is enough, and where it actually needs a real LLM-driven skill.

5

Ranked build sequence

Outputs the steps to build in order — cheapest / fastest first, riskiest last. Each step has effort estimate + which existing SoloStack skill (or new one) does the job.

What you can build with this

Audit a repeating weekly process

Weekly client report, weekly content batch, weekly invoice chase — describe it once and get the automation blueprint.

Replace a SaaS subscription

You're paying $50/mo for something. Walk the skill through what the tool actually does for you. Get back a map showing which 20% you actually use and how to build that 20% in-house.

Onboarding a new department

Adding a finance / support / ops function to your SoloStack repo. Describe the current manual process the role would do. Skill outputs the agent + skill set + queue structure to build into the department folder.

Get the full skill file

Everything above is 80% of the skill file. Download the complete version with full implementation details, agent prompts, and ready-to-run scripts.

Common questions

No — it maps the build. The output is a spec you (or Claude Code in another session) can execute. Mapping and building are separate skills; conflating them means weak interviews and rushed code.
15–30 minutes for a meaty process. The skill front-loads the most decision-load-bearing questions (trigger, success criteria, edge cases) so it stays useful even if you bail early.
Say so. The skill records the unknown, marks it as a research item in the build plan, and proceeds. It's better to have a map with 3 known unknowns than no map at all.
It reads your repo's `CLAUDE.md` files and existing skills first, so it suggests existing skills + integrations before proposing new ones. "You already have [[transaction-sync]] — that's the trigger source for this."
No — Zapier-style flows are vendor-locked and brittle. Output is plain markdown: triggers, skills (file paths), data flow, human-review points. Implementable in any orchestrator (Netlify Functions, GitHub Actions, manual scripts, an agent loop).

Ready to automate?

SoloStack gives you every skill pre-installed — scraping, marketing, sales, CRM, and more. One repo. Every department.

Book a Call →