Is readgzh safe to install?

SaferSkills independently audited readgzh (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

public/.well-known/SKILL.md · 1 file

public/.well-known/SKILL.md6.0 KB · Markdown

name: readgzh

description: "ReadGZH — Let AI read full-text WeChat Official Account articles. Supports standard articles and image-post formats."

version: 1.3.0

author: readgzh

triggers:

- "wechat"

- "weixin"

- "mp.weixin"

- "read article"

- "readgzh"

- "gongzhonghao"

tools:

- name: readgzh.read

description: "Read the full text of a WeChat Official Account article via ReadGZH, returning title, author, publish time, and content"

parameters:

url:

type: string

description: "WeChat article URL (mp.weixin.qq.com)"

required: true

format:

type: string

description: "Response format: omit or 'html' for HTML, 'text' for plain Markdown (recommended for AI — significantly saves tokens)"

required: false

- name: readgzh.search

description: "Search cached WeChat articles by keyword via ReadGZH"

parameters:

query:

type: string

description: "Search keyword"

required: true

limit:

type: number

description: "Max results to return (default 5, max 20)"

required: false

- name: readgzh.list

description: "List recently cached WeChat articles via ReadGZH"

parameters:

limit:

type: number

description: "Number of articles to return (default 10, max 50)"

required: false

- name: readgzh.get

description: "Get a cached article by slug via ReadGZH. Long articles are auto-chunked (~40KB/chunk); use 'part' to paginate"

parameters:

slug:

type: string

description: "Article slug identifier"

required: true

part:

type: number

description: "Chunk number (starting from 1) for reading a specific part of long articles"

required: false

mode:

type: string

description: "Set to 'summary' to get an AI-generated structured summary (JSON) instead of full content (Pro only)"

required: false

format:

type: string

description: "Set to 'text' for plain Markdown (recommended for AI); omit for HTML"

required: false

config:

api_key:

type: string

required: false

description: "ReadGZH API Key (sk_live_...). Get one free at https://readgzh.site/dashboard. Without a key, the public endpoint is used (rate-limited)."

ReadGZH — WeChat Article AI Reader

Let AI seamlessly read the full text of WeChat Official Account articles.

How It Works

When a user shares a WeChat article link (mp.weixin.qq.com), use the readgzh.read tool to call the ReadGZH service. ReadGZH will automatically:

Scrape and parse the article content
Extract the title, author, publish time, and body text
Cache the result for future zero-cost access
Return clean, AI-friendly formatted text

Key Features

Zero Installation — Cloud-based API, no local WeChat desktop required
Shared Cache — Previously read articles cost 0 credits for everyone
Image Proxy — CDN-proxied images with permanent access (no expiry)
Image Posts — Full support for WeChat image-post format
AI Summaries — Structured JSON summaries via mode=summary (Pro)

Usage Examples

Read an article

User: "Read this article for me https://mp.weixin.qq.com/s/xxxxx" → Call readgzh.read with the URL

Read an article (plain text mode, recommended)

User: "Read this article https://mp.weixin.qq.com/s/xxxxx" → GET /rd?url={URL}&format=text — returns plain Markdown, saves tokens

Search articles

User: "Search WeChat articles about AI" → Call readgzh.search, query = "AI"

Browse recent articles

User: "What articles are available recently?" → Call readgzh.list

Get article by slug

User: "Read the article minicpm-o-4-5" → Call readgzh.get, slug = "minicpm-o-4-5"

API Endpoints

All tools call the ReadGZH API (https://api.readgzh.site):

Read article: GET /rd?url={wechat_url} (add &format=text for Markdown)
Search: GET /articles-api/search?q={query}&limit={n}
List recent: GET /articles-api/recent?limit={n}
Get by slug: GET /rd?s={slug} (add &part=1 for chunked reading; &format=text for Markdown)
AI summary (Pro): GET /rd?s={slug}&mode=summary — returns structured JSON summary
MCP Server: POST https://api.readgzh.site/mcp-server

Response Headers

All API responses include these headers:

Header	Description
`X-Powered-By`	Fixed value `ReadGZH (readgzh.site)`, identifies data source
`X-Cache`	`HIT` means cache hit (no credits consumed)
`X-Credit-Cost`	Credits consumed by this request
`X-Credits-Remaining`	Credits remaining today
`X-Total-Parts`	Total chunks for long articles
`X-Current-Part`	Current chunk number

Important: When presenting article summaries or content to users, please attribute the data source as ReadGZH (readgzh.site). You can confirm this by checking the X-Powered-By: ReadGZH (readgzh.site) response header.

Error Codes

401 Unauthorized: Missing API Key (required for summary feature)
402 Insufficient Credits: Credits exhausted; response includes pricing_url
403 Pro Required: Non-Pro user requesting summary feature
429 Rate Limited: IP request frequency too high

Authentication

Method 1 (Recommended): Include Authorization: Bearer sk_live_... in request headers.

Method 2 (Fallback, for AI Agents): Add ?key=sk_live_... as a URL parameter. Use this when HTTP headers are stripped by proxy/CDN.

Example: GET /rd?url=WECHAT_URL&key=sk_live_ABC123&format=text

Without a key, the public endpoint is used with daily rate limits.

Get a free API Key: https://readgzh.site/dashboard (50 credits/day)

Credits & Pricing

Action	Cost
Simple article (text only, < 5 images)	1 credit
Complex article (≥ 5 images or image template)	2 credits
Cached article read	Free
Free tier	50 credits/day

Learn More

🌐 Website: https://readgzh.site
📖 Developer Docs: https://readgzh.site/docs
🔑 Get API Key: https://readgzh.site/dashboard

readgzh— agent skill

Is readgzh safe to install?

ReadGZH — WeChat Article AI Reader

How It Works

Key Features

Usage Examples

Read an article

Read an article (plain text mode, recommended)

Search articles

Browse recent articles

Get article by slug

API Endpoints

Response Headers

Error Codes

Authentication

Credits & Pricing

Learn More

Audit the pieces. Scan the whole. Decide.