Gingiris B2b Growth
Gingiris-1031/Competitor-analysis-tool
🇺🇸 B2B SaaS Growth — PLG vs SLG Playbook — Diagnose whether your problem is distribution, pricing, or PMF.
Win/loss analysis for B2B SaaS. An agent skill from growthack88/growth-marketing-os.
Install Win Loss Analysis
$ npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install growthack88/growth-marketing-os win-loss-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/growthack88/growth-marketing-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/community/win-loss .claude/skills/win-loss-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "win-loss-analysis" agent skill from https://github.com/growthack88/growth-marketing-os/tree/main/skills/community/win-loss into .claude/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/growthack88/growth-marketing-os/tree/main/skills/community/win-lossType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install growthack88/growth-marketing-os win-loss-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthack88/growth-marketing-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/community/win-loss .agents/skills/win-loss-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/growthack88/growth-marketing-os/tree/main/skills/community/win-loss into .agents/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install growthack88/growth-marketing-os win-loss-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthack88/growth-marketing-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/community/win-loss .cursor/skills/win-loss-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "win-loss-analysis" agent skill from https://github.com/growthack88/growth-marketing-os/tree/main/skills/community/win-loss into .cursor/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/growthack88/growth-marketing-os.git --path skills/community/win-loss--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install growthack88/growth-marketing-os win-loss-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthack88/growth-marketing-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/community/win-loss .gemini/skills/win-loss-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/growthack88/growth-marketing-os/tree/main/skills/community/win-loss into .gemini/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install growthack88/growth-marketing-os win-loss-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/growthack88/growth-marketing-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/community/win-loss .github/skills/win-loss-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/growthack88/growth-marketing-os/tree/main/skills/community/win-loss into .github/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install growthack88/growth-marketing-os win-loss-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/growthack88/growth-marketing-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/community/win-loss .opencode/skills/win-loss-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "win-loss-analysis" agent skill from https://github.com/growthack88/growth-marketing-os/tree/main/skills/community/win-loss into .opencode/skills/win-loss-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "win-loss-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
win-loss-analysis- GitHub stars
- 116
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,014 words
- Files
- 8 (incl. references)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Win/loss analysis for B2B SaaS. An agent skill from growthack88/growth-marketing-os.
- Works in 3 steps: Transcript processing — classify… → Pattern aggregation — group by outcome,… → Insight synthesis — state pattern,…
- Tasks that involve Meeting notes and agendas
- SKILL.md covers Claude Code triggers, Input requirements, Process and Core frameworks, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Win Loss Analysis is an agent skill from growthack88/growth-marketing-os. Win/loss analysis for B2B SaaS. Analyzes sales call transcripts across 6 dimensions (product, messaging, GTM/sales, pricing, competition, customer context) to extract why deals are won, lost, retained, or churned. Produces aggregate patterns with verbatim-quote evidence, frequency counts, confidence levels, and strategic recommendations. Includes process steps, output template, quality checklist, extraction patterns, and a worked 5-transcript example.
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/auto-update.md`, `references/example-analysis.md` and `references/extraction-patterns.md`).
It sits in Marketing & SEO, covering Meeting notes and agendas, Go-to-market strategy and Multi-tenancy. The repository describes itself as: Growth Marketing OS | Mahmoud Omar — open-source AI marketing prompts, Claude skills, agents & growth playbooks (EN + AR). The licence is MIT.
When your agent uses it
- Tasks that involve Meeting notes and agendas
- Tasks that involve Go-to-market strategy
- Tasks that involve Multi-tenancy
Example prompts
- “/win-loss-analysis”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Transcript processing — classify outcome, identify speakers, extract customer context, pull verbatim quotes for the 6 dimensions
- Pattern aggregation — group by outcome, count frequency, rank patterns (3+ mentions), cross-reference by ICP/competitor/persona
- Insight synthesis — state pattern, provide evidence with frequency + confidence, identify opportunity, generate executive summary
What it can do on your machine
Read from SKILL.md and the folder at commit c6b55c7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Win Loss Analysis loads about 2.5k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 118 tokens; SKILL.md has 1,014 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from growthack88/growth-marketing-os at commit c6b55c7, republished under its MIT licence (© growthack88). 1,014 words, ~2,537 tokens.
Download SKILL.mdSave it as
.claude/skills/win-loss-analysis/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- win-loss-analysis
- description
- Win/loss analysis for B2B SaaS. Analyzes sales call transcripts across 6 dimensions (product, messaging, GTM/sales, pricing, competition, customer context) to extract why deals are won, lost, retained, or churned. Produces aggregate patterns with verbatim-quote evidence, frequency counts, confidence levels, and strategic recommendations. Includes process steps, output template, quality checklist, extraction patterns, and a worked 5-transcript example.
- version
- 2.0
- author
- genesys-growth
- last_updated
- 2026-06-08
<!--
COMMUNITY SKILL — included under its original MIT license.
Source: https://github.com/matteotitta/genesys-skills by Matteo Titta (MIT).
License text: ../LICENSE-genesys-skills.txt
Curated into Growth Marketing OS by Mahmoud Omar (mahmoudomar.com) — this file
is NOT original work by the repo author; see /skills/community/README.md.
-->Win/loss analysis
Analyze sales call transcripts to extract actionable insights on why deals are won, lost, retained, or churned. Cross-reference findings with ICP, firmographics, and competitive context to produce strategic recommendations.
Knowledge type: win-loss-analysis
Maturity on first run: emergent → validated after team review
Claude Code triggers
Invoke when user says:
- "Win/loss analysis"
- "Analyze sales calls"
- "Why did we win/lose"
- "Churn analysis"
- "Retention analysis"
- "Sales call insights"
- "Deal outcome patterns"
- "Customer feedback synthesis"
- "Analyze these transcripts"
- "What patterns in our sales calls"
Do NOT invoke when:
- User wants general transcript analysis → use a generic transcript skill
- User wants competitor research → use
competitor-research - User wants a single customer interview write-up → use a transcript skill
- User wants sales enablement assets → use a sales-enablement skill
Input requirements
Required
| Input | Description | Source |
|---|---|---|
| Transcripts | Sales call transcripts with customer name and outcome | User provides |
| Outcome | Win/Loss/Retention/Churn for each call | User specifies or infer |
Optional (improve quality)
| Input | How it helps |
|---|---|
| Website URL per customer | Firmographics cross-reference |
| Product/ICP document | Define in-scope product capabilities |
| Market/GTM document | Positioning and competitive landscape |
| Sales notes column | Additional context (stage, deal size) |
| Competitor names | Pre-identify competitors to watch for |
Validation
Before proceeding: at least one transcript provided; outcome known or inferable from transcript; customer name identifiable.
If inputs are missing: ask the user for transcripts. Clarify if outcome should be inferred from transcript signals.
Transcript intake — normalize, redact, bind to evidence
Transcripts arrive in many shapes (Gong, Fireflies, Otter, Grain, Zoom/Avoma VTT, SRT, recorder JSON, or plain pasted text). Before Phase 1, normalize whatever you're handed into one shape — speaker-attributed turns with timestamps where present. Two rules apply to every transcript before analysis:
- Redact PII first. Mask end-client names, emails, and account numbers before processing; keep roles, company, and deal context. (Load-bearing for regulated industries.)
- Bind every claim to evidence. Every extracted pattern cites a verbatim quote plus the speaker; normalized, speaker-attributed turns make that attribution reliable.
Process
The analysis runs in 3 phases. Read references/process.md for the full step-by-step (4 transcript-processing steps, 4 aggregation steps, 4 synthesis steps, plus per-phase checkpoints and the process flowchart).
Phase summary:
- Transcript processing — classify outcome, identify speakers, extract customer context, pull verbatim quotes for the 6 dimensions
- Pattern aggregation — group by outcome, count frequency, rank patterns (3+ mentions), cross-reference by ICP/competitor/persona
- Insight synthesis — state pattern, provide evidence with frequency + confidence, identify opportunity, generate executive summary
Core frameworks
Analysis modes
| Mode | When to use | Output |
|---|---|---|
| Single call | Deep analysis of one transcript | Full insight extraction per dimension |
| Batch analysis | Multiple transcripts (3-20 calls) | Aggregated patterns with frequency counts |
| Comparison matrix | Win vs. loss OR retention vs. churn | Side-by-side pattern comparison |
Default to batch analysis mode when multiple transcripts are provided.
6 analysis dimensions
| # | Dimension | Win signals | Loss signals |
|---|---|---|---|
| 1 | Product | "Exactly what we need," feature praised | "Missing [feature]," "Doesn't do [X]" |
| 2 | Messaging | "Now I understand why this matters" | "What does it actually do?" |
| 3 | GTM/Sales | "You really understand our problem" | "Demo didn't address our needs" |
| 4 | Pricing | "Fair price," "good value" | "Too expensive," "over budget" |
| 5 | Competition | "Chose you over [competitor]" | "Going with [competitor]" |
| 6 | Customer context | "Need this now," deadline-driven | "No rush," "maybe next year" |
Confidence scoring
| Level | Definition | When to apply |
|---|---|---|
| High | 3+ calls with consistent pattern | Clear recurring theme |
| Medium | 2 calls or inferred from strong signals | Emerging pattern |
| Low | Single mention or indirect reference | Possible outlier |
Outcome classification
| Outcome | Definition | Key signals |
|---|---|---|
| Win | Deal closed, contract signed | "We're moving forward," pricing confirmed |
| Loss | Deal lost to competitor or no-decision | "Going with [competitor]," "Not right now" |
| Retention | Existing customer renewing/expanding | Renewal discussion, expansion |
| Churn | Existing customer leaving/reducing | Cancellation, "not getting value" |
Show full SKILL.md (412 more words)Show less
Output
Produce a single win/loss report markdown file. Template + iteration prompts library: references/output-format.md.
Pre-delivery quality checklist + worked example + anti-examples: references/quality.md.
Auto-update protocol (feedback signals, pattern detection, skill-update template): references/auto-update.md.
Anti-hallucination guardrails
- Quote verbatim. All insights must trace to specific transcript quotes.
- Never invent patterns. If a pattern appears in only one call, label it "Single mention — pattern unconfirmed."
- State frequency. Always note how many calls support each finding (e.g., "4 of 7 calls").
- Acknowledge gaps. If a dimension has no data, mark "Not discussed in transcripts."
- Distinguish roles. Tag who said what — prospect vs. sales rep vs. champion.
Gotchas
- Correlation as causation. Reports "deals with longer sales cycles were lost" as if cycle length caused the loss → always distinguish patterns from causes. Use "associated with" not "caused by".
- Small sample bias. Draws conclusions from 2-3 deals instead of waiting for sufficient data → flag sample size prominently. Minimum 5 wins and 5 losses for reliable patterns.
- Missing verbatim quotes. Summarizes what buyers said instead of extracting exact quotes → verbatim quotes are the primary deliverable. Summaries are secondary.
- Single-dimension analysis. Only looks at win/loss by competitor, missing dimensions like deal size, ICP segment, or sales cycle stage → cross-tabulate across at least 3 dimensions.
- Conflates product feedback with sales insights. Mixes "they wanted feature X" with "they didn't trust our team" → separate product gaps from sales execution issues. They feed into different downstream work.
Integration with other skills
| Skill | Relationship | Usage |
|---|---|---|
| transcript analysis | Related | Use for general transcripts, not sales calls |
| sales enablement | Downstream | Feed insights into battlecards and objection handlers |
| product messaging | Downstream | Update messaging based on win patterns |
| competitor research | Related | Cross-reference competitor mentions |
Reference files
| File | Purpose |
|---|---|
references/process.md | Full 3-phase step-by-step + flowchart |
references/output-format.md | Win/loss report template + iteration prompts |
references/quality.md | Pre-delivery checklist + worked example + anti-examples |
references/auto-update.md | Feedback signal detection + pattern rules |
references/extraction-patterns.md | Signal patterns for each dimension |
references/output-template.md | Legacy report template (kept for reference) |
references/example-analysis.md | Worked example with 5 transcripts |
Data integration
Level: 0 — Context (heavy pulls)
If you run win/loss inside a connected environment, pull transcripts and deal context fresh:
| Source | What to pull | When |
|---|---|---|
| Meeting recorder (Granola, Gong, Fireflies, etc.) | Sales call transcripts and deal discussions | Always |
| Team chat (Slack, etc.) | Deal discussion threads and competitive intel | Always |
Fallback (no integrations): user-provided call transcripts or recordings; manual deal review notes.
Changelog
| Version | Date | Changes |
|---|---|---|
| 2.0 | 2026-01-16 | Refactored to v2.0 template: structured phases, evidence-ready insights, iteration prompts, auto-update rules |
| 1.0 | Previous | Initial skill creation with 6 dimensions |
© growthack88, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in skills/community/win-loss of growthack88/growth-marketing-os.
- SKILL.md
- references/auto-update.md
- references/example-analysis.md
- references/extraction-patterns.md
- references/output-format.md
- references/output-template.md
- references/process.md
- references/quality.md
Open the folder on GitHubat commit c6b55c7
Compare with similar skills
Win Loss Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Win Loss Analysis this skillgrowthack88/growth-marketing-os | 116 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Gingiris B2b GrowthGingiris-1031/Competitor-analysis-tool | 110 | — | ~1.2k | Automated safety check: Pass | None | |
| Marketing PlanNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Jaredrhod Marketingjaredrhod/ai-marketing-skills | 282 | — | ~584 | Automated safety check: Pass | CC-BY-SA-4.0 |
Similar skills
Marketing Plan
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
Revenue Centric Design
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
Jaredrhod Marketing
jaredrhod/ai-marketing-skills
Run any marketing task the way jaredrhod actually runs it. An agent skill from jaredrhod/ai-marketing-skills.
Linkedin Employee Advocacy
sergebulaev/linkedin-skills
Stand up and run a LinkedIn employee advocacy program for a marketing or sales team.
More from growthack88/growth-marketing-os
All 13 skills in this repoMena Ads
growthack88/growth-marketing-os
MENA Ads Command Center — a complete paid-ads operating system for the Arab world (Egypt, KSA, UAE, GCC, Levant, North Africa) and global accounts.
Arabic Copy Localizer
growthack88/growth-marketing-os
Marketing copy localization skill that converts English marketing copy (ads, landing pages, emails, CTAs) into native Egyptian Arabic عامية — or GCC dialect on request — with natural English…
Benchmark Analyst
growthack88/growth-marketing-os
Marketing benchmark triage skill. An agent skill from growthack88/growth-marketing-os.
Cod Operations Analyst
growthack88/growth-marketing-os
COD (cash-on-delivery) e-commerce operations skill. An agent skill from growthack88/growth-marketing-os.
Conversion Copywriter
growthack88/growth-marketing-os
Direct-response copywriting skill. An agent skill from growthack88/growth-marketing-os.
Funnel Decomposition Analyst
growthack88/growth-marketing-os
Senior performance analyst skill that answers "why did sales drop (or jump)?" using rigorous funnel decomposition.
Related
Categories
Questions about Win Loss Analysis
What does Win Loss Analysis do?
Win/loss analysis for B2B SaaS. An agent skill from growthack88/growth-marketing-os. Win Loss Analysis is an agent skill from growthack88/growth-marketing-os. Win/loss analysis for B2B SaaS.
When should I use Win Loss Analysis?
Win Loss Analysis fits situations like: tasks that involve Meeting notes and agendas; tasks that involve Go-to-market strategy; tasks that involve Multi-tenancy.
How do I install Win Loss Analysis in Claude Code?
Run `npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a claude-code`. Or copy the skill folder (skills/community/win-loss in growthack88/growth-marketing-os) into .claude/skills/win-loss-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Win Loss Analysis in Codex?
Run `npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a codex`. Or copy the skill folder (skills/community/win-loss in growthack88/growth-marketing-os) into .agents/skills/win-loss-analysis in your project. Codex loads it when a task matches its description.
Can I use Win Loss Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add growthack88/growth-marketing-os --skill win-loss-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/win-loss-analysis, .gemini/skills/win-loss-analysis, .github/skills/win-loss-analysis and .opencode/skills/win-loss-analysis in your project.
What does Win Loss Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Win Loss Analysis is instructions for the agent only.
Does Win Loss Analysis access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Win Loss Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Win Loss Analysis use?
Win Loss Analysis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Win Loss Analysis use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Win Loss Analysis?
Skills that share tags, products or a category with Win Loss Analysis: Gingiris B2b Growth (Gingiris-1031/Competitor-analysis-tool, 110 stars), Marketing Plan (Nexus-JPF/note-companion, 870 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars) and Startup Design (ferdinandobons/startup-skill, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Win Loss Analysis?
growthack88 (a GitHub user) maintains it in growthack88/growth-marketing-os, which has 116 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 2, 2026.
Source: growthack88/growth-marketing-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.