updated 2026-08-12 05:02 UTC

GPT Image2 Skill

wuyoscar/GPT-Image2-Skill

GPT Image 2 prompt gallery, image prompt library, agentic skill, and CLI for OpenAI image generation/editing

Agent Skills Python Grade D Listed MIT
15.3/100
Rank #139 of 148
Compare GPT Image2 Skill

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-10 · 2d ago
Recent change
New

Is GPT Image2 Skill safe? GPT Image2 Skill scores 15.3/100 (Grade D), ranked #139 of 148 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; 34% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#137 Claude Ads — 15.5 (D) → #138 Brooks Lint — 15.5 (D) → #140 Claude Code Java — 15.1 (D) → #141 AI Research SKILLs — 15.1 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-11
Newly Listed
First tracked at rank #139
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.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for GPT Image2 Skill View Agent Skills Report missing data
66.3
Activity sub-score · out of 100
#139
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-08-12 05:02 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
4.4k
Forks
378
Last Push
2026-08-10
2 days ago
Commits (4 wk)
3?
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #139

Analysis

HVTrust Dimensions vs Agent Skills

15.3 / 100 · 40.0% confidence

GPT Image2 Skill Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.7 / 25
1.0 below avg 2.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.5 below avg 11.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.5
Maintenance60% last-push freshness · 40% commit activity
13.1 / 20
2.0 below avg 15.1
AdoptionLog-scaled stars · package downloads
8.7 / 20
in line with avg 9.2

Activity Inputs

66.3 / 100
StarsRepository reach
21.9 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
12.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
34%
of last 100 commits verified

Is GPT Image2 Skill safe?

Public trust evidence for GPT Image2 Skill 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 GPT Image2 Skill publish package provenance?
No published build provenance is currently detected for GPT Image2 Skill. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does GPT Image2 Skill have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for GPT Image2 Skill. 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 GPT Image2 Skill actively maintained?
Actively maintained. The repository was pushed to within the last 2 day(s).
What license does GPT Image2 Skill use?
GPT Image2 Skill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are GPT Image2 Skill's commits signed?
34% of the last 100 commits to GPT Image2 Skill 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
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain GPT Image2 Skill?

For maintainers

HVTrust scores GPT Image2 Skill 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-08-11
Newly Listed
First tracked at rank #139
GitHub → PyPI: gpt-image-cli

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 15.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/gpt-image2-skill.svg)](https://hvtracker.net/agents/gpt-image2-skill)
HTML:
<a href="https://hvtracker.net/agents/gpt-image2-skill"><img src="https://hvtracker.net/badge/gpt-image2-skill.svg" alt="HVTrust"></a>

Other agents in Agent Skills

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