Ai changelog
Fetch the past week of changelog entries from Anthropic, Google Gemini, and OpenAI, generate a beautiful HTML dashboard, deploy it to Vercel, and return the URL. Use when the user says "差分", "diff", "changelog", "AI更新", "最近の変更", "AI changelog", "AI updates", "weekly AI news", or asks about recent changes from AI providers.From its SKILL.md
npx -y skills add yukihirop/nagi --skill ai-changelogAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.1 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it
AI Changelog — Weekly Summary
Fetch changelogs from Anthropic, Google Gemini, and OpenAI for the past 7 days, generate a styled HTML dashboard, deploy to Vercel, and return the live URL.
Step 1: Determine Date Range
echo "Today: $(date +%Y-%m-%d)"
echo "7 days ago: $(date -d '7 days ago' +%Y-%m-%d 2>/dev/null || date -v-7d +%Y-%m-%d)"
Use these dates to filter changelog entries.
Step 2: Fetch Changelogs
Anthropic
Use WebFetch to retrieve:
https://platform.claude.com/docs/en/release-notes/overview
This is static HTML. Parse the response for date-stamped sections and extract entries from the past 7 days. Look for date headings (e.g., "March 18, 2026") and their associated bullet points or descriptions.
If WebFetch fails, fall back to agent-browser:
agent-browser open "https://platform.claude.com/docs/en/release-notes/overview"
agent-browser wait --load networkidle
agent-browser snapshot
OpenAI
Use WebFetch to retrieve:
https://developers.openai.com/changelog/
This is a static Astro site. Parse the HTML for changelog entries with dates and descriptions. Filter to the past 7 days.
Do NOT use platform.openai.com/docs/changelog — it returns 403.
If WebFetch fails, fall back to agent-browser.
Google Gemini
This page is a JavaScript SPA and requires a browser. Use agent-browser:
agent-browser open "https://ai.google.dev/gemini-api/docs/changelog"
agent-browser wait --load networkidle
agent-browser snapshot
Extract changelog entries from the rendered page content. Filter to the past 7 days.
If agent-browser fails, try WebFetch as a fallback (some content may be in the initial HTML).
Step 3: Handle Missing Data
For each provider:
- If the page loads but no entries exist in the past 7 days → show "No updates this week"
- If the page fails to load entirely → show "Could not fetch updates" with a subtle error style
- If ALL three providers fail → report the error to the user and do NOT deploy
Step 4: Generate HTML
IMPORTANT — 言語: 日本語で生成すること
サイト全体を日本語で作成してください。英語で書かないでください。
- タイトル: 「AI更新情報」または「AIチェンジログ」
- 日付表記: 「2026年3月15日〜3月22日」形式
- セクション見出し、ボタン、フッターすべて日本語
- 更新内容の説明も日本語に翻訳(元が英語でも)
Create a single index.html file with all CSS inlined. The design should be:
Layout:
- Dark header bar with title "AI Changelog" and the date range (e.g., "Mar 15 – Mar 22, 2026")
- Three provider sections, each with a colored header card
- Entries displayed as cards within each section, grouped by date
- Footer with "Generated on [timestamp]"
Brand colors:
- Anthropic:
#D97757(coral) - OpenAI:
#000000(black) - Google Gemini:
#4285F4(blue)
Design philosophy — use ui-ux-pro-max skill:
Before writing any HTML, generate a design system using the ui-ux-pro-max skill:
python3 skills/ui-ux-pro-max/scripts/search.py "dashboard dark mode editorial news" --design-system -p "AI Changelog"
Apply the generated design system (typography, colors, effects) to the HTML output.
Additional requirements for this dashboard:
- Provider brand colors must be preserved:
- Anthropic:
#D97757(coral) - OpenAI:
#000000(black) - Gemini:
#4285F4(blue)
- Anthropic:
- Use staggered fade-in animation on page load
- Hover effects on cards with provider-colored glow
Layout guidelines:
- Responsive: max-width container, stacks on mobile
- Each entry card shows: date badge, title, description
- If an entry has a link, make the title clickable
Source links (important):
- Each provider section header must include a link to the original changelog page:
- Anthropic:
https://platform.claude.com/docs/en/release-notes/overview - OpenAI:
https://developers.openai.com/changelog/ - Gemini:
https://ai.google.dev/gemini-api/docs/changelog
- Anthropic:
- Style the link as a subtle "View original changelog →" button or text link next to the provider name
- Individual entries should also link to their specific page if the original changelog provides per-entry URLs
Keep it concise: Summarize long descriptions. The page should be scannable.
Step 5: Deploy to Vercel
Use the mcp__vercel__vercel_deploy tool:
mcp__vercel__vercel_deploy({
name: "ai-changelog",
files: [
{ file: "index.html", data: "<the full HTML string>" }
]
})
No projectSettings needed — Vercel will serve it as a static site.
Step 6: Return Result
Respond to the user with:
- The deployed URL
- A brief summary: how many updates were found per provider
- Any providers that were unavailable
Examples
Example 1: 全プロバイダー取得成功
ユーザー: ai changelog
回答:
AI更新情報をデプロイしました!🎉
🔗 **URL:** https://ai-changelog-xxx.vercel.app
📋 **今週のまとめ(2026年3月16日〜23日)**
| プロバイダー | 件数 | 主なアップデート |
|---|---|---|
| 🟠 Anthropic | 2件 | Models API に能力フィールド追加 |
| ⚫ OpenAI | 1件 | gpt-5.3-chat-latest モデルスラッグ更新 |
| 🔵 Google Gemini | 3件 | OpenAI互換機能拡張 |
Example 2: 一部プロバイダー取得失敗
ユーザー: 差分
回答:
AI更新情報をデプロイしました!🎉
🔗 **URL:** https://ai-changelog-xxx.vercel.app
📋 **今週のまとめ(2026年3月16日〜23日)**
| プロバイダー | 件数 |
|---|---|
| 🟠 Anthropic | 2件 |
| ⚫ OpenAI | ⚠️ 取得失敗 |
| 🔵 Google Gemini | 1件 |
```
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most readme changelog skills give in ~1.6k tokens
Counted across 472 of the 478 authors here whose files we hold, read 2026-08-07
- Follow the keep a changelog formatin 31 of 472, across 26 files
- Run from the git repository rootin 20 of 472, across 7 files
- Save output directly to CHANGELOG.mdin 20 of 472, across 7 files
- Group commits into logical categoriesin 19 of 472, across 6 files
- Review the generated changelog before publishingin 19 of 472, across 6 files
- Omit empty sectionsin 19 of 472
- Apply changelog guidelines and brand voicein 18 of 472, across 5 files
- Exclude internal commits like refactoring and testsin 18 of 472, across 5 files
- Specify date ranges for focused changelogsin 17 of 472, across 4 files
- Convert technical commits into customer languagein 17 of 472, across 4 files
- Provide a migration guide for breaking changesin 15 of 472, across 10 files
- Group commits by conventional commit typein 13 of 472
Said here and by no other author read
- Calculate the date range for the past week
- Fetch changelogs from each provider
- Filter changelog entries to the past seven days
- Generate HTML dashboard entirely in Japanese
- Run the UI design system generation script
- Apply generated design system to the HTML
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.