updated 2026-10-15 12:09 UTC

Beautify GitHub README

Repository by oil-oil

README design skill for Claude Code & Codex. 帮你把 GitHub README 做得好看又好懂。

Agent Skills Python Listed MIT

Is Beautify GitHub README safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 59%
Last push 11d ago
Compare Beautify GitHub README

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Beautify GitHub README scores 21.7/100 (Grade D), ranked #376 of 385 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 59% of recent commits are signed; last pushed 2026-10-04. Every point is earned from checkable signals — never paid placement. How scoring works →

How Beautify GitHub README could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Beautify GitHub README and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/oil-oil/beautify-github-readme, MIT, last pushed 2026-10-04. 59% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages None

    No registry package. Beautify GitHub README is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Beautify GitHub README.

Evidence behind this score

Coverage D: 1 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks (missing)
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Beautify GitHub README’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Beautify GitHub README compares in Agent Skills

  1. #374 Obsidian Skills 22.1 +0.4
  2. #375 natural-japanese 21.8 +0.1
  3. #376 Beautify GitHub README 21.7 this agent
  4. #377 oh-my-hermes 21.3 −0.4
  5. #378 Oil Motion 21.2 −0.5

Bars show each HVTrust score; the tick marks Beautify GitHub README’s 21.7.

Where the 21.7 comes from

HVTrust dimensions vs the Agent Skills average

21.7 / 100 · 50.0% confidence

Beautify GitHub README Agent Skills average (385 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.0 / 25
4.8 below avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.5 below avg 12.0
Maintenance60% last-push freshness · 40% commit activity
13.2 / 20
0.9 below avg 14.1
AdoptionLog-scaled stars · package downloads
7.9 / 20
1.1 below avg 9.0

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-10-15
Newly Listed
First tracked at rank #376
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent Get email alerts for Beautify GitHub README View Agent Skills Report missing data
59.1
Activity sub-score · out of 100
#376
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-15 12:09 UTC · Repo last pushed 11 days ago

Activity & Reach

Stars
1.9k
Forks
133
Last Push
2026-10-04
11 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
NEW

Analysis

Activity Inputs

59.1 / 100
StarsRepository reach
19.6 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
9.9 / 20

Common questions about Beautify GitHub README

Public trust evidence for Beautify GitHub README is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Beautify GitHub README publish package provenance?
No published build provenance is currently detected for Beautify GitHub README. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Beautify GitHub README have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Beautify GitHub README. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Beautify GitHub README actively maintained?
Maintained. Last push was 11 days ago.
What license does Beautify GitHub README use?
Beautify GitHub README ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Beautify GitHub README's commits signed?
59% of the last 100 commits to Beautify GitHub README are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Beautify GitHub README?

For maintainers

HVTrust scores Beautify GitHub README 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-10-15
Newly Listed
First tracked at rank #376
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 21.7 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/beautify-github-readme.svg)](https://hvtracker.net/agents/beautify-github-readme)
HTML:
<a href="https://hvtracker.net/agents/beautify-github-readme"><img src="https://hvtracker.net/badge/beautify-github-readme.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON