Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计通过

news-gameinfomer新闻游戏信息员

Agent Skill

news-gameinfomer 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,118

周安装

91

GitHub Stars

公开资料未说明

下载量

743
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:news-gameinfomer(新闻游戏信息员)
来源仓库:https://github.com/maximedogawa/news-gameinfomer
安装命令:
openclaw skills install news-gameinfomer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install news-gameinfomer

简介

news-gameinfomer 获取 Game Informer 的 RSS 内容,按节返回英文项目。

  • 适用于游戏新闻、评论与预览内容订阅场景。
  • 通过 clawhub 安装,使用 openclaw skills install news-gameinfomer 命令部署。
  • 建议确认 RSS 源结构与语言过滤规则,注意网络访问。
  • 可结合原始 README 了解标题分级与内容分段逻辑。

SKILL.md

name
Game Informer News
description
Game Informer — section RSS (news/reviews/previews/features). Fetch per section; English reply; only ### headings for sections with at least one item from that feed; no empty placeholders; title as markdown link.
tags
[news, games, game-informer, rss]
requires
[]
source
https://www.gameinformer.com/

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).

SectionURL
Newshttps://www.gameinformer.com/news.xml
Reviewshttps://www.gameinformer.com/reviews.xml
Previewshttps://www.gameinformer.com/previews.xml
Featureshttps://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: <title>, <link> (canonical article URL), <pubDate>, <description> (often long HTML), optional <dc:creator>.

  • Use exact <title> and <link> from the same <item>.
  • Do not paste raw HTML from <description>; at most a very short plain-text teaser if you strip tags safely — otherwise title + link only.

Which feeds to load

User intentFetches
Generic: Game Informer / GI / “what’s new” / headlines overviewAll four section feeds (news, reviews, previews, features) — four separate fetch calls
Only news / reviews / previews / featuresOnly the matching .xml URL(s)
Explicitly “everything in one list” / main RSS onlyrss.xml only (single section in the reply is OK)

Response — section layout (only non-empty feeds)

Language: English for headings and any prose.

Include a ### section only when that feed was loaded successfully and you are listing at least one <item> from it.

Do not output a section that has no items — no headings like ### Reviews with “No reviews available”, “Nothing in the feed”, or *(Feed unavailable.)*. If you did not fetch that URL or the XML has no items, omit that section entirely.

If several section feeds have items, use headings in this order (skip any that you omit): News → Reviews → Previews → Features.

Example when only News has data (e.g. only news.xml was fetched):

## Game Informer

### News

1. **[Title from news.xml](exact-link-from-item)**
2. …

Example when News and Reviews both have data:

## Game Informer

### News

1. **[Title](url)**

### Reviews

1. **[Title](url)**

Rules:

  • Blank line after each ## / ###.
  • Numbered lists under each included section; default 3–5 items per section unless the user asks otherwise.
  • Put the URL only in the title: **[Title](url)** — no separate Link: line.
  • A story from news.xml appears only under News; same for reviews/previews/features. Never list a reviews feed item under News.

Mandatory

Non-negotiable checklist (single-file skill — everything lives in this README):

  1. Sections map to feeds: News = news.xml, Reviews = reviews.xml, Previews = previews.xml, Features = features.xml. Items may appear only under the section whose feed they came from.
  1. Overview questions: If the user does not restrict to one topic, fetch all four URLs (four separate fetch calls) before answering — when the runtime allows multiple fetches.
  1. Reply shape — omit empty: Output ### News / ### Reviews / ### Previews / ### Features only for feeds you actually loaded and that contain at least one item you list. Forbidden: empty sections, “No reviews available”, “Nothing in the current feed”, or similar placeholders for a feed you did not populate from XML.
  1. Order: Among sections you do include, use this order: News, then Reviews, then Previews, then Features.
  1. Items: Title and URL must be from the same <item>. Use `title`. No invented stories. Default 3–5 items per included section unless the user specifies another count.
  1. Language: Reply in English.
  1. Descriptions: Do not dump HTML from <description>; title + link is enough unless a short plain teaser is clearly safe.

Errors

If all fetches fail, say so — do not invent headlines.

When to use

Game Informer, GI, gaming news from Game Informer, reviews/previews/features from the site, “latest Game Informer stories”.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

79.05%
按下载量换算587

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills