Shuorenhua
说人话|中文优先的去 AI 味改写 skill:保事实、分场景、改完可直接发。Chinese-first rewrite skill for Codex / Claude Code / Cursor / ChatGPT — removes AI tone, preserves facts.
Is Shuorenhua safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Shuorenhua
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Shuorenhua scores 51.5/100 (Grade C), ranked #218 of 351 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.6/10; 3% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How Shuorenhua compares in Agent Skills
- #216 Claude Code My Workflow 51.5 ±0
- #217 Jeffallan Claude Skills 51.5 ±0
- #218 Shuorenhua 51.5 this agent
- #219 Ktx 51.4 −0.1
- #220 Recall 51.3 −0.2
Bars show each HVTrust score; the tick marks Shuorenhua’s 51.5.
Where the 51.5 comes from
HVTrust dimensions vs the Agent Skills average
51.5 / 100 · 100.0% confidenceShuorenhua Agent Skills average (351 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
68.4 / 100Supply Chain Trust
Common questions about Shuorenhua
Does Shuorenhua publish package provenance?
Does Shuorenhua have an OpenSSF Scorecard?
Is Shuorenhua actively maintained?
What license does Shuorenhua use?
Are Shuorenhua's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Shuorenhua's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Shuorenhua?
For maintainers
HVTrust scores Shuorenhua from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/shuorenhua)
<a href="https://hvtracker.net/agents/shuorenhua"><img src="https://hvtracker.net/badge/shuorenhua.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON