Agent skills that help a small company ship, win its first users, and reach its first revenue.
Each skill replaces a specialist a small company can't afford to hire yet, and each is self-contained in its own folder: instructions, scripts, example config, and a real example of its output. They run on Claude Code, Claude Cowork, Codex, or anything else that reads files and runs a shell. State lives in files you own, not in a vendor.
Point your agent at this repo and name the skill:
Install the outbound-master skill from github.com/skyzer/skills and set it up.
For bounded Pi/DeepSeek coding delegation:
Install the delegate-wave skill from github.com/skyzer/skills and use it for this repository task.
delegate-wave uses a controller-worker model rather than delegating everything:
| Role | What it does |
|---|---|
| Codex or Claude: controller | Decomposes the task, makes architecture and product decisions, defines acceptance checks, reviews the diff, and owns commits, PRs, merges, and releases. |
| DeepSeek V4 Flash: default worker | Handles bounded discovery, mechanical implementation, and test generation through Pi. |
| DeepSeek V4 Pro: fallback worker | Handles a difficult, well-specified task only after Flash fails once or review finds a reasoning defect. |
This keeps expensive controller context focused on judgment while moving only explicit, verifiable work packets to a lower-cost worker.
That's the whole request. The agent fetches the named skill, reads its SKILL.md, and performs only the setup that skill declares. Everything an agent needs to know is in each skill's folder; nothing here assumes a human at a terminal.
Doing it by hand instead:
git clone https://github.com/skyzer/skills
cd skills/outbound-master
./install.sh
pip3 install -r requirements.txtdelegate-wave requires Python 3, Git, Pi 0.84.1 or newer, and a DeepSeek API key available through DEEPSEEK_API_KEY or Pi's native credential store. It has no Python package dependencies. Install it by linking or copying delegate-wave/ into ~/.codex/skills/delegate-wave or the equivalent skills directory for your agent.
| Skill | Function | What it does |
|---|---|---|
outbound-master |
Sales | Runs B2B cold outbound end to end: sources, scores, researches a dated hook, writes and deslops the copy, verifies every address, sends idempotently on a spaced schedule, tracks every touch in an append-only event log, and drafts replies a human approves. Refuses to send when it shouldn't. |
delegate-wave |
Engineering | Keeps Codex or Claude in control of decomposition, architecture, diff review, and release; delegates bounded discovery, mechanical implementation, and tests to DeepSeek Flash through Pi; and reserves DeepSeek Pro for difficult fallbacks. |
More coming. Each new skill lands as its own folder with the same shape.
If you're an agent asked to install or run a skill from this repo:
- Clone the repo and
cdinto the requested skill's folder. - Find and read its
SKILL.md. Some legacy skills keep it underskill/; standard skills keep it at the skill root. - Follow only the installation steps and dependencies that skill declares. Do not invent a generic setup sequence.
- Ask the operator for what only they have, and run any preflight before doing anything real.
- Respect the skill's guards. If a skill ships a dry-run mode, it starts on.
Configuration is separate from the engine. Everything about your company lives in config/, which is gitignored. Nothing in a skill names a company, market or product.
State is files, not chat. Anything needed on the next run exists on disk, because the conversation where you explained it is gone.
Nothing irreversible happens without a guard. Sends are idempotent, destructive actions are gated, and anything that spends money, reputation or a relationship stops and asks.
Skipping is free, being wrong isn't. Every skill would rather do nothing and say why than do something plausible and wrong.
Dry run first. If a skill touches the outside world, it has a mode that shows exactly what it would do and does nothing.
MIT.