agentsclimarketplace
Sign in

Order of operations

Skill matt-bat/agent-command-center/skills/order-of-operations

Use only for explicit multi-step work with real dependencies, mixed or unsafe requested order, hidden prerequisites, or parallel branches that require sequencing. Do not activate for single-step tasks, routine command execution, or obvious local ordering.From its SKILL.md

Install
npx -y skills add matt-bat/agent-command-center --skill order-of-operations

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 395 tokens by cl100k_base, as published. Nobody here has run it

Order of Operations

Purpose

Convert an explicitly multi-step request into a dependency-correct, safe execution sequence while preserving user intent.

Core Rule

Prompt order is not automatically execution order. Reorder only when dependencies, safety, authorization, validation prerequisites, or rollback readiness require it.

If the requested order is valid, keep it. If it must change:

  1. use the smallest necessary reordering
  2. explain the reason briefly
  3. continue unless the change requires new authority or the user requested a pause

Sequencing Workflow

  1. Normalize the requested actions without adding scope.
  2. Identify each action's prerequisites, outputs, side effects, and validation needs.
  3. Build dependency edges only where one action truly relies on another.
  4. Separate the critical path from independent branches.
  5. Place authorization and irreversible-risk gates before their side effects.
  6. Run validation after the state it validates exists.
  7. Confirm every requested action is completed, deferred with agreement, or blocked with evidence.

Boundaries

  1. Do not invoke other skills solely because they are mentioned in a sequencing example.
  2. Do not create plans, trackers, project indexes, documentation, or governance artifacts solely because this skill activated.
  3. Do not introduce project-intake questions unrelated to the multi-step dependency graph.
  4. Do not use sequencing as permission to override a safe explicit user constraint.
  5. Stop for direction when a reordered step needs materially broader authority.

Conditional Reference

Read Sequencing Playbook only when the task needs a dependency graph, concurrency decision, validation staging, or conflict resolution beyond the core workflow.

Output

When sequencing is material, report:

  1. dependency-correct order
  2. meaningful reordering and reason
  3. validation gates and outcomes
  4. unresolved blocker or residual risk

For uncomplicated execution, keep the sequence internal and report only the outcome.

What ships with it: 1 file

2.3 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most operations skills give in 395 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • preserve user intent during reordering
  • use the smallest necessary reordering
  • explain the reason for a change briefly
  • normalize requested actions without adding scope
  • identify each action's prerequisites and side effects
  • build dependency edges only for true reliance

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.