Run any Skill in Manus with one click

so-what-sharpener

Stars2

Forks0

UpdatedJuly 1, 2026 at 11:57

This skill should be used when the user asks "what's the so-what here," "sharpen this insight," "this is just facts, what does it mean," or provides a list of observations or data points that need to be turned into insight statements.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

daddia

daddia/claude-for-strategy

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	so-what-sharpener
description	This skill should be used when the user asks "what's the so-what here," "sharpen this insight," "this is just facts, what does it mean," or provides a list of observations or data points that need to be turned into insight statements.
allowed-tools	Read, Grep, Glob
metadata	{"version":"0.3.0","owner":"consulting practice","review_cadence":"quarterly","work_shape":"narrative-synthesis","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"}

So-What Sharpener

When to use

Sharpen observations into insight via observation → implication → insight chain. Smallest Minto unit before full narrative.

What this skill does not do

Does not skip implication step — catches lazy insights.
Does not force insight on non-load-bearing facts — "No insight earned" section.
Does not build full pyramid — use narrative-builder for that.

Preconditions

Input	If missing
Observations or data points	Ask user to list
Decision context	Ask what decision insights must support

Provisional mode

Missing decision context: implications literal only; insights tagged [review].

Trust spine

Analytical Rigor (mandatory): Explicit three-step chain per point; merge redundant insights.
Per trust-conventions.md on tagged figures in observations.

Workflow

For each observation:

State observation unchanged.
State implication (literal).
State insight (so-what for decision).
Flag observations with no earned insight.
Group and merge overlapping insights.

Output format

Observation: [...]
  → Implication: [...]
  → Insight: [...]

No insight earned: [...]

Worked example

Input: "Mid-tier ARPU down 12% QoQ." Decision: pricing revert?

Excerpt: Implication: mid-tier spending less; Insight: increase likely priced out intended segment — reconsider pricing [review].

Quality checks before delivering

Three-step chain per point
No insight earned section when applicable
Overlaps merged

Propose profile update

When a stable convention surfaces during this run (thresholds, naming, tone, output format, or recurring corrections), propose a profile update: show the exact diff against ~/.claude/plugins/config/claude-for-strategy/consulting/CLAUDE.md (org-wide facts go to org-profile.md), ask for confirmation, and write only on yes. Only /consulting:practice-setup auto-applies a full profile write.

Outputs

Follows plugin CLAUDE.md § Outputs. Next: /consulting:narrative-builder to assemble insights.

More from this repository

same repository

auto-updater

daddia/claude-for-strategy

Check installed community skills for updates. Shows a diff and requires explicit approval before applying. Use when the user says "check for updates", "update my skills", "anything new for my installed skills", or when invoked from the registry-sync agent.

2026-07-012

practice-setup

daddia/claude-for-strategy

Engagement-profile interview that recommends and installs a starter pack of community strategy skills. This IS the practice setup for the whole ecosystem — it asks what kind of strategist you are and recommends what to install first. Use on fresh install, when the user says "get me started" or "what should I install", or to re-run the integration-availability check after adding or removing an MCP connector.

2026-07-012

skill-installer

daddia/claude-for-strategy

Install a community skill from a watched registry. Reads the allowlist first, fetches, shows the RAW SKILL.md (not just a summary), runs structural trust checks, runs skills-qa, and only writes files after explicit user approval. Use when the user says "install [skill]", picks install from browse, or provides a direct skill URL.

2026-07-012

skills-qa

daddia/claude-for-strategy

Evaluate a skill against the Strategy Skill Design Framework — thirteen design parameters (including trust-surface, freshness, schema validation, and conflict detection), three strategy-specific failure modes, and a three-band verdict (Ready / Some Concern / Material Concerns). Use when deciding whether to trust a community skill before installing it, before deploying a first-party skill to your team, or whenever the user asks "should I trust this?" or "is this skill well-designed?". Runs automatically as part of /strategy-builder-hub:skill-installer.

2026-07-012

allocate-resources

daddia/claude-for-strategy

This skill should be used when the user asks to "review our resource allocation," "are we funding the right things," "build a portfolio allocation view," or needs current spend, headcount, or management attention checked against strategic priority for misallocation.

2026-07-012

synergy-stress-test

daddia/claude-for-strategy

This skill should be used when the user asks to "stress-test these synergies," "is this deal's synergy case realistic," or has a deal or partnership's projected synergies that need cost/revenue separation, evidence checks, and a base-rate haircut.

2026-07-012

name	so-what-sharpener
description	This skill should be used when the user asks "what's the so-what here," "sharpen this insight," "this is just facts, what does it mean," or provides a list of observations or data points that need to be turned into insight statements.
allowed-tools	Read, Grep, Glob
metadata	{"version":"0.3.0","owner":"consulting practice","review_cadence":"quarterly","work_shape":"narrative-synthesis","permission_tier":"advisory","output_class":"draft-for-review","sourcing_policy":"volatile-facts-must-be-sourced"}

So-What Sharpener

When to use

Sharpen observations into insight via observation → implication → insight chain. Smallest Minto unit before full narrative.

What this skill does not do

Does not skip implication step — catches lazy insights.
Does not force insight on non-load-bearing facts — "No insight earned" section.
Does not build full pyramid — use narrative-builder for that.

Preconditions

Input	If missing
Observations or data points	Ask user to list
Decision context	Ask what decision insights must support

Provisional mode

Missing decision context: implications literal only; insights tagged [review].

Trust spine

Analytical Rigor (mandatory): Explicit three-step chain per point; merge redundant insights.
Per trust-conventions.md on tagged figures in observations.

Workflow

For each observation:

State observation unchanged.
State implication (literal).
State insight (so-what for decision).
Flag observations with no earned insight.
Group and merge overlapping insights.

Output format

Observation: [...]
  → Implication: [...]
  → Insight: [...]

No insight earned: [...]

Worked example

Input: "Mid-tier ARPU down 12% QoQ." Decision: pricing revert?

Excerpt: Implication: mid-tier spending less; Insight: increase likely priced out intended segment — reconsider pricing [review].

Quality checks before delivering

Three-step chain per point
No insight earned section when applicable
Overlaps merged

Propose profile update

Outputs

Follows plugin CLAUDE.md § Outputs. Next: /consulting:narrative-builder to assemble insights.