Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Strategy

ASecurity

Routes to the right strategy skill for any adversarial or competitive reasoning situation. Triggers: 'how do I beat X', 'competitive strategy', 'outmaneuver', 'I'm up against', 'position myself', 'what's my play here', any situation involving competitive pressure, adversarial dynamics, negotiation, or resource-constrained contest.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Strategy?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-strategy/badge)](https://www.skillsdirectory.com/skills/rondoflow-strategy)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: strategy
description: "Routes to the right strategy skill for any adversarial or competitive reasoning situation. Triggers: 'how do I beat X', 'competitive strategy', 'outmaneuver', 'I'm up against', 'position myself', 'what's my play here', any situation involving competitive pressure, adversarial dynamics, negotiation, or resource-constrained contest."
---

# Strategy

Sun Tzu's central insight: "The victorious warrior wins first and then goes to war, while the defeated warrior goes to war first and then seeks to win." Strategy is what happens before the contest. It is the discipline of creating conditions — position, intelligence, timing, alliances — so that when the contest begins, the outcome is already determined.

The strategy skills in this category draw on Sun Tzu (*The Art of War*), Clausewitz (*On War*), Miyamoto Musashi (*Book of Five Rings*), and competitive theory. They are not about aggression. They are about reading competitive contexts clearly and acting with economy, intelligence, and timing.

---

## Your Process

Read the user's situation carefully. Identify which strategic challenge is primary, then present the options below — briefly and specifically — and ask which fits. Execute immediately on selection.

**Framing check:** Confirm the competitive situation before continuing. State what you've identified — the actor, the opponent or competitive pressure, and the primary objective at stake — in one sentence, then use `AskUserQuestion`:
- **Question:** "I'm reading this as: [your one-sentence framing of the actor, the adversarial dynamic, and the goal]. Is that right?"
- **Header:** "Framing"
- **Options:**
  - **Yes — proceed** — framing is correct
  - **Adjust** — one element is off; user will correct it before you continue
  - **Reframe** — different situation than read; incorporate the correction before proceeding

**Reading the landscape — where should I compete, and where should I avoid?**
→ `/strategy-terrain` — Maps available positions, identifies favorable and dangerous ground, tells you which battles are worth fighting.

**What do I actually know, and what am I assuming?**
→ `/strategy-intelligence` — Audits what you know vs. what you're assuming about yourself and your opponent. Closes the intelligence gaps that cause strategic failures.

**When should I act — now, or wait?**
→ `/strategy-timing` — Analyzes conditions favoring action vs. patience. Reads your opponent's rhythm. Identifies trigger conditions for the right moment.

**How do I do more with less — I'm outgunned?**
→ `/strategy-force-economy` — Finds the minimum intervention that achieves the objective. Identifies leverage points where a small input creates a large output.

**How do I create a position that's hard to attack?**
→ `/strategy-positioning` — Builds the conditions for unassailability before the contest. What must be true for a rational opponent to choose a different arena?

**What should I reveal vs. conceal — information asymmetry?**
→ `/strategy-deception` — Manages information asymmetry in legitimate competitive contexts. Protects your position; identifies what your opponent may be concealing from you.

**What does winning actually mean here?**
→ `/strategy-victory` — Defines victory before the contest begins. Prevents the pyrrhic trap: winning in ways that lose the larger goal.

**Who do I need on my side — coalition and alliance?**
→ `/strategy-alliance` — Maps parties, identifies natural allies and swing parties, assesses alliance stability. Alliances built on shared interest vs. goodwill alone.

---

## Routing Confirmation

After diagnosing, use `AskUserQuestion` before routing:
- **Question:** "My read: this is a [type] situation — [one sentence why]. Run `/[sub-skill]`?"
- **Header:** "Direction"
- **Options:**
  - **Yes — run `/[sub-skill]`** — diagnosis is correct
  - **Show all options** — list all eight sub-skills with one-line descriptions
  - **Different angle** — describe which aspect of the competitive situation is most pressing

Adapt [type], [why], and [sub-skill] based on the primary strategic challenge identified.

---

## Output Format

Present the 3–4 most relevant options for the user's specific situation (not all eight every time). For each option, one sentence on why it fits. Ask which they want. Execute immediately on selection without further preamble.

---

## Notes

If the objective itself is unclear, start with `/strategy-victory` — you cannot select terrain, timing, or force economy without knowing what winning means. If the situation is genuinely complex, terrain is usually the right first move: it establishes the ground on which all other choices operate.

Strategy skills are for competitive and adversarial contexts. For purely cooperative situations where parties share objectives, the decision and systems categories are more appropriate.

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →