updated 2026-10-12 00:08 UTC

Distilly

Repository

Distilly — Distill how they think into reusable Skills for any Agent or Bot. Formerly Colleague Skill（原同事 Skill）.

Agent Skills Python Listed MIT

Is Distilly safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.9 / 10
Provenance None
Signed commits 7%
Last push 20d ago
Compare Distilly

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Distilly scores 50.0/100 (Grade C), ranked #240 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; 7% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Distilly 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 Distilly 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/titanwings/distilly, MIT, last pushed 2026-09-22. 7% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Oct 11, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection1
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 1
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages None

    No registry package. Distilly 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-10-11 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 Distilly’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 Distilly compares in Agent Skills

  1. #238 ResearcherSkill 50.2 +0.2
  2. #239 GZH Design Skill 50.1 +0.1
  3. #240 Distilly 50.0 this agent
  4. #241 Designer Skills 49.9 −0.1
  5. #242 Claude OSINT 49.9 −0.1

Bars show each HVTrust score; the tick marks Distilly’s 50.0.

Where the 50.0 comes from

HVTrust dimensions vs the Agent Skills average

50.0 / 100 · 100.0% confidence

Distilly Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.2 / 25
2.7 below avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
11.8 / 17
in line with avg 12.1
Maintenance60% last-push freshness · 40% commit activity
11.9 / 20
2.2 below avg 14.1
AdoptionLog-scaled stars · package downloads
10.6 / 20
1.6 above avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-11
Scorecard Added
OSSF Scorecard: 3.9/10
2026-10-11
Grade Changed
Trust grade D → C
2026-10-11
Rank Moved
Rank rose 126 spots (#367 → #241)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.
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 Distilly View Agent Skills Report missing data
68.1
Activity sub-score · out of 100
#240
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 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 →

Signals refreshed 2026-10-12 00:08 UTC · Repo last pushed 20 days ago

Rank Trend

2026-10-09 2026-10-11

Activity & Reach

Stars
25.5k
Forks
2.2k
Last Push
2026-09-22
20 days ago
Commits (4 wk)
1
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
21
Rank Change
▲1
was #241

Analysis

Activity Inputs

68.1 / 100
StarsRepository reach
26.4 / 30
FreshnessLast push recency
22.2 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
15.5 / 20

Common questions about Distilly

Public trust evidence for Distilly 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 Distilly publish package provenance?
No published build provenance is currently detected for Distilly. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Distilly have an OpenSSF Scorecard?
Distilly has an OpenSSF Scorecard score of 3.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Distilly actively maintained?
Maintained. Last push was 20 days ago.
What license does Distilly use?
Distilly ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Distilly's commits signed?
7% of the last 100 commits to Distilly 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
medium confidence
1 tags
Broad capability areas detected.
  • browser
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 Distilly?

For maintainers

HVTrust scores Distilly 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 1HVTrust 1Rank 1Grade 1Scorecard 1
2026-10-11
Scorecard Added
OSSF Scorecard: 3.9/10
2026-10-11
Grade Changed
Trust grade D → C
2026-10-11
Rank Moved
Rank rose 126 spots (#367 → #241)
2026-10-11
HVTrust Changed
HVTrust up 29.1pts (20.9 → 50.0)
2026-10-09
Newly Listed
First tracked at rank #367
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/distilly.svg)](https://hvtracker.net/agents/distilly)
HTML:
<a href="https://hvtracker.net/agents/distilly"><img src="https://hvtracker.net/badge/distilly.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
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