Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people whose skills already drift across multiple agents and folders and who want one coherent inventory plus a safer way to install, align, and clean them up.
Who should use it
Who should skip it
Skip Milktang0128/myskills unless the captured evidence suggests it solves a problem you are actively working on.
About this signal
Milktang0128/myskills is tracked by RepoRadar as a developer tool in the Agent Skills section. It was first seen on 2026-07-01 and last updated on 2026-07-01. The current verdict is 'try now' with a Gold tier and easy setup difficulty. Across RepoRadar's eight signals, Milktang0128/myskills is strongest on workflow potential (9.5) and setup ease (8.8) and weakest on maturity (6.3) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Milktang0128/myskills a composite score of 8.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'conditional' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Its MCP path can install, realign, and clean up local skill directories, so first evaluation should happen in a backed-up sandbox rather than your primary agent profile; Dedupe by name and source is useful, but teams should still review drifted copies before bulk sync so good local edits are not flattened accidentally.