본문으로 건너뛰기
cccskills
무료GitHub에 공개

competitive-intelligence

Use when the user names a competitor, a battlecard, or win-loss, or asks how you win against someone: the CI brief with landscape, change blocks, pricing read, and win strategy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Competitive intelligence

Use this when the user names a competitor, a battlecard, or win-loss, or asks how you win against someone. Start from the competitors, what your product sells, and the decision the read informs. Gong call excerpts and win-loss notes, where they exist, are the quotes the win strategy rests on.

Set the tiered watch list first

Tier 1 direct competitors for a deep read, Tier 2 adjacent substitutes for a skim, Tier 3 aspirational for a monthly read. Each gets its pricing, changelog, product, and careers pages logged — including fetches that fail — plus review-site mining, competitor demo notes, and community chatter where they exist.

Read what changed

Group the changes by competitor and cite the link and date on each line. Keep to moves that matter: launches, pricing, messaging, positioning shifts. A competitor with nothing worth reporting is left out entirely, and an unlinked claim never makes the page.

Write the so-what

Two to four lines per material move, for this user's GTM job. A launch gets a positioning read, a pricing move gets a packaging read, a content push gets an enablement read. Say it is unclear when it is unclear.

Turn the read into win strategy

Three discriminators with proof, the competitor line the rep will hear, and the counter in rep register. Fold in win-loss quotes where they exist, quoted not paraphrased.

Build or refresh the battlecard

One page per competitor, scannable in under two minutes. Each card carries win/loss zones (where you win, where you battle, where you lose), the Know/Say/Show for the rep's exact words, scenario variants for head-to-head versus rip-and-replace (the pain of staying must outweigh the pain of switching), and a 90-day deal-intel pane with the latest win, loss, and at-risk quotes. Refresh on signal, never on schedule alone — changelog, pricing, review batches, exec changes, and earnings trigger a same-week versioned diff — with a biweekly floor for Tier 1 cards. Every card names its owner, last refresh, and approver; a card with no owner is retired until it has one.

What you hand back

The brief, saved dated with sources and a full source ledger including failures. A quiet market is one line saying so, not a brief. Never brief the same change twice — fold in what the routine already logged.

Fallbacks

No competitor list means you draft the watch list from the market and ask for a yes. No pricing pages means you say so and refuse the pricing read. Never pad the brief to look busy, and never invent a competitor move, a price, or a customer. Battlecards publish rep-wide only on the owner's explicit yes.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Write ad variants that each test one idea, within platform limits and supported claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Significant-Gravitas의 스킬 모두 보기

이 스킬의 문제 신고