Agent skill

win-loss-report

Generate visual win/loss analysis reports as self-contained HTML with CSS-based charts and data visualizations.

activeSelf-containedInstructions only337 words

Filed under Calls, demos and discovery and Analytics and reporting.

From octavehq/lfgtm · 27 skill entries · 11 · pushed 2026-09-21

What it does when it runs

Generate visual win/loss analysis reports as self-contained HTML with CSS-based charts and data visualizations. Use when user says "win/loss report", "deal report", "visual analysis", or wants a formatted HTML version of deal outcome analysis. Do NOT use for text-based deal analysis — use /octave:win-loss-report instead.

Automated analysis of the skill and the 5 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply: None found.
Hosts it reaches: No third-party host appears in the skill or its bundled files.
Tool permissions it declares: No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files: None. Instructions only.

Our read

Computed from the artifact. Nothing here has been run, so none of it is a claim about how well the skill works — only about what it is and what it needs.

Maintenanceactive

Pushed within the last 30 days, with commits in the last 90.

CouplingSelf-contained

Nothing outside the agent is required.

Blast radiusInstructions only

No shell, no file writes, no network calls in the skill or its bundled files.

What it does to your systemsUnreviewed

The reading was not confident enough, or not yet confirmed, to publish.

Sends messages: No step found in the source
Writes records: No step found in the source
Spends credits: No step found in the source
Needs credentials: No key or connector found by pattern match

Read from source, not tested by running. Machine-read from SKILL.md at commit 6facb2c with jev-1.13.0; labels that write, send or spend were also checked against the cited line by a second reviewer. How this is read

Substancebrief

Under 600 words, no bundled reference files.

LicenceMIT

Permits redistribution with attribution, per the repository.

Ask about win-loss-report

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?Claude ChatGPT

Adapt it to my stackClaude ChatGPT

What else do I need for it to workClaude ChatGPT

Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗

git clone --depth 1 --filter=blob:none --sparse https://github.com/octavehq/lfgtm.git /tmp/lfgtm
git -C /tmp/lfgtm sparse-checkout set "skills/win-loss-report"
mkdir -p ~/.claude/skills/win-loss-report
cp -R "/tmp/lfgtm/skills/win-loss-report/." ~/.claude/skills/win-loss-report/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 27 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add octavehq/lfgtm
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from octavehq/lfgtm/blob/6facb2c00d93c48e29a370d3d93d52e4380f3b45/skills/win-loss-report/SKILL.md, which is licensed MIT (repository). 337 words, 5 headings.

/octave:win-loss-report - Visual Win/Loss Report Builder

Run the task

Read the task method before selecting context, claims, or output. It is the execution method for this skill. Supporting templates supply structure and styling; populate them from the task method and current evidence, not their illustrative figures or assertions.

Use a normalized close-date cohort and one metric model for text, cards and charts. Use four sections: cohort/outcome summary, drivers and counterevidence, segment/competitor comparisons, interventions to test. Observed loss associations do not establish preventable losses.

Use GTM context for strategic tasks and evidence and inputs for material claims and missing facts. A narrow list/get or a render-only handoff does not require unrelated research. Read host runtime for available tools, portable resource paths, routing, and review fallback.

Resolve current tool schemas before execution; use returned IDs and pagination. Inventory rows locate records; hydrate selected entities/resources before relying on their contents. Reuse supplied or inherited context and authorization. Ask grouped questions only for material unresolved inputs, continue independent work, incorporate replies, and recheck affected output.

Usage

/octave:win-loss-report [--period <timeframe>] [--segment <filter>] [--competitor <name>] [--style <preset>]

References by task

Read only the reference for the selected mode, then the format/layout references when rendering. Do not repeat intake or change approved claims when routing to a renderer.

Delivery and changes

Apply output readiness to text and artifacts. HTML also uses the review protocol and the matching format checks. A working preview can be shared with its status; unrun checks are NOT RUN. Reviewers return findings on an immutable version; one author applies edits and rechecks the final version.

For visual output, inherit the selected sender/workspace brand through brand kit usage; honor an explicit override and avoid repeated brand extraction. Public hosting requires the approved audience and publish manifest, followed by URL/access/link verification.

For comparisons, trends or rates, use the analytics contract. Only requested persistence loads workspace mutations; report changes as applied only after scoped readback.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

deal-review-win-loss by louisblythe · 159
win-loss-reason-extraction by louisblythe · 159
win-loss-reasons by pmalliance · 69
win-loss-analysis by matteotitta · 57
win-loss-program by NEON-Rutger · 48
win-loss-analysis by jbalbu01 · 15
win-loss-brief by zime-ai · 15
win-loss-decoder by varunk130 · 6

Need help setting it up?

This page tells you what win-loss-report does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.