Taste Skill
Website
Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Is Taste Skill safe? Promising trust profile, but some evidence still deserves review.
Compare Taste Skill
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Taste Skill scores 60.2/100 (Grade C), ranked #102 of 371 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.9/10; 42% of recent commits are signed; last pushed 2026-10-14. Every point is earned from checkable signals — never paid placement. How scoring works →
How Taste Skill 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.
- Raise the OSSF Scorecard from 3.9 to 9.0lowest checks: CI-Tests 0, CII-Best-Practices 0, Code-Review 0 +10.7 → 70.9 B · #30 of 371
- Sign every commit42% signed today +2.9 → 63.1 C · #75 of 371
Chain of custody
Scanners check what the code says. This traces who ships Taste Skill 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.
-
Source Partly signed
github.com/Leonxlnx/taste-skill, MIT, last pushed 2026-10-14. 42% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Sep 27, 2026, refresh pending). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflown/a
- Token Permissionsn/a
- Pinned Dependenciesn/a
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 0CII-Best-Practices 0Code-Review 0Contributors 0Dangerous-Workflow -1Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies -1SAST 0Security-Policy 0Signed-Releases -1Token-Permissions -1Vulnerabilities 10 -
Published packages None
No registry package. Taste Skill is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
- 2026-08-30 OSSF Scorecard: 3.9/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Taste Skill’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.
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 Taste Skill compares in Agent Skills
- #100 NotFair 60.2 ±0
- #101 Microsoft Skills 60.2 ±0
- #102 Taste Skill 60.2 this agent
- #103 Claude Code Agent Monitor 60.1 −0.1
- #104 Styleseed 60.0 −0.2
Bars show each HVTrust score; the tick marks Taste Skill’s 60.2.
Where the 60.2 comes from
HVTrust dimensions vs the Agent Skills average
60.2 / 100 · 100.0% confidenceTaste Skill Agent Skills average (371 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
94.3 / 100Common questions about Taste Skill
Does Taste Skill publish package provenance?
Does Taste Skill have an OpenSSF Scorecard?
Is Taste Skill actively maintained?
What license does Taste Skill use?
Are Taste Skill'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 Taste Skill'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 Taste Skill?
For maintainers
HVTrust scores Taste 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/taste-skill)
<a href="https://hvtracker.net/agents/taste-skill"><img src="https://hvtracker.net/badge/taste-skill.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.4 · Raw JSON