LMTYdotcom / skills
git clone https://github.com/LMTYdotcom/skills.git
v1.0.0 · 22d ago
Agent Skills for competitive GTM work - battlecards, win-loss, positioning, pricing, launches, deal prep and sales enablement. Installs into Claude Code, Codex, Copilot CLI, Cursor, Gemini CLI and any Agent Skills client. Works standalone; uses live evidence when LMTY is connected.
—
stars, 24h
—
stars, 7 days
+82
stars, 30 days · #2,768
82
★ total
2
forks · 0 open issues
Star history starts 2026-10-20; the chart appears after the second daily snapshot.
LanguagePython
LicenseMIT
Created2026-09-28 (22d ago)
Last push18d ago
Watchers2
OwnerOrganization
GitHub topics
agent-skillsaiai-agentsbattlecardsclaudeclaude-codecodexcompetitive-intelligencecopilot-clicursorgemini-cligo-to-marketllmmcppmmpositioningproduct-marketingsales-enablementwin-loss-analysis
Links
- GitHub: github.com/LMTYdotcom/skills
- Homepage: https://lmty.com
- Releases · Issues · Hacker News mentions
README excerpt
# Competitive Skills by LMTY Use your AI assistant for competitive work you already do: researching competitors and market shifts, building positioning and messaging, reviewing pricing and launches, creating battlecards, preparing deals, analyzing wins and losses, and keeping sales enablement current. Add the pack once, then ask in plain English, "Give me this week's competitive briefing." Your assistant selects the matching skill and follows a repeatable method for completing the work. The skills work in Claude Code, ChatGPT and Codex, GitHub Copilot, Cursor, Gemini CLI and any assistant that supports Agent Skills; the pack itself is an Agent Plugin. Every skill works on its own. Connect LMTY and each one starts from your tracked competitors, kept current with what has changed and the evidence behind it, instead of a blank page. ## What you can ask | Skill | Ask something like | You get | | --- | --- | --- | | `competitive-market-briefing` | "Give me this week's competitive briefing." | A calm digest of what actually changed, and what to watch | | `competitive-deep-dive` | "Get me fully up to speed on Northwind." | One competitor, understood and evidenced | | `competitive-market-shift-analysis` | "Everyone is adding AI. Is this a real shift or just noise?" | A verdict: noise, one move, an emerging shift, or a new expectation | | `competitive-executive-market-brief` | "Board meeting Friday. What market changes could blindside me?" | What leadership must decide, with the uncertainty shown | | `competitive-positioning` | "Our competitors all sound like us now. Pressure-test our positioning." | A position tested against the alternatives buyers really consider | | `competitive-messaging-audit` | "Does our homepage still differentiate us?" | What still works, what went generic, what buyers would say instead | | `competitive-pricing-packaging-review` | "Northwind raised prices. What should we look at before changing ours?" | The market evidence a pricing decision needs, and the decision named | | `competitive-launch-readiness` | "Here's the PRD. What do I need to know before we launch?" | Whether it's parity, catch-up or real differentiation, and how to frame it | | `competitive-battlecard` | "Build a battlecard for us vs Northwind." | A card a rep can use with two minutes before a call | | `competitive-objection-response` | "The buyer just said Northwind is cheaper. What do I say?" | The facts checked, a response, and the question to ask next | | `competitive-deal-prep` | "Prep me for the Globex call tomorrow - we're up against Northwind." | One deal, prepared for the next meeting | | `competitive-poc-rfp-plan` | "We're going into a POC against Northwind. What should we prove?" | An evaluation planned around the criteria that will decide it | | `competitive-enablement-refresh` | "Northwind changed their pricing. What in our talk tracks is now wrong?" | The lines that changed, with proof and date | | `competitive-asset-audit` | "Audit our competitive m