competitive-strategy
Skill101 starsChanged 16 days agoMITView on GitHub
Builds customer-specific competitive positioning with supported differentiators, honest tradeoffs, objection responses, and claims to avoid. Use when a customer use case needs supported competitive positioning, comparison, objection handling, or discovery hypotheses, such as "position against this competitor", "answer this competitive objection", "compare options for this customer", "which competitive claims are safe to use", "build a battlecard for this deal", or "how do we beat this competitor here". DO NOT use for business-case or ROI modeling, a full meeting brief, generic product pitches, or unsupported competitor claims.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- RefoundAI/lenny-skillstheir own version, first seen Jul 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- RefoundAI/lenny-skills★ 1.3ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository294 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- accessibility-passSkill
- accounting-root-skillSkill
- budget-and-forecastSkill
- financial-presentationsSkill
- financial-statementsSkill
- journal-entrySkill
- reconciliationSkill
- tax-preparationSkill
- acroform-writerSkill
- action-items-todoSkill
- agent-evaluation-designerSkill
- agent-harness-explorerSkill
- agent-performance-triageSkill
- agent-rai-impact-assessmentSkill
- agent-red-teamSkill
- ai-demo-assistantSkill
- ai-first-process-redesignSkill
- ai-usecase-assessmentSkill
- anonymised-case-study-writerSkill
- answer-researchSkill
- b2b-outreach-suiteSkill
- blog-content-auditorSkill
- blog-post-structure-passSkill
- booth-loop-videoSkill
- brand-template-enforcerSkill
- brand-voice-passSkill
- breathing-roomSkill
- browser-uat-analystSkill
- business-case-composerSkill
- business-osSkill
- call-for-speakers-digestSkill
- campaign-deck-builderSkill
- cim-teardownSkill
- company-profile-packSkill
- comps-analysisSkill
- coverage-meeting-prep-debriefSkill
- dd-checklistSkill
- document-diligenceSkill
- earnings-noteSkill
- ic-memoSkill
- merger-modelSkill
- pitch-deck-skeletonSkill
- case-preparation-briefSkill
- case-triageSkill
- chart-builderSkill
- classic-text-adventureSkill
- coding-rationaleSkill
- document-deriveSkill
- handoff-draftSkill
- note-contextSkill
- quality-gap-checkSkill
- clipchamp-videoSkill
- clt-hr-assistantSkill
- commenting-contentSkill
- competitive-battlecard-builderSkill
- conditional-chat-reminderSkill
- conference-session-abstract-packSkill
- content-quality-auditorSkill
- copilot-agent-advisorSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 12 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Follow this skill's evidence, artifact, privacy, action-control, and outcome-reporting rules below.
- Distinctive: line 21
Use relevant supplied material or applicable tools and sources you are authorized to access.
- Distinctive: line 29
Never send confidential content to public search.
- Distinctive: line 61
Test whether the evidence is current, opportunity-specific, and sufficient for each claim.
- Distinctive: line 75
Do not fabricate competitor capabilities, pricing, customer preferences, win rates, or proof.
- Distinctive: line 107
Word (.docx): Default for reviewing positioning, objections, tradeoffs and the next move.
- Distinctive: line 108
Excel (.xlsx): Instead for maintaining a criterion-by-criterion claim comparison, with the strategy narrative retained.
- Distinctive: line 110
Markdown (.md): When requested or Office creation is unavailable or fails.
- Distinctive: line 112
Use authorized, format-specific workflows.
- Distinctive: line 116
Verify each save before reporting success and provide the actual links or locations.
- Distinctive: line 126
Not for generic market research with no customer decision context.
- Very specific: line 127
Not for a full business-case document.
- Distinctive: line 128
Never turn an inference into a competitor fact or use unapproved material as an approved claim.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Competitive Strategy
Follow this skill's evidence, artifact, privacy, action-control, and outcome-reporting rules below.
Domain: Sales.
Evidence and connectivity
Begin with authorized user-provided material and accessible work sources. Discover optional CRM capabilities at runtime and use them only to enrich or execute the job; never require a vendor, connector, record identifier, object name, or field name to begin when the minimum semantic evidence is otherwise available.
If CRM is unconfigured, unavailable, denied, stale, partial, or unsupported, continue with the supported baseline, disclose the affected scope, and block only the dependent conclusion or action. Distinguish an authorized empty result from failed or unexecuted retrieval. If no connected evidence source is available, ask for the minimum pasted facts or file needed for the next useful step and return a bounded framework or needs_input rather than inventing data.
Data Sources
Use relevant supplied material or applicable tools and sources you are authorized to access. These are options, not a mandatory checklist. Ask for missing essential input or context; unavailable evidence remains unknown, not negative evidence.
- Meeting Transcripts & Email for the customer's requirements, decision criteria and actual objections.
- Approved Competitive Intelligence for dated capabilities, tradeoffs and permitted proof or claim wording.
- Knowledge & Files for authorized product documentation, proof assets and claim-review rules.
- Record Snapshots & Exports for opportunity context and evidenced alternatives, not proof of customer preference.
- Public web for material public competitor facts missing internally; verify authority and claim approval before use.
Never send confidential content to public search. Preserve source authority, dates and privacy boundaries.
Purpose
Build an opportunity-specific competitive position that connects customer requirements and decision criteria to relevant, approved competitor evidence, honest tradeoffs, likely objections, and the next move.
Applicability
Applies when a selling context or customer use case is identifiable and the user needs to understand a named competitor, an explicit comparison set, or which competitive questions to investigate. When a competitor and approved evidence are available, build opportunity-specific positioning. When the competitor is unknown, produce discovery hypotheses and verification questions rather than asserting an incumbent or inventing a comparison. A missing opportunity summary or competitor association does not block a bounded discovery brief.
Usage situations
- "We are up against [competitor]. How should we position?"
- "Map our strengths to this customer's decision criteria."
- "Help me answer this competitive objection."
- "Which competitive claims are safe to use on this deal?"
Procedure
- Define the opportunity, competitor, decision stage, and business decision the strategy must influence. Distinguish an established target from a proposed selection. If a generic continuation leaves the opportunity or competitor unresolved, keep the positioning conditional or ask the minimum distinguishing question. Do not silently select a deal because it has richer records. Sufficient supplied context can establish the target without a CRM lookup; an evidenced build-versus-buy alternative need not be a named vendor.
- Assemble customer requirements, decision criteria, objections, stakeholder priorities, and known commercial constraints.
- Assemble approved competitor intelligence and directly observed competitor facts, preserving source and date.
- Separate approved intelligence, observed customer or competitor facts, and inference.
- Map each material customer criterion to relevant differentiation, weakness, tradeoff, proof, and objection response.
- Test whether the evidence is current, opportunity-specific, and sufficient for each claim; surface material conflicts rather than selecting the convenient source.
- Recommend a positioning approach, proof points to use, claims to avoid, and the next validation step.
Judgment
- Current, opportunity-specific evidence outranks generic or stale material. Generic intelligence can frame a question but cannot establish what this customer values.
- A differentiation matters only when it connects to a stated or strongly evidenced decision criterion. Product differences without customer relevance are background.
- Show strengths and weaknesses honestly. Explain the tradeoff rather than hiding a disadvantage behind generic messaging.
- An objection response is relevant only when it addresses the customer's actual concern and is supported by approved evidence.
- Do not fabricate competitor capabilities, pricing, customer preferences, win rates, or proof. If material sources conflict, state both positions and withhold the affected claim until resolved.
- Apply supplied organizational rules for approved intelligence and claim use. Without them, keep recommendations qualitative and identify claims that require review.
Output
Deliver both a concise chat summary and one saved primary editable artifact, following the sections below. The artifact must contain supported competitive positioning or a bounded discovery brief.
Chat summary
In chat, summarize the recommended competitive posture, the customer criterion that most shapes it, the strongest supported differentiator or tradeoff, the highest-risk claim or evidence gap, and the next discovery or validation move.
Artifact content
- Opportunity decision context and evidence scope.
- Customer requirement-to-positioning map.
- Recommended differentiators, proof points, objections, and honest tradeoffs.
- Source classification for material claims: approved intelligence, observed fact, or inference.
- Claims to avoid, conflicts, stale or missing evidence, and validation needs.
- Recommended next move and an optional reviewable draft when requested.
Artifact selection
Choose one format for the complete internal competitive strategy, respecting the user's requested format:
- Word (.docx): Default for reviewing positioning, objections, tradeoffs and the next move.
- Excel (.xlsx): Instead for maintaining a criterion-by-criterion claim comparison, with the strategy narrative retained.
- PowerPoint (.pptx): A separate customer-safe derivative only when requested and reviewed; keep the full internal strategy separate.
- Markdown (.md): When requested or Office creation is unavailable or fails; retain the full content and disclose fallback limitations.
Use authorized, format-specific workflows. Keep content concise and styling simple. Plan changes together and apply them in as few supported batches as practical. Update authorized existing artifacts without creating duplicates or changing unrelated content. Follow Delivery and control for saving and reporting.
Delivery and control
Verify each save before reporting success and provide the actual links or locations. If saving fails, disclose it and provide clearly labeled unsaved content in chat. Keep internal strategy separate from any requested customer-safe derivative.
Guardrails
Analysis, recommendation, and drafting require no approval. Creating and saving the requested file artifact in an authorized location is permitted. Creating or linking a competitor record, updating opportunity data, or sending competitive messaging requires separate, specific approval and any required internal authorization. Report proposed, approved, completed, and unconfirmed states separately.
When NOT to Use
- Not for generic market research with no customer decision context.
- Not for a full business-case document; use
business-case-composer. - Never turn an inference into a competitor fact or use unapproved material as an approved claim.
Required information
- Baseline: an identifiable selling context or customer use case. A named competitor or comparison set enables positioning; when absent, the deliverable is a discovery-hypothesis brief with claims withheld pending verification.
- Claim-ready comparison: at least one customer requirement, decision criterion, or objection plus approved or directly observed competitor evidence relevant to it.
- Broader scope: stakeholder priorities, decision stage, commercial configuration, proof assets, and dated opportunity evidence deepen the strategy. Their absence limits the claims that can be made rather than blocking the whole result.
- Missing-input question: "Which customer use case should I assess, and is there a competitor or comparison set?"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

