Game Informer — news by section
Official per-section RSS feeds (RSS 2.0). Each section has its own URL — do not guess categories from the all-in-one feed when the user wants the usual overview.
Feed URLs (use fetch)
Use https://www.gameinformer.com/… (or https://gameinformer.com/… — both work).
| Section | URL |
|---|
| --------- | ----- |
| News | https://www.gameinformer.com/news.xml |
| Reviews | https://www.gameinformer.com/reviews.xml |
| Previews | https://www.gameinformer.com/previews.xml |
| Features | https://www.gameinformer.com/features.xml |
All recent content (no section split): https://www.gameinformer.com/rss.xml — use only when the user explicitly wants one combined feed, not the four blocks below.
XML (per item)
Typical fields: </code>, <code><link></code> (canonical article URL), <code><pubDate></code>, <code><description></code> (often long HTML), optional <code><dc:creator></code>.</p><ul><li>Use <strong>exact</strong> <code><title></code> and <code><link></code> from the <strong>same</strong> <code><item></code>.</li><li><strong>Do not</strong> paste raw HTML from <code><description></code>; at most a <strong>very short</strong> plain-text teaser if you strip tags safely — otherwise <strong>title + link only</strong>.</li></ul><h2>Which feeds to load</h2><table><thead><tr><th>User intent</th><th>Fetches</th></tr></thead><tbody><tr><td>-------------</td><td>---------</td></tr><tr><td>Generic: Game Informer / GI / “what’s new” / headlines overview</td><td><strong>All four</strong> section feeds (<code>news</code>, <code>reviews</code>, <code>previews</code>, <code>features</code>) — <strong>four</strong> separate <code>fetch</code> calls</td></tr><tr><td>Only news / reviews / previews / features</td><td>Only the matching <code>.xml</code> URL(s)</td></tr><tr><td>Explicitly “everything in one list” / main RSS only</td><td><code>rss.xml</code> only (single section in the reply is OK)</td></tr></tbody></table><h2>Response — section layout (only non-empty feeds)</h2><p>Language: <strong>English</strong> for headings and any prose.</p><p>Include a <code>###</code> section <strong>only</strong> when that feed was <strong>loaded successfully</strong> and you are listing <strong>at least one</strong> <code><item></code> from it.</p><p><strong>Do not</strong> output a section that has no items — no headings like <code>### Reviews</code> with “No reviews available”, “Nothing in the feed”, or <em>(Feed unavailable.)</em>. If you did not fetch that URL or the XML has no items, <strong>omit</strong> that section entirely.</p><p>If several section feeds have items, use headings in this <strong>order</strong> (skip any that you omit): <strong>News → Reviews → Previews → Features</strong>.</p><p>Example when only <strong>News</strong> has data (e.g. only <code>news.xml</code> was fetched):</p><pre><code>## Game Informer
### News
1. **[Title from news.xml](exact-link-from-item)**
2. …
</code></pre><p>Example when <strong>News</strong> and <strong>Reviews</strong> both have data:</p><pre><code>## Game Informer
### News
1. **[Title](url)**
### Reviews
1. **[Title](url)**
</code></pre><p>Rules:</p><ul><li><strong>Blank line</strong> after each <code>##</code> / <code>###</code>.</li><li><strong>Numbered lists</strong> under each included section; default <strong>3–5</strong> items per section unless the user asks otherwise.</li><li>Put the URL <strong>only</strong> in the title: <code><strong><a href="url" target="_blank" rel="noopener">Title</a></strong></code> — no separate <code>Link:</code> line.</li><li>A story from <code>news.xml</code> appears <strong>only</strong> under <strong>News</strong>; same for reviews/previews/features. <strong>Never</strong> list a reviews feed item under News.</li></ul><h2>Mandatory</h2><p>Non-negotiable checklist (single-file skill — everything lives in this README):</p><ol><li><strong>Sections map to feeds:</strong> <strong>News</strong> = <code>news.xml</code>, <strong>Reviews</strong> = <code>reviews.xml</code>, <strong>Previews</strong> = <code>previews.xml</code>, <strong>Features</strong> = <code>features.xml</code>. Items may appear <strong>only</strong> under the section whose feed they came from.</li></ol><ol><li><strong>Overview questions:</strong> If the user does not restrict to one topic, <strong>fetch all four</strong> URLs (four separate <code>fetch</code> calls) before answering — when the runtime allows multiple fetches.</li></ol><ol><li><strong>Reply shape — omit empty:</strong> Output <code>### News</code> / <code>### Reviews</code> / <code>### Previews</code> / <code>### Features</code> <strong>only</strong> for feeds you actually loaded <strong>and</strong> that contain <strong>at least one</strong> item you list. <strong>Forbidden:</strong> empty sections, “No reviews available”, “Nothing in the current feed”, or similar placeholders for a feed you did not populate from XML.</li></ol><ol><li><strong>Order:</strong> Among sections you <strong>do</strong> include, use this order: News, then Reviews, then Previews, then Features.</li></ol><ol><li><strong>Items:</strong> Title and URL must be from the <strong>same</strong> <code><item></code>. Use <strong><code></strong><a href="url" target="_blank" rel="noopener">title</a><strong></code></strong>. No invented stories. Default <strong>3–5</strong> items per <strong>included</strong> section unless the user specifies another count.</li></ol><ol><li><strong>Language:</strong> Reply in <strong>English</strong>.</li></ol><ol><li><strong>Descriptions:</strong> Do not dump HTML from <code><description></code>; title + link is enough unless a short plain teaser is clearly safe.</li></ol><h2>Errors</h2><p>If all fetches fail, say so — do not invent headlines.</p><h2>When to use</h2><p>Game Informer, GI, gaming news from Game Informer, reviews/previews/features from the site, “latest Game Informer stories”.</p></div>
</div>
</div>
<div id="tab-versions" class="detail-content">
<div class="detail-section">
<h2>版本历史</h2>
<p style="margin-bottom:12px;font-size:14px;color:#94a3b8;">共 2 个版本</p>
<ul class="version-list">
<li>
<div>
<span class="version-tag">v1.0.1</span>
<span style="font-size:11px;color:#5b6abf;margin-left:8px;background:#eef0ff;padding:1px 8px;border-radius:10px;">当前</span> </div>
<div style="font-size:12px;color:#94a3b8;">
2026-05-21 13:29 安全 安全 </div>
</li>
<li>
<div>
<span class="version-tag">v1.0.0</span>
</div>
<div style="font-size:12px;color:#94a3b8;">
2026-05-07 19:50 安全 安全 </div>
</li>
</ul>
</div>
</div>
<div id="tab-security" class="detail-content">
<div class="detail-section">
<h2>安全检测</h2>
<div class="sec-grid"> <div class="sec-card">
<h4>腾讯云安全 (Keen)</h4>
<div class="sec-status sec-safe">
安全，无风险 </div>
<a href="https://tix.qq.com/search/skill?keyword=7be7c27f30bbf187a91503f0477db3df" target="_blank">查看报告</a> </div>
<div class="sec-card">
<h4>腾讯云安全 (Sanbu)</h4>
<div class="sec-status sec-safe">
安全，无风险 </div>
<a href="https://static.cloudsec.tencent.com/html-report-v2/2026/05/26/449157_5275773efbf9e2db3e567a79b3478d85.html?q-sign-algorithm=sha1&q-ak=AKID8JMG1bzBC1dz96qNhssfFftujT1NCoFi&q-sign-time=1782188574%3B1813724574&q-key-time=1782188574%3B1813724574&q-header-list=host&q-url-param-list=&q-signature=c467d17e067a4ff93698bfc48f009ab5e2b4402f" target="_blank">查看报告</a> </div>
</div>
</div>
</div>
<!-- Recommended Skills -->
<div style="margin-top:24px;">
<h2 style="font-size:18px;font-weight:600;margin-bottom:16px;">🔗 相关推荐</h2>
<div class="rec-grid">
<div class="rec-card">
<span class="badge-cat" style="margin-bottom:8px;display:inline-block;">data-analysis</span>
<h3><a href="/s/data-analysis">Data Analysis</a></h3>
<div class="rec-owner">ivangdavila</div> <div class="rec-desc">{"answer":"数据分析与可视化。查询数据库、生成报告、自动化电子表格，将原始数据转化为清晰可行的见解。适用于：(1) 您……"}</div>
<div class="rec-stats">
<span style="color:#f39c12;">★ 210</span>
<span style="color:#5b6abf;">📥 68,848</span>
</div>
</div>
<div class="rec-card">
<span class="badge-cat" style="margin-bottom:8px;display:inline-block;">data-analysis</span>
<h3><a href="/s/openclaw-tavily-search">Tavily 搜索</a></h3>
<div class="rec-owner">jacky1n7</div> <div class="rec-desc">通过 Tavily API 进行网页搜索（Brave 替代方案）。当用户要求搜索网页、查找来源或链接，且 Brave 网页搜索不可用时使用。</div>
<div class="rec-stats">
<span style="color:#f39c12;">★ 273</span>
<span style="color:#5b6abf;">📥 100,452</span>
</div>
</div>
<div class="rec-card">
<span class="badge-cat" style="margin-bottom:8px;display:inline-block;">life-service</span>
<h3><a href="/s/weather-2-0">Weather 2.0</a></h3>
<div class="rec-owner">maximedogawa</div> <div class="rec-desc">天气预报（无需 API 密钥）。默认一次获取wttr.in；若失败则切换至 Open‑Meteo。聊天式回答——请参见‘如何回答’。</div>
<div class="rec-stats">
<span style="color:#f39c12;">★ 0</span>
<span style="color:#5b6abf;">📥 462</span>
</div>
</div>
</div>
</div>
</div>
<script>
document.addEventListener('DOMContentLoaded',function(){
document.querySelectorAll('.detail-tab').forEach(function(btn){
btn.addEventListener('click',function(e){
var tab = this.getAttribute('data-tab');
document.querySelectorAll('.detail-tab').forEach(function(b){b.classList.remove('active')});
document.querySelectorAll('.detail-content').forEach(function(c){c.classList.remove('active')});
this.classList.add('active');
var el = document.getElementById('tab-'+tab);
if(el) el.classList.add('active');
});
});
});
</script>
<div class="footer">
<p>Skill工具集 © 2026</p>
</div></body>
</html>