Sno Station
Sno Station은 AI 에이전트를 하나의 팀으로 묶는 오픈소스 워크스테이션으로, 로컬 머신에서 에이전트 협업을 가능하게 함
ai-employees는 오픈소스 AI 직원으로, Claude Code 등 10가지 도구에서 8가지 업무 역할과 60가지 루틴을 수행합니다
Open source AI Employees. 8 scheduled business roles, 60 routines, on Claude Code and 10 other harnesses. They drive your browser the way you do and improve every run. You own the files.
플러그인JavaScript · HTMLGitHub @markfulton직접 설치운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
설치형 프로젝트는 배포 도메인 없이도 확인할 수 있습니다. 개인 저장소는 GitHub 로그인으로, 조직 저장소는 위의 저장소 확인 파일로 직접 확인해 주세요.
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Eight open source AI Employees. Each one runs a whole business role.
60 scheduled routines. Your own machine. The AI agent you already use.
⭐ Found something useful? Star the repo. It takes a second and helps the next person find it.
An AI Employee is a folder of scheduled routines that covers one business role. It runs on your own machine, on the AI agent you already use, and briefs you every morning. They drive your browser and your PC the way you do, and every run makes the next one better. Eight roles, every routine and schedule in this repo, nothing held back.README 전문 보기 ↗An AI Employee is a folder of scheduled routines that covers one business role. It runs on your own machine, on the AI agent you already use, and briefs you every morning. They drive your browser and your PC the way you do, and every run makes the next one better. Eight roles, every routine and schedule in this repo, nothing held back.
Created by Mark Fulton of Reinventing.AI, founder of Vibe Coding is Life (340,000+ members). Running my own business every weekday since August 27, 2026.
New to building with AI agents? Start with What is vibe coding, the free reference that explains the practice, the tools and how to do it well.
| Employee | What it owns | Routines |
|---|---|---|
| GTM Engineer | Your launch: positioning, the launch board, outbound drafts, directory and press forms, the weekly scoreboard | 8 |
| SEO/AEO Employee | Keyword research, one article a weekday, publishing, indexing, rank review and your visibility in AI answers | 8 |
| Web Dev Employee | Site health, error triage, small changes on a branch, dependency review | 8 |
| Social Media Employee | Posts drafted in your voice for each platform, a veto window, replies drafted for you | 7 |
| Ad Manager Employee | Account reads, creative sets, build sheets and the weekly change list. Money moves only when you approve | 7 |
| Sales Employee | Prospect sweeps, first touches into your own drafts, follow ups that never go quiet | 7 |
| Customer Satisfaction Employee | Inbox sweep, replies drafted hardest first, churn flags with evidence | 8 |
| Chief of Staff | Reads every other employee's run log, names what quietly stopped, brings you three moves | 7 |
Sixty routines. Every kit, with its full schedule and a sample of its output, is in employees/.
The fastest way: hire your first AI Employee in the Agent Ops Club. Pick the role, and the club writes the one prompt your agent runs from start to finish: it downloads the kit, researches your business from your website, builds your dashboard and schedules its own routines. A free account, no card, and the Hire Your First AI Employee walkthrough is waiting on the other side. The two steps below are the same install done by hand.
1. Download a kit and extract it to your PC. Click Code, Download ZIP above, or run npx ai-employees hire gtm-engineer --to <folder>. Any folder not inside OneDrive, Dropbox, Google Drive or iCloud.
2. Open your agent in that folder and say "Install the GTM Engineer from this folder." It researches your business from your website, builds your dashboard, schedules its own routines, and stops once to show you its first drafts.
You need an AI agent you are logged in to (Claude Code is what I use) and a browser signed in to the accounts it should read. Prerequisites. Full install guide.
This repository is also a Claude Code plugin with one skill, hire, and all eight kits bundled. In any Claude Code session:
/plugin marketplace add markfulton/ai-employees
/plugin install ai-employees@ai-employees
Then say "hire the GTM Engineer into D:\AgentOps\gtm-engineer", or run /ai-employees:hire. The skill checks the folder is outside cloud sync, copies the kit from the plugin with no download, runs the self tests, and tells you the one line to say in a fresh session in that folder. It registers nothing and sends nothing. The plugin page has the same steps with a walkthrough.
What the plugin runs. The hire skill runs one command, node installer/cli.mjs hire <employee> --to <folder>, from the installer bundled in the plugin. It copies one kit from the plugin into the folder you choose, writes .installed.json there, runs every kit script with --selftest under Node, and runs claude auth status to see whether you are signed in. On that path it makes no network request, collects no data and sends no telemetry. The installer downloads a kit from github.com/markfulton/ai-employees only when it has no bundled copy, which never happens inside the plugin or the npm package, since both carry the kits. Used without the plugin, the skill asks before it fetches anything from npm or GitHub. It registers no schedule, sends nothing and never reads or enters a credential. A hired employee is a separate step that runs in its own folder, and docs/GUARDRAILS.md says what it may and may not do.
Not on Claude Code? The same two steps work on OpenClaw, Hermes, OpenCode, Grok Bot, Codex, Antigravity, Pi, Cline, Qwen Code, DeepSeek, Muse and Dots. docs/HARNESSES.md has the command for each.
npx ai-employees upgrade leaves every file you edited alone.The existing routines now record verified deliverables separately from successful runs and business results. They keep preparing authorized work when another step is blocked, review bounded experiments, and report delivery stalls. Configured handoffs connect roles without writing into another employee's folder. Interrupted work uses atomic claims and the remaining scheduled budget.
SEO/AEO includes native Google Search Console Generative AI impressions. Upgrades preserve local changes and offer reviewable three-way reconciliation. See upgrade instructions, behavior evaluation and release commands.
The brief the GTM Engineer leaves, from a fictional business, Northwind Roofing. Yours has your cards in it.
# 2026-03-05
## Today
- C-007 | Stage the storm season email for segment-1 | queue/2026-03-05-email.md
- C-011 | Fill the local trades directory listing and leave the tab open | queue/2026-03-05-form.md
- C-012 | Verify the quote request conversion event fires on the thank you page | paid/conversion-quote-request.md
## Waiting on you
- queue/2026-03-05-email.md: three drafts, none ticked
- C-009 | Submit the supplier co-marketing listing | filled in its tab, the submit is yours
## Blocked
- gtm-signal-sweep, open since 2026-02-26: the review platform asked for a sign in, nothing entered
The full brief, with the run log and the ledgers beside it.
A folder of plain text files you can open and change. Nothing runs anywhere else.
gtm-engineer/
INSTALL-PROMPT.md what your agent reads to set itself up, once
ROLE.md who this employee is and how it thinks
SCHEDULE.md when each routine runs
RELEASES.md yours: the channels you have released, shipped empty
routines/<id>/SKILL.md one folder per routine
Each routine runs at its time, inside a window. If your machine was asleep and the job fires late or twice, it sees the work is done and does nothing.
Two guardrails. Shipped, every send, post, submit, publish and spend is held for your click, and RELEASES.md is where you hand a channel over. No AI Employee ever creates an account, enters a password, completes a captcha or accepts terms.
How employees work. The guardrails, routine by routine.
On a Claude Pro or Max plan, nothing beyond the plan. They spend a share of your plan's usage limits, not dollars. Measured on my own Max seat, the GTM Engineer's scheduled runs were about 6 percent of everything the machine sent to Claude. docs/COST.md has the method, the per routine table and the API key reference.
The eight are free for good. The Agent Ops Masterclass, the premium software library with a resale license, the live sessions and premium AI Employees as they ship live in the Agent Ops Club. A free club account gets you Masterclass Part 1 and its certificate, the session calendar and AI Employee updates.
Does it send anything? By default, no. It drafts, fills and stages, and you press the button. Windows, Mac or Linux? All three. Can I run just one? Yes, each is a self contained folder. Can I sell installs to clients? Yes, it is MIT; just do not call yours by the club's name. The rest is in docs/FAQ.md.
Routine requests, new employee proposals, harness reports and corrections from real runs are all welcome. Post what an employee did for your business in Discussions under Show and tell. CONTRIBUTING.md has the rules.
MIT. Copyright (c) 2026 Mark Fulton. LICENSE. Names and logos are not licensed, and forks get their own name: TRADEMARKS.md.
Built by Mark Fulton with Claude Code. Every contributor is in CREDITS.md. Report a way to make an employee send or spend through SECURITY.md, not a public issue.