New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Workflow Work

by nabeelhyatt in nabeelhyatt/coworkpowers

Execute a knowledge work plan efficiently while maintaining quality.

MITAuto-check passed

Install Workflow Work

skills CLI
$ npx skills add nabeelhyatt/coworkpowers --skill workflow-work -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nabeelhyatt/coworkpowers workflow-work --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nabeelhyatt/coworkpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/workflow-work .claude/skills/workflow-work && rm -rf skills-src

Use ~/.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/

Facts

Skill name
workflow-work
GitHub stars
114
Token cost
~1.2k tokens
SKILL.md length
627 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Execute a knowledge work plan efficiently while maintaining quality.

  • Works in 4 steps: Quick Start → Execute → Quality Check → …
  • Requests like execute the plan
  • SKILL.md covers Process, Execution Principles, Work Patterns by Type and Next Step, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workflow Work is an agent skill from nabeelhyatt/coworkpowers. Execute a knowledge work plan efficiently while maintaining quality. Use after the research phase to systematically work through a plan using the right agents for each step. Triggers on requests like 'execute the plan', 'draft that email we planned', 'go ahead and write', or when moving from planning to execution.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Superpowers for knowledge work in Claude Code. The licence is MIT.

When your agent uses it

  • Requests like execute the plan
  • Draft that email we planned
  • Go ahead and write
  • Moving from planning to execution

Example prompts

  • “execute the plan”
  • “draft that email we planned”
  • “go ahead and write”
  • “/workflow-work”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Quick Start
  2. Execute
  3. Quality Check
  4. Present Output

What it can do on your machine

Read from SKILL.md and the folder at commit 65a1fb7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

Workflow Work loads about 1.2k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 627 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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 nabeelhyatt/coworkpowers at commit 65a1fb7, republished under its MIT licence (© nabeelhyatt). 627 words, ~1,218 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-work/SKILL.md (or your agent's skills folder).
name
workflow-work
description
Execute a knowledge work plan efficiently while maintaining quality. Use after the research phase to systematically work through a plan using the right agents for each step. Triggers on requests like 'execute the plan', 'draft that email we planned', 'go ahead and write', or when moving from planning to execution.
disable-model-invocation
true

Work: Knowledge Work Execution Workflow

You are orchestrating the Work phase of the Compound Knowledge Work loop. Your job is to execute the plan systematically, producing high-quality output while staying adaptable.

The work itself should be straightforward if planning was thorough. If you find yourself struggling, the plan may need revisiting.

Process

Phase 1: Quick Start
  1. Read the plan completely. If a plan file exists, read it. If the plan was discussed in conversation, review it.
  2. Create a task list from the plan's steps using TaskCreate.
  3. Identify the right agent mindset for each step:
Work TypePrimary Agent
Writing communicationsexecutive-writer
Data analysisanalyst
Structuring decisionsdecision-architect
Meeting preparationmeeting-orchestrator
Coaching conversationcoach
Task executiontask-executor
  1. Check prerequisites. Does any step need user input before you can proceed?
Phase 2: Execute

Work through each step in order. For each step:

  1. Mark the task as in-progress.
  2. Apply the right agent mindset for the work type.
  3. Use the context from planning. Don't re-research what was already gathered.
  4. Validate as you go:
    • Does this align with the stated goals?
    • Does this account for the stakeholder considerations?
    • Does this respect the constraints identified?
    • Would the user be surprised by anything here?
  5. Flag blockers immediately. If you need user input, ask. Don't guess on important details.
  6. Mark the task as complete when done.
Phase 3: Quality Check

Before presenting output to the user:

  1. Self-review against success criteria from the plan.
  2. Run the review agents specified in the plan (see Review workflow).
  3. Check for completeness - did you address everything in the plan?
Phase 4: Present Output

Present the completed work to the user with:

  1. The deliverable itself (email draft, analysis, decision memo, etc.)
  2. Key decisions you made during execution and why
  3. Anything that deviated from the plan and why
  4. Suggested next steps or review areas
  5. Ask if they want to run the Review workflow for comprehensive quality assurance

Execution Principles

Ship Complete Work
  • Don't present half-finished output
  • If a piece isn't ready, say so and explain what's needed
  • Complete means it addresses all success criteria
Follow the Plan, Adapt as Needed
  • The plan is your guide, not a straitjacket
  • If new information emerges, adjust
  • Document any deviations and rationale
Show full SKILL.md (246 more words)Show less
Continuous Validation
  • Check alignment with goals at each step
  • Don't wait until the end to discover misalignment
  • Ask the user to validate early if stakes are high
Right Level of Polish
  • Match polish to the audience and purpose
  • Internal draft != board presentation
  • Don't over-polish low-stakes work

Work Patterns by Type

Communications
  1. Draft using executive-writer mindset
  2. Apply tone appropriate to audience and relationship
  3. Front-load the key message
  4. Include clear call to action
  5. Check against stakeholder map from planning
Decisions
  1. Structure using decision-architect mindset
  2. Present options with explicit tradeoffs
  3. Include clear recommendation with rationale
  4. Document assumptions and uncertainties
  5. Provide implementation notes for chosen option
Analysis
  1. Analyze using analyst mindset
  2. Separate findings from interpretation
  3. State confidence levels explicitly
  4. Include "so what" for each finding
  5. Lead with executive summary
Meetings
  1. Prepare using meeting-orchestrator mindset
  2. Build timed agenda with clear objectives
  3. Prepare discussion guides and questions
  4. Anticipate likely discussion paths
  5. Create pre-read materials if needed
Coaching
  1. Engage using coach mindset
  2. Lead with questions, not answers
  3. Surface assumptions and beliefs
  4. Challenge respectfully
  5. Capture insights and commitments

Next Step

When work is complete, run the quality review: /coworkpowers:workflow-review

Anti-Patterns to Avoid

  • Starting execution without reading the full plan
  • Re-researching what was already gathered in planning
  • Guessing at important details instead of asking
  • Over-polishing before getting user feedback
  • Deviating from the plan without noting why
  • Presenting output without self-review

© nabeelhyatt, MIT. 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 skills/workflow-work of nabeelhyatt/coworkpowers.

Open the folder on GitHubat commit 65a1fb7

Compare with similar skills

Workflow Work 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.

Workflow Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Work this skillnabeelhyatt/coworkpowers114—~1.2kAutomated safety check: PassMIT
Executealirezarezvani/claude-skills28k—~831Automated safety check: PassMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Wiki Maintaineropenclaw/openclaw392k1 repos~462Automated safety check: PassMIT
Obsidian Vault Maintaineropenclaw/openclaw392k2 repos~262Automated safety check: PassMIT
Openclaw PR Maintaineropenclaw/openclaw392k—~2.2kAutomated safety check: PassMIT

Similar skills

  • Execute

    alirezarezvani/claude-skills

    /cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.

    28k GitHub stars~831 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Debugging Executions

    n8n-io/n8n

    Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Wiki Maintainer

    openclaw/openclaw

    Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

    392k GitHub starsUsed in 1 repo~462 tokens
    Knowledge ManagementAuto-check passed

  • Obsidian Vault Maintainer

    openclaw/openclaw

    Maintain an Obsidian-friendly memory wiki vault with wikilinks, frontmatter, and official Obsidian CLI awareness.

    392k GitHub starsUsed in 2 repos~262 tokens
    Knowledge ManagementAuto-check passed

  • Openclaw PR Maintainer

    openclaw/openclaw

    Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

    392k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Ulw Execute

    code-yeongyu/oh-my-openagent

    Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents.

    70k GitHub stars~6.3k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from nabeelhyatt/coworkpowers

  • Workflow Compound

    nabeelhyatt/coworkpowers

    Extract and store learnings from completed knowledge work to make the next task easier.

    114 GitHub stars~2.2k tokensUpdated 7 mo ago
    Auto-check passed

  • Workflow Research

    nabeelhyatt/coworkpowers

    Research and plan a knowledge work task thoroughly before execution.

    114 GitHub stars~2.2k tokensUpdated 7 mo ago
    Auto-check passed

  • Workflow Review

    nabeelhyatt/coworkpowers

    Run parallel multi-agent review on completed knowledge work.

    114 GitHub stars~1.3k tokensUpdated 7 mo ago
    Auto-check passed

Questions about Workflow Work

What does Workflow Work do?

Execute a knowledge work plan efficiently while maintaining quality. Workflow Work is an agent skill from nabeelhyatt/coworkpowers. Execute a knowledge work plan efficiently while maintaining quality.

When should I use Workflow Work?

Workflow Work fits situations like: requests like execute the plan; draft that email we planned; go ahead and write; moving from planning to execution.

How do I install Workflow Work in Claude Code?

Run `npx skills add nabeelhyatt/coworkpowers --skill workflow-work -a claude-code`. Or copy the skill folder (skills/workflow-work in nabeelhyatt/coworkpowers) into .claude/skills/workflow-work in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Work in Codex?

Run `npx skills add nabeelhyatt/coworkpowers --skill workflow-work -a codex`. Or copy the skill folder (skills/workflow-work in nabeelhyatt/coworkpowers) into .agents/skills/workflow-work in your project. Codex loads it when a task matches its description.

Can I use Workflow Work 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 nabeelhyatt/coworkpowers --skill workflow-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-work, .gemini/skills/workflow-work, .github/skills/workflow-work and .opencode/skills/workflow-work in your project.

What does Workflow Work need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflow Work is instructions for the agent only.

Does Workflow Work 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 Workflow Work 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 Workflow Work use?

Workflow Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Work use?

About 1.2k tokens (SKILL.md is roughly 4.9k 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 Workflow Work?

Skills that share tags, products or a category with Workflow Work: Execute (alirezarezvani/claude-skills, 28k stars), Debugging Executions (n8n-io/n8n, 207k stars), Wiki Maintainer (openclaw/openclaw, 392k stars) and Obsidian Vault Maintainer (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Work?

nabeelhyatt (a GitHub user) maintains it in nabeelhyatt/coworkpowers, which has 114 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on February 15, 2026.

Source: nabeelhyatt/coworkpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.