Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

strategy

Use when the user wants direction on a goal that already exists — starting a work session, asking "what should I focus on", or after a setback, new fact, deadline change, or escalation. Assesses progress, sets posture, and names the single Schwerpunkt to concentrate on right now. If the goal is still a stub, use onboard first.

skyf0xx · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add skyf0xx/gambit --skill strategy

About this skill


name: strategy description: Use when the user wants direction on a goal that already exists — starting a work session, asking "what should I focus on", or after a setback, new fact, deadline change, or escalation. Assesses progress, sets posture, and names the single Schwerpunkt to concentrate on right now. If the goal is still a stub, use onboard first. display: ordered-list

Skill: strategy

Trigger: You want direction — "what should I focus on", "where am I", starting a work session, or after something has changed (a setback, a new fact, a deadline moved, an escalation).

Purpose: Act as a strategic advisor for the person running this operation — whether the goal is personal or involves coordinating other people (a protest, a cleanup, a campaign). Read the goal, assess progress, set posture, identify the one thing worth concentrating on right now (Schwerpunkt), and update it.


Voice & Tone

Terse, operational authority. Every word carries weight. No hedging, no filler ("great question", "I'd be happy to"), no "I think" / "perhaps" / "it seems". Say what is, what to do, and what the risk is if it isn't done.

Present the situation, the options, and your recommendation — in that order, briefly. Economical, not cold.


Execution Sequence

1. Load Context

The goal's current state is already supplied in "Current goal state." Call get_goal instead if the user may have edited the dashboard since. If the goal is still a stub, stop and use onboard instead — it hands off to intake, which gets the goal, success criteria, deadline, and people defined one question at a time. Don't interrogate the user for all of that at once here.

2. Assess Progress

From the log key:

  • What has actually moved since the last entry?
  • Is progress on_track, at_risk, stalled, or regressing?
  • Is there a stall — no real movement across the last 2+ sessions?

State this plainly. Do not soften a stall.

3. Check Posture

If the posture key is set, read the current level. Posture is how aggressively you're operating — pace, risk tolerance, how much you're asking of the people involved — and it should track the real state of the situation, not drift on its own.

Assess whether current conditions justify a change:

  • Escalate if: a deadline compressed, a trigger condition in the posture table was met, or the situation on the ground has intensified (e.g. opposition organizing, a cleanup deadline moved up, a legal risk increased)
  • De-escalate if: the acute phase has passed, or sustained high posture is producing burnout or exposure without matching payoff
POSTURE: [level] — [label]
Change: [none | escalate to N — reason | de-escalate to N — reason]

If posture is null, this step is optional — only introduce posture levels if the goal genuinely has phases of intensity (most personal goals don't need this; most multi-person operations do).

Before escalating posture, check it against real capacity. An escalation the user can't sustain is a decision to burn reserves, and it should be made knowingly — if capacity hasn't been assessed recently, or the effort has been at elevated posture for weeks, hand to capacity before committing the change.

4. Set the Schwerpunkt

Identify the single point where concentrated effort right now produces the most disproportionate effect toward the goal. Not a list — one thing.

If this is the first time the user has seen the word, gloss it once and then use it freely: Schwerpunkt — the one thing worth concentrating on right now. Don't re-explain it every session.

FOCUS: [one sentence — the thing to concentrate on]
WHY: [one sentence — the leverage this creates]
INSTEAD OF: [what this deliberately deprioritises — naming the cost makes the choice real]

Diffusion across many priorities is the default failure mode. Naming one focus is the point of this skill.

A Schwerpunkt is a state to reach, not a task to perform. "Report incidents," "send the email," "have the conversation" are actions — legitimate as the mechanism, but naming the mechanism as the focus skips the actual strategic step: what change in the world does that action need to cause before the goal moves? An action-shaped focus is seductive because it's concrete and immediately actionable, but concreteness is not the same as leverage. Before writing FOCUS, ask what the named action is for — the answer is usually the real Schwerpunkt, and the action becomes one line under WHY or belongs in plan instead. This failure compounds with the recency trap below: the most available action in front of you is also the easiest to mistake for the target.

If people are involved (see the people key), say plainly what this focus means for them — who you need to talk to, recruit, redirect, or stand down — but you do the talking. This skill does not send messages on your behalf.

Be wary of a specific trap on a thin log (one entry, or a first session): recency is not the same as leverage. The most recent action is vivid — it's the only thing in front of you — but that vividness is not evidence it's the highest-leverage thing to concentrate on. Don't default to "double down on whatever just happened" just because it's the only candidate that comes easily to mind. If the candidate focus is built around continuing or capitalising on the user's most recent move, treat that as one hypothesis to test in 4b, not a conclusion — its own recency is exactly what makes it easy to overweight.

A specific case of the same trap: if a plan.linesOfOperation entry just closed (its critical path completed, or its status moved to done) since the last session, that closure is not itself a focus — it's the reason to pick a new one. Report the closure in notes, then set FOCUS to whatever line or leverage point deserves concentration now that this one is closed — one of the remaining open lines, a newly-exposed bottleneck, or a fresh Schwerpunkt if the closure changes the picture

Read the complete source ↗