What makes Situational Leadership notable?

1K downloads. Trust evidence available

How should Situational Leadership be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Situational Leadership

Activate when: user says 'my management style isn't working for this person', 'I don't know how much to delegate', 'my top performer is disengaged', 'my new... Skill: Situational Leadership Owner: deciqai Summary: Activate when: user says 'my management style isn't working for this person', 'I don't know how much to delegate', 'my top performer is disengaged', 'my new... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T18:16:09.293Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/situational-leadership.json) v1.0.4 | 2026-07-09T11:

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.0k

Updated

Oct 11, 2026

Version

1.0.5

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.5release · observed Jul 16, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:situational-leadership

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-deciqai-situational-leadership/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

122,864 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: situational-leadership
description: "Activate when: user says 'my management style isn't working for this person', 'I don't know how much to delegate', 'my top performer is disengaged', 'my new hire is struggling without guidance', 'should I give him more autonomy?', or asks how to lead/manage a specific person on a specific task.
  Do NOT activate when: the performance issue is an incentive misalignment (reward structure is wrong — use principal-agent instead); the organization is in acute crisis requiring uniform command and all debate is suspended. More: deciqai.com/c/situational-leadership"
---

# Situational Leadership

## Overview

Match your leadership style to each person's development level on each specific task — cycling through four styles (Directing, Coaching, Supporting, Delegating) as competence and commitment evolve. Introduced by Hersey & Blanchard (1969); formalized as SLII by Blanchard, Zigarmi & Zigarmi (1985).

Core diagnostic: instead of "what kind of leader should I be?" ask "what does this person need from me on *this task* right now?" Failure to update style as the person grows is the most common cause of high performers disengaging.

Composes with: `kotter-change` for org-level transformation (Kotter = org sequence; this = each individual relationship); `principal-agent` to rule out incentive problems first; `okr-goal-setting` to set goals (OKR) then govern how to support each person toward them.

## When to Use

- A manager-report relationship has **friction or underperformance** and root cause is undiagnosed
- A **high performer is disengaging** ("I'm being micromanaged", "no room to grow") — signature of D4 receiving S1
- A **new hire or person in a new role** is struggling despite effort — signature of D1/D2 receiving insufficient structure
- A **task or technology change** resets development levels for experienced people
- **AI adoption resets who's the expert** — after rolling out AI coding tools / AI-native workflows amid the 2024–2026 AI capex race, a senior person is D1/D2 on the new tool even while D4 on the core work
- You are making a **delegation decision** for a specific person on a specific task

**When NOT to use:** incentive misalignment (principal-agent problem); acute crisis requiring uniform command; task is too vague to name (diagnosis requires a specific task).

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** user has a specific person and task → run The Process directly.
- **Coach mode:** user is unfamiliar or asks "what is situational leadership?" → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. One-line what-it-is: there's no single best management style — what works depends on how much the person knows and how confident/motivated they feel on *this task*. The manager's job is to match style to that, and update as the person grows.
2. Check fit: is there a specific person and spec

_meta.json

{
  "ownerId": "kn754b8sk22s8c6gjxt02bftbn88q7ye",
  "slug": "situational-leadership",
  "version": "1.0.5",
  "publishedAt": 1784225769293
}

references/sources.md

# Sources — situational-leadership

> *Primary sources for the [situational-leadership](../SKILL.md) skill.*

- Hersey, P. & Blanchard, K.H. (1969). "Life Cycle Theory of Leadership." *Training and Development Journal*, 23(5), 26-34. The original publication introducing the situational leadership framework with the foundational claim that no single style is universally effective.
- Blanchard, K., Zigarmi, P., & Zigarmi, D. (1985). *Leadership and the One Minute Manager.* William Morrow. The SLII formalization with the four development levels and four leadership styles; the "unequal treatment of unequals" formulation. ISBN 978-0688038250.
- Hersey, P., Blanchard, K.H., & Johnson, D.E. (2012). *Management of Organizational Behavior: Leading Human Resources.* 10th ed. Pearson. The comprehensive academic treatment of situational leadership including the empirical basis and cross-cultural applications. ISBN 978-0132556408.
- Garvin, D.A. (2013). "How Google Sold Its Engineers on Management." *Harvard Business Review*, 91(12), 74–82. Documents Project Oxygen's empirical findings — the behavioral evidence that style flexibility produces better team outcomes than style consistency. https://hbr.org/2013/12/how-google-sold-its-engineers-on-management
- Blanchard, K. & Johnson, S. (1981). *The One Minute Manager.* William Morrow. The popular companion to SLII; provides accessible descriptions of the three tools (goal setting, praising, redirecting) that implement S1/S2/S3/S4 behavior. ISBN 978-0688014292.

- GitHub (2024–2025). "GitHub Copilot" product documentation and adoption announcements. github.com. Supports the 2024–2026 example: GitHub's public reporting that Copilot is among its most rapidly adopted developer products and reached broad use across professional development teams (GitHub reported ~20 million all-time users by mid-2025) — the industry shift that resets task-level development levels for experienced engineers. https://github.com/features/copilot
- Stack Overflow (2024). *2024 Developer Survey* — AI section. survey.stackoverflow.co. Documents that a large majority of professional developers were using or planning to use AI coding tools in their workflow by 2024, corroborating the AI-native-team leadership context. https://survey.stackoverflow.co/2024

**What is not cited and why:** The frequently cited claim that "SLII has trained over 15 million managers" comes from the Ken Blanchard Companies' marketing materials, not from independently verified research. Claims about specific percentage improvements in retention or performance in SLII-trained teams are from corporate training evaluations without peer review. This skill grounds its empirical support in Google's Project Oxygen (Garvin 2013), which is documented in a peer-reviewed academic outlet, rather than in training vendor effectiveness claims.

examples/google-project-oxygen-2009.md

# Method in Action: Google's Project Oxygen (2009)

> *Example for the [situational-leadership](../SKILL.md) skill.*

In 2008, Google's People Analytics team launched Project Oxygen to answer a question the company's engineering culture resisted: do managers matter? The initial hypothesis among many Google engineers was that technical skill was sufficient and management was unnecessary overhead.

Project Oxygen analyzed performance data, feedback surveys, and management behavior data from more than 10,000 Google manager-employee pairs. The result — published internally in 2009 and referenced in Garvin (2013) — identified eight behaviors that distinguished the highest-rated managers from the lowest.

The alignment between Project Oxygen's findings and Situational Leadership is striking:

**Oxygen Behavior 1: "Be a good coach."** In Situational Leadership terms: apply S2 behavior (high directive + high supportive) to people in the D2 development state. The Oxygen analysis found that the highest-rated managers invested in explaining the "why" and building skills — not just assigning tasks.

**Oxygen Behavior 2: "Empower your team and don't micromanage."** In Situational Leadership terms: apply S4 behavior (delegating) to D4 individuals. The failure mode Project Oxygen found: senior engineers receiving S1 behavior from managers who either didn't trust them or defaulted to directive behavior out of habit.

**Oxygen Behavior 7: "Have a clear vision and strategy for the team."** In Situational Leadership terms: S1 behavior applied at the strategic level, ensuring D1 individuals (new hires, new role assignments) have clear direction.

**Oxygen Behavior 8: "Have key technical skills so you can help advise the team."** In Situational Leadership terms: competency as the foundation for credible S2 coaching — a manager cannot coach what they do not understand.

The Project Oxygen findings confirmed Situational Leadership's core premise empirically: the managers who produced the best team outcomes were not those who used one style consistently, but those who adapted their behavior to what each team member needed. The lowest-performing managers showed two failure modes: uniform S1 (micromanagement regardless of competence) or uniform S4 (abandonment of people who needed support).

Results documented in Garvin (2013): teams with the highest-quality managers (top quartile) showed approximately 20% lower turnover, approximately 30% higher performance ratings, and approximately 27% higher employee satisfaction scores compared to teams with the lowest-quality managers (bottom quartile).

Primary source: Garvin, D.A. (2013). "How Google Sold Its Engineers on Management." *Harvard Business Review*, 91(12), 74–82. https://hbr.org/2013/12/how-google-sold-its-engineers-on-management

examples/leading-ai-native-teams-2024-2026.md

# Method in Action: Leading AI-Native Engineering Teams (2024–2026)

> *Example for the [situational-leadership](../SKILL.md) skill.*

Between 2024 and 2026, AI coding assistants (GitHub Copilot, Cursor, Anthropic's Claude Code, and similar tools) moved from novelty to a standard part of many software teams' daily workflow. GitHub has publicly described Copilot as one of its most rapidly adopted developer products, and by 2024–2025 it was in broad use across professional development teams (GitHub reported roughly 20 million all-time users by mid-2025). This created a leadership problem that Situational Leadership diagnoses cleanly: **the introduction of a fast-moving new tool resets development levels, so yesterday's expert becomes today's novice — even as the tool keeps changing under them.**

A recurring 2024–2026 pattern: a senior engineer with a decade of experience is genuinely D4 on the team's core language and architecture, but D1 on "getting reliable output from an AI agent on our codebase" — a task that did not exist two years earlier and whose best practices shift with each model release. Managers who read seniority as a global development level (S4 everywhere, because "she's senior") watch strong engineers quietly struggle with the new tooling and blame themselves. The skill's own warning applies directly: *never assess development level globally — always for a specific named task.*

Walking a concrete case through **The Process**:

**1. Define the task precisely.** Not "Priya's performance" but: *Priya (staff engineer, 9 years, deep in the payments service) on the task of using an AI coding agent to ship features in that service — writing effective prompts, reviewing AI-generated diffs, and knowing when to abandon the agent and code by hand.*

**2. Assess competence** on *this* task. Knowledge: low — she has read about the tools but has little hands-on model of where they fail. Skill: low — her first attempts produced plausible-looking but subtly wrong diffs she over-trusted. Track record: none on this specific task. **Overall: low.** (Note the split: on the payments service itself, her competence remains high. This is the engineering-team error the skill flags — treating technical seniority as a proxy for all tasks.)

**3. Assess commitment** on this task — asked directly, not inferred. Motivation: mixed; she sees the upside but resents "prompting a tool" after a decade of hard-won mastery. Confidence: low, and privately worried the shift devalues her expertise. Engagement: variable. **Overall: variable-to-low.** Assessment method: conversation, not observation — because from the outside her frustration could be misread as disengagement or resistance.

**4. Determine development level.** Low competence with low/wavering confidence and motivation is **D2** (the disillusioned learner), not D1. The commitment dip — driven by identity threat, not laziness — is the distinguishing signal. *Stop-rule reminder: had the assessment been ambigu

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.