updated 2026-08-12 05:02 UTC

Goose Skills

gooseworks-ai/goose-skills

Library of Growth & GTM skills + data APIs for Claude Code, Codex, Cursor to run ads, social, content, lead gen, seo and

Agent Skills Python Grade D Listed MIT
28.0/100
Rank #33 of 148
Compare Goose Skills

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 C · 2/5 signals
Last push
2026-07-23 · 20d ago
Recent change
New

Is Goose Skills safe? Goose Skills scores 28.0/100 (Grade D), ranked #33 of 148 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 36% of recent commits are signed; last pushed 2026-07-23. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#31 Claude Plugins Official — 29.3 (D) → #32 Pinme — 28.2 (D) → #34 Trailofbits Skills — 27.3 (D) → #35 Power Platform Skills — 26.7 (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 #33
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 Goose Skills View Agent Skills Report missing data
69.6
Activity sub-score · out of 100
#33
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 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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 20 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
1.1k
Forks
200
Last Push
2026-07-23
20 days ago
Commits (4 wk)
27
Downloads (7d)
17
npm
HN mentions (30d)
—
Open Issues
3
Rank Change
=
was #33

Analysis

HVTrust Dimensions vs Agent Skills

28.0 / 100 · 67.0% confidence

Goose Skills Agent Skills average (148 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.8 / 25
0.9 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
16.4 / 20
1.3 above avg 15.1
AdoptionLog-scaled stars · package downloads
9.0 / 20
in line with avg 9.2

Activity Inputs

69.6 / 100
StarsRepository reach
18.4 / 30
FreshnessLast push recency
22.2 / 25
ActivityRecent commits
18.1 / 25
CommunityFork signal
10.7 / 20

Supply Chain Trust

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

Is Goose Skills safe?

Public trust evidence for Goose Skills 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 Goose Skills publish package provenance?
No published build provenance is currently detected for Goose Skills. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Goose Skills have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Goose Skills. 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 Goose Skills actively maintained?
Maintained. Last push was 20 days ago.
What license does Goose Skills use?
Goose Skills ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Goose Skills's commits signed?
36% of the last 100 commits to Goose Skills 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
medium confidence
Implemented
Goose Skills appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies 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
high confidence
Warning
1 package source mismatch detected
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Goose Skills?

For maintainers

HVTrust scores Goose Skills 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 #33
GitHub → npm: goose-skills

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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