improve-business
Guided journey from a stalled, plateaued business to one with an honest diagnosis, a working operating rhythm, and offers repriced to real value.
Install / Use
npx skills add wondelai/skills --skill improve-businessInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Data & AnalyticsSupported Platforms
Tags
Our assessment of improve-business
improve-business scores 87/100 on our quality scale, 396th of 604 Data & Analytics skills we index.
Its SKILL.md is 21 KB long, well organised into 17 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 2,248 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so improve-business is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
improve-business compared with similar skills
All 4 of these similar skills score higher than improve-business; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| improve-business (this skill)by wondelai | 87 | 2.2k | 2mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install improve-business?
- Run
npx skills add wondelai/skills --skill improve-business. The install tabs above show the steps for each supported agent. - Which AI agents does improve-business work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is improve-business safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is improve-business still maintained?
- The repository was last updated about 2 months ago, so improve-business is actively maintained.
Skill content
View source on GitHubname: improve-business description: 'Guided journey from a stalled, plateaued business to one with an honest diagnosis, a working operating rhythm, and offers repriced to real value. Orchestrates eight skills phase by phase - good-strategy-bad-strategy, traction-eos, high-output-management, team-topologies, drive-motivation, lean-analytics, negotiation, monetizing-innovation - asking the user questions at every decision point and recording results in the project docs/ folder (STRATEGY.md, OPERATIONS.md, METRICS.md, IMPROVE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a business that has plateaued, diagnose why growth stalled, tighten strategy and execution, re-motivate a team, or says ''revenue is flat and I do not know why''. Starting from scratch with no customers: use create-business. Once the fundamentals work and the goal is expansion: use grow-business. When the product itself drags the business down: use improve-app. For one framework in isolation, invoke that skill directly.' license: MIT metadata: author: wondelai version: "1.0.1"
Improve a Business
An interactive, resumable journey for a business that already runs but has stopped moving — real revenue, real customers, a flat line. Across eight phases it works the layers in order (strategy, execution, management, structure, motivation, metrics, margin, pricing), diagnosing before treating rather than chasing one tactic at a time. The agent asks before every decision and records each choice in docs/ so the turnaround survives across sessions.
Core Principle
A plateau is a diagnosis failure: diagnose before treating, and work the layers in order — strategy, execution, management, structure, motivation, metrics, margin, pricing. Poking one tactic at a time never breaks a plateau because the constraints compound. This skill sequences the phases, asks the decision questions, and records what was decided; the constituent skills carry the actual method — invoke them rather than improvising their frameworks.
Journey Map
| Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1 | good-strategy-bad-strategy | What single challenge is capping the business? | Creates docs/STRATEGY.md — GATE | | 2 | traction-eos | How do we execute the strategy every week? | Creates docs/OPERATIONS.md | | 3 | high-output-management | How does the operator multiply the team, not bottleneck it? | Extends docs/OPERATIONS.md | | 4 | team-topologies | Is the org structure itself the constraint? | Extends docs/OPERATIONS.md | | 5 | drive-motivation | Why has the team quietly checked out? | Extends docs/OPERATIONS.md | | 6 | lean-analytics | Which one number tells us the truth? | Creates docs/METRICS.md | | 7 | negotiation | Where are we leaking margin, and what do customers truly value? | Extends docs/CUSTOMER.md | | 8 | monetizing-innovation | Are we charging for the value we deliver? | Extends docs/OFFER.md |
Operating Rules
- Resume first. Before anything else, read
docs/IMPROVE-BUSINESS-PLAN.mdand every artifact in the Journey Map. If the tracker exists, summarize the journey state in 3-5 lines and ask which phase to enter. Done when the user has confirmed an entry point. A journey with a tracker is resumed, never restarted. - Intake on first run only. No tracker: run the Intake below, then create
docs/IMPROVE-BUSINESS-PLAN.mdwith every phase statusedpending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason. Done when the tracker exists and the user has confirmed the phase plan. - Phase entry. Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed / skip / defer — phases marked GATE may be deferred, never skipped. Mark the phase
in-progresson proceed. Done when the user chose. - Skill invocation and fallback. Load the phase's skill and use it: each phase's Invoke line names the skill by slug — use that skill to run the phase. If it is not available, offer:
npx skills add wondelai/skills/<slug> --global. If the user declines, run the phase from its Brief — the minimum viable method. State which mode you are in. - In-phase decisions. Ask every question under "Decide with the user" — with concrete options and your recommendation. Record the choice in the tracker's Key Decisions. A decision made silently is a defect.
- Phase exit. Present the draft artifact content for sign-off before writing. On approval: write or extend the docs/ files, update the tracker (status, Key Decisions, Next Actions). Done when the files are written and the phase row shows
done. - Artifact discipline. Read before writing; create a file only if missing, otherwise extend — add or update your sections, preserve everyone else's. Files are UPPERCASE in
docs/. Every recommendation lands as a checkbox or a table row with owner and priority. See references/artifact-templates.md when creating a docs/ file for the first time — create it from the full skeleton (all section headings), then fill the sections your phase names. - Diagnosis before treatment. No new initiative, reorg, or pricing change starts before
docs/STRATEGY.mdholds a written Diagnosis the user has confirmed. When asked to jump straight to Phase 4, 7, or 8, complete Phase 1 first (or confirm it is already done and recorded). Done when a confirmed Diagnosis exists before any treatment phase writes its artifact.
Intake
Ask these before creating the tracker:
- What is the plateau — flat revenue, rising churn, a team working hard with nothing moving? (Frames the Phase 1 diagnosis and the Phase 6 OMTM.)
- What passes for your current strategy today — a deck, OKRs, a goal list, nothing written? (Feeds Phase 1; if none exists the diagnosis work is larger.)
- How big is the team and how is it structured? (Sizes the Rocks and 1:1 system in Phases 2-3; gates Phase 4.)
- Do you run technology teams, or is this a services / brick-and-mortar business? (
team-topologiesis engineering-specific — skip Phase 4 for non-tech orgs.) - When was pricing last set, and on what basis — cost-plus, competitor, or value? (Gates Phase 8; cost/competitor pricing signals margin left on the table.)
- What is your sales win rate, and do you hear price objections? (Near-100% win rate with no pushback signals minivation — Phase 8.)
- Where does work get stuck — within teams or between them? (Between-team stalls point at Phase 4; within-team points at Phases 3 and 5.)
Phase-skip heuristics: skip Phase 4 when you don't run technology teams or teams already deliver cleanly; skip Phase 5 when morale is engaged and not the constraint; skip Phase 7 when no large renewals or vendor contracts are in play; skip Phase 8 only if pricing was recently repriced from validated willingness to pay.
Then create docs/IMPROVE-BUSINESS-PLAN.md from the template and confirm the phase plan. Done when docs/IMPROVE-BUSINESS-PLAN.md exists with every phase statused and the user has confirmed the plan.
Phases
Phase 1 — Diagnose the real challenge (good-strategy-bad-strategy) — GATE
Purpose: Name the single critical challenge capping the business, so every later layer works the right constraint. Phases 2-8 may not start before this Diagnosis is confirmed.
Brief (fallback): Good strategy has a kernel — an honest diagnosis of the critical challenge, a guiding policy, and coherent actions. Bad strategy is fluff, goals dressed as strategy, and forty "priorities" that concentrate nothing. Treat the funnel as a chain-link system and find the one binding link; investing in strong links is wasted until the weak one is fixed. Set a proximate objective close enough that the team can see how to hit it, and force a no-list.
Invoke: Use the good-strategy-bad-strategy skill with the current annual plan, OKRs, or deck pasted in. Ask
it to (a) audit the plan as strategy and score it 0-10, (b) write a proper kernel, (c) name the
binding chain-link constraint and one proximate objective for the quarter.
Decide with the user: Does the diagnosis name the real obstacle, not a symptom? Which single link (lead-gen / activation / retention / expansion) is the binding constraint, and what is the proximate objective? What goes on the no-list — what will you deliberately stop doing?
Artifact: Create docs/STRATEGY.md with ## Diagnosis (critical challenge + binding constraint), ## Guiding Policy (including the proximate objective), ## Coherent Actions (Action | Owner | Due | Status), and ## No-List. Update the tracker.
Done when: STRATEGY.md holds a confirmed Diagnosis, a Guiding Policy, 3-5 Coherent Actions with owners, and a No-List — only then are Phases 2-8 unlocked.
Phase 2 — Install an execution rhythm (traction-eos)
Purpose: Convert the strategy into a weekly operating rhythm that survives Monday.
Brief (fallback): Vision without traction is hallucination. Set 3-7 quarterly Rocks — each with one owner, SMART, binary (done or not, no partial credit) — aimed at the proximate objective. Install the Level 10 Meeting: same day and time, 90 minutes, fixed agenda ending in 60 minutes of IDS (Identify, Discuss, Solve) driven to root cause. Never cancel it.
Invoke: Use the traction-eos skill with STRATEGY.md's guiding policy and proximate objective. Ask for (a)
5-7 quarterly Rocks with owners and binary criteria, flagging any that are business-as-usual, (b) a
Level 10 agenda with time boxes, (c) an IDS pass on the top recurring issue.
Decide with the user: Which 5-7 Rocks make the quarter (cap at seven)? Who owns each? What weekly cadence for the Level 10, and who facilitates?
Artifact: Create docs/OPERATIONS.md with ## Vision/Traction Summary, ## Rocks (this quarter) (Rock | Owner | Binary done-condition | Status), and ## Meeting Cadence (Meeting | Rhythm | Agenda). Update the tracker.
Done when: OPERATIONS.md holds 5-7 owned binary Rocks tied to the proximate objective and a scheduled Level 10 cadence the user has committed to.
Phase 3 — Manage for output, not activity (high-output-management)
Purpose: Multiply the team's output by getting the operator off the critical path.
Brief (fallback): A manager's output equals the output of their organization plus the neighboring teams they influence. Negative-leverage habits — meddling, waffling, being the approval bottleneck — multiply downward. High-leverage tools: subordinate-owned 1:1s at a cadence set by task-relevant maturity (TRM), and delegation-with-monitoring — delegate what you know best, monitor at task level, sample deeper when TRM is low, lighter as it rises.
Invoke: Use the high-output-management skill with the operator's last two weeks of calendar and the tasks
they keep grabbing back. Ask for a leverage audit, a redesigned week built around forecasted key
events, and a 1:1 plus delegation system for direct reports.
Decide with the user: Which negative-leverage habits to cut? The 1:1 cadence per report (set by TRM, not seniority)? Which tasks to delegate-with-monitoring off the critical path?
Artifact: Extend docs/OPERATIONS.md: add ## Management Leverage (1:1 cadence per report, delegation decisions, monitoring depth). Update the tracker.
Done when: OPERATIONS.md records a 1:1 cadence for every direct report and at least one delegation decision that removes the operator as a bottleneck.
Phase 4 — Reshape teams around value streams (team-topologies)
Purpose: Remove structural friction when work keeps getting stuck between teams rather than within them.
Brief (fallback): Conway's law — you ship your communication structure. Reduce every team to one of four types: stream-aligned (the default), enabling, complicated-subsystem, platform. Cap cognitive load: at most one complicated domain per team; never split a singl
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
