Skill audit report
win-loss Audit report.
Analyses sales call transcripts (and churn or renewal calls) to find why deals are won, lost, kept or churned. Reads each call across six dimensions (product, messaging, sales process, pricing, competition, customer context), pulls verbatim quotes with the speaker named, counts how often each pattern appears, and writes findings with recommendations. Works with any recorder export or pasted text. Triggers: "win/loss analysis", "why do we lose", "why do we win", "analyse these sales calls", "lost deals", "churn analysis", "objection patterns". Feeds /positioning and /messaging. Not for general meeting summaries or competitor research (use /competitor-research).
OpenAgentSkill Trust Score
OpenAgentSkill Trust Score
The Trust Score helps an agent decide whether a skill is safe enough to shortlist before installation.
GitHub adoption
WARN48
63 GitHub stars
Stars/forks activity
WARN48
63 stars, 19 forks; issue activity unavailable in current metadata
Recent maintenance
PASS100
3d since push
License clarity
PASS86
MIT
README/SKILL.md completeness
INFO76
Public metadata needs stronger README/SKILL.md context
Dependency/runtime risk
PASS90
no major dependency risk hints in public metadata
Install availability
PASS92
npx skills add matteotitta/repo-structure-in-house --skill win-loss
Install command safety
PASS92
standard package or runtime install path
Permission surface
PASS86
filesystem or document access
Repository evidence
PASS86
https://github.com/matteotitta/repo-structure-in-house/tree/main/.claude/skills/win-loss
Review status
WARN46
AI review approval is missing
Agent Proven outcomes
INFO54
No agent outcome data yet
Checks
Install and adoption review
Install path
92
npx skills add matteotitta/repo-structure-in-house --skill win-loss
Repository
88
https://github.com/matteotitta/repo-structure-in-house/tree/main/.claude/skills/win-loss
License
86
MIT
Maintenance
100
3d since push
AI review
55
Review approval is missing
README/SKILL.md completeness
84
Usable description available
Dependency risk
90
no major dependency risk hints in public metadata
Install command safety
92
standard package or runtime install path
Permission surface
86
filesystem or document access
Stars/forks activity
48
63 stars, 19 forks; issue activity unavailable in current metadata
Adoption
68
63 GitHub stars
Warnings
- Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
- AI review approval is missing
- This skill may touch real-money trading, broker, wallet, or exchange operations; use only in a sandbox with explicit approval.
- Quality score needs review
- GitHub adoption: 63 GitHub stars
- Stars/forks activity: 63 stars, 19 forks; issue activity unavailable in current metadata
- Review status: AI review approval is missing
Method
This report combines public metadata, AI review output, repository freshness, install readiness, OpenAgentSkill events, quality scoring, trust checks, and the agent safety gate. It is not a full source-code security review.
Compare nearby options
Related skills to audit next
copy-editing
When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit,' 'this sounds like AI,' 'AI slop,' 'de-slop this,' or 'make it sound human.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. Every edit removes AI tells such as 'it's not X, it's Y' reveals, 'no X, no Y, no Z' lists, and sentences that trail into extra comma clauses. A request to fix one line gets a point edit that changes only that line. For writing new copy, see copywriting.
55K Stars · Audit report
free-tools
When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
55K Stars · Audit report
influencer-marketing
When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and vetting partners, structuring deals, briefing creators, disclosure compliance, and measuring ROI. Also use when the user mentions 'influencer marketing,' 'creator partnerships,' 'sponsorships,' 'YouTube sponsorships,' 'podcast sponsorships,' 'newsletter sponsorship,' 'newsletter ad,' 'sponsor a newsletter,' 'brand ambassador,' 'ambassador program,' 'creator program,' 'UGC creators,' 'tech UGC,' 'UGC creator program,' 'creator network,' 'B2B influencers,' 'thought leader ads,' 'gifting,' 'product seeding,' 'whitelisting creator content,' 'Telegram channel ads,' 'buy a post in a Telegram channel,' 'how much to pay an influencer,' or 'FTC disclosure.' For affiliate/referral payout mechanics, see referrals. For community-led advocacy, see community-marketing. For turning creator content into paid ads, see ad-creative.
55K Stars · Audit report