用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/warpdotdev/competitive-intelligence-agent-oss --skill summarize-changelog命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 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/