updated 2026-08-26 19:03 UTC

Claude to IM skill

op7418/Claude-to-IM-skill

Pending first signal refresh

Agent Skills TypeScript Grade D Listed
8.3/100
Rank #326 of 331
Compare Claude to IM 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-03-23 · 156d ago
Recent change
New

Is Claude to IM skill safe? Claude to IM skill scores 8.3/100 (Grade D), ranked #326 of 331 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; recent commits are unsigned; last pushed 2026-03-23. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#324 Founder Skills — 8.8 (D) → #325 Web Asset Generator — 8.7 (D) → #327 Bundles Forge — 8.2 (D) → #328 Shinkoku — 7.4 (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-26
Newly Listed
First tracked at rank #326
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.
Refresh maintenance signals The repo was last pushed 156 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Claude to IM skill View Agent Skills Report missing data
35.6
Activity sub-score · out of 100
#326
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-26 19:03 UTC · Repo last pushed 156 days ago

Activity & Reach

Stars
2.9k
Forks
319
Last Push
2026-03-23
156 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
60
Rank Change
NEW

Analysis

HVTrust Dimensions vs Agent Skills

8.3 / 100 · 40.0% confidence

Claude to IM skill Agent Skills average (331 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0 / 25
1.7 below avg 1.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 11.1
Transparency50% declared license · 50% OSSF Scorecard
0 / 17
4.4 below avg 4.4
Maintenance60% last-push freshness · 40% commit activity
1.6 / 20
12.9 below avg 14.5
AdoptionLog-scaled stars · package downloads
8.3 / 20
in line with avg 8.3

Activity Inputs

35.6 / 100
StarsRepository reach
20.7 / 30
FreshnessLast push recency
3.3 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
11.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
—
Unable to query

Is Claude to IM skill safe?

Public trust evidence for Claude to IM 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 Claude to IM skill publish package provenance?
No published build provenance is currently detected for Claude to IM 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 Claude to IM skill have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Claude to IM 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 Claude to IM skill actively maintained?
Slowing down. Last push was 156 days ago — keep an eye on whether activity resumes.
What license does Claude to IM skill use?
Claude to IM skill ships under no SPDX license detected. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

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 Claude to IM skill?

For maintainers

HVTrust scores Claude to IM 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-26
Newly Listed
First tracked at rank #326
GitHub → npm: claude-to-im-skill

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 8.3 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/claude-to-im-skill.svg)](https://hvtracker.net/agents/claude-to-im-skill)
HTML:
<a href="https://hvtracker.net/agents/claude-to-im-skill"><img src="https://hvtracker.net/badge/claude-to-im-skill.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