Work Engine
Stand up a repeatable loop — brief in, deliverables out, results read, learnings folded back — for a recurring body of work, so it compounds instead of starting from scratch each time. Use to systematize anything done on a cadence. Works for any role.
Install
npx skills add DylXBT/claude-orchestrator-skills --skill work-enginegit clone --depth 1 https://github.com/DylXBT/claude-orchestrator-skills.git /tmp/claude-orchestrator-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-orchestrator-skills/work-engine ~/.claude/skills/work-enginePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Work Engine A one-off task is a prompt. A recurring body of work wants an **engine**: a brief goes in, deliverables come out, results get read, and what you learn folds back into your context so the next run starts further ahead. Run it on a cadence and it compounds. Role-agnostic: the engine could produce a content pack, a hiring shortlist, a design system update, a weekly ops report — ask what the user's recurring deliverable is. ## Step 1 — Interview 1. **What do you produce on a cadence?** The recurring deliverable, and how often. 2. **What goes into a run?** The brief — the inputs, goal, and constraints each time. 3. **What comes out?** The full set of deliverables a complete run should produce. 4. **How do you know it worked?** The signal/metrics you read afterward. ## Step 2 — Define the four moves Spell out the loop concretely for their work: ``` 1. BRIEF — what's dropped in to start a run (audience, goal, scope, deadline) 2. PRODUCE — the deliverables, ideally via a saved pipeline (see pipeline-builder) 3. REPORT — after it ships, the results turned into a short, shareable read-out 4. LEARN — what worked, folded back into the context brain for next time ``` Tie each move to something concrete in the user's world — real input names, real output formats. ## Step 3 — Wire it to the pieces
Details
- Skill name
work-engine- Repository
- DylXBT/claude-orchestrator-skills
- Path
work-engine/SKILL.md- License
- MIT
- Repo updated
- 2 June 2026
FAQ
What does the Work Engine skill do?
Stand up a repeatable loop — brief in, deliverables out, results read, learnings folded back — for a recurring body of work, so it compounds instead of starting from scratch each time. Use to systematize anything done on a cadence. Works for any role.
How do I install the Work Engine skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add DylXBT/claude-orchestrator-skills --skill work-engine. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Work Engine popular?
It lives in DylXBT/claude-orchestrator-skills, which has 114 GitHub stars and 1 forks.
Related skills
Connector Setup
114DylXBT/claude-orchestrator-skills
Plan a safe, least-privilege way to connect the user's real tools (Drive, Slack, a task board, a calendar, etc.) to Claude so it works from live data instead of copy-paste. Use when wiring up connectors/MCP. Works for any stack and any role.
Context Brain
114DylXBT/claude-orchestrator-skills
Build a reusable context pack (a "brain") so Claude reasons from the user's role, audience, voice, and standards every time, instead of generic output. Use when setting up a Project/workspace, or when output is on-topic but off-voice. Works for any role or domain.
Orchestrator
114DylXBT/claude-orchestrator-skills
Assemble the user's context brain, skills, connectors, and pipelines into one system they actually run end-to-end — and document it so a teammate could run it too. The capstone meta-skill. Works for any role.
胡希恕·经方临床
49jangviktor-web/huxishu
胡希恕(1898-1984)北京中医学院教授,经方临床家、教育家。 核心心智模型:六经来自八纲、方证是辨证的尖端、正邪交争、胃气为本。 决策启发式:发热恶寒辨阴阳、有汗桂麻、但见一证便是柴胡证、承气三阶、排除法辨半表半里。 触发词:「胡希恕」「胡老」「经方胡希恕」「六经八纲」「胡希恕怎么看」「方证对应」「伤寒论胡希恕」。 知识库覆盖:伤寒论398条全+金匮要略22篇+六经辨证诊断公式(16个)+方证鉴别速查+饮食调理思维模型(8个)+胡希恕核心讲稿38万字。 基于一手素材:胡希恕《伤寒论》与《金匮要略》讲座完整讲稿(中日录音增补版)。 版本:2026-08-22 V2.1(V4.4 三件套回填+索引修复+编码卫生检查)。
Wc Transfer Planner
200lyndonkl/claude
Plans between-round FIFA World Cup Fantasy transfers — budgets the round's free transfer(s), forces out players whose nation has been eliminated, chases fixture-swing drops, upgrades on value, and decides when a rebuild is large enough to fire the Wildcard instead of spending free transfers one at a time. Ranks candidate in/out pairs by EV gain over each player's remaining survival horizon (delta xEV weighted by progression_carry) MINUS transfer cost (a free transfer is cheap, a points hit is real, churning the squad for marginal swings is a critic flag), and tags forced/fixture/upgrade priori
Using Superpowers
49sodiumjoe/dotfiles
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.