소스 정보
- 저장소
- warpdotdev/competitive-intelligence-agent-oss
- 최근 소스 활동
- 2026년 7월 8일 15:39
- 감지된 SKILL.md 언어
- 영어
- 스타
- 0
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/warpdotdev/competitive-intelligence-agent-oss --skill summarize-changelog명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
| name | summarize_changelog |
| description | Does research on competitor's changelogs. |
Use your web search tool to create a summary of recent changelogs entries from competitors over the last 2 weeks. If there are any important themes in common, point them out.
Specifically, check these links for each competitor:
https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md https://cursor.com/changelog https://docs.factory.ai/changelog/cli-updates https://ampcode.com/chronicle https://github.com/sst/opencode/releases https://developers.openai.com/codex/changelog/ https://www.conductor.build/blog https://github.blog/changelog/?label=copilot&opened-months=2
YOU MUST INCLUDE YOUR PRODUCT'S CHANGELOG IN YOUR ANALYSIS
Review your product's changelog at YOUR_PRODUCT_CHANGELOG_URL and compare your recent changes in the same time periods to competitors. Keep in mind, you don't know what was shipped previously, so in your comparison, think about the things each of the teams have shipped in that period. USE THIS CHANGELOG AS THE SOURCE OF TRUTH FOR YOUR PRODUCT'S CHANGELOG, don't rely on other web searches.
Setup required: Replace
YOUR_PRODUCT_CHANGELOG_URLwith your product's public changelog URL. If the page is behind a CDN cache, usecurlwith cache-busting headers to fetch fresh content:curl -sL -H "Cache-Control: no-cache" -H "Pragma: no-cache" "YOUR_PRODUCT_CHANGELOG_URL?_=$(date +%s)"
Finally, deduplicate information. Search for previous summaries you did in the folder reports/competitor_changelog_reports/, and don't repeat changelog entries that have been covered previously. However, you can reference these reports to influence your summary and analysis.
In your summary, note the dates each feature was shipped. (e.g. is it a monthly or weekly release)
The summary should follow this format:
---BEGIN FORMAT---
Competitive Changelog Analysis - Last 2 Weeks (Date range) TL;DR: [Summary of changes]
[Competitor] (version number) -[Date][Feature description] -[Date][Feature description] -[Date][Feature description]
COMMON THEMES [common themes]
[YOUR PRODUCT] Comparison Shipped: Competitors: Opportunity:
RISKS
---END FORMAT---
And here is an example post (note: competitor entries are real; replace the [YOUR PRODUCT] section with your own changelog data):
---BEGIN EXAMPLE---
Competitive Changelog Analysis - Last 2 Weeks (Jan 13-27, 2026) TL;DR: Major industry push toward agent skills/customization, multi-agent collaboration, and image generation. Enterprise features expanding across all tools.
CURSOR (v2.3-2.4)
CLAUDE CODE (v2.1.x)
FACTORY (v0.42-0.52)
AMP
OPENCODE (v1.1.32-34)
CODEX (v0.90-0.92)
CONDUCTOR (v0.28-0.29)
COMMON THEMES
[YOUR PRODUCT] COMPARISON (Jan 7-21) Shipped: [list features your product shipped in this period] Competitors ahead on: [areas where competitors have shipped ahead of you] Opportunity: [gaps you could close or areas to differentiate]
RISKS
---END EXAMPLE---
Make sure to return your entire summary in the proper format to the requester, don't truncate it.
When you are finished, create a PR with the new report in the folder reports/competitor_changelog_reports/
Sets up the competitive-intelligence-agent from scratch — clones the repo (or works from an existing clone), installs dependencies, configures .env credentials, authenticates GitHub and Google, and replaces codebase placeholders with the user's real values. Use when asked to "set up this agent", "run the setup skill", "deploy this agent", "configure this repo", or when a user has just cloned the repo and wants it working.
analyzes customer feedback across Email, GitHub, NPS, and churn cancellations.
Analyzes git history from a repository to summarize recent development activity, features in progress, and engineering priorities. Use when asked about what the team is working on, recent code changes, development velocity, or to prepare for planning/roadmap discussions.
SOC 직업 분류 기준