Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for people juggling multiple coding assistants and wanting one place to organize, enable, translate, sync, and share skill packs without manually copying files between tool-specific directories.
Who should use it
Who should skip it
Skip jiweiyeah/Skills-Manager if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
jiweiyeah/Skills-Manager 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. The standout signals for jiweiyeah/Skills-Manager are workflow potential (9.6) and setup ease (8.8), while maturity (6.4) trails — that balance shapes where it fits best. 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 jiweiyeah/Skills-Manager a composite score of 8.1 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
It writes symlinked skill changes into multiple assistant environments, so first rollout should happen on a test machine or a disposable skill library; Marketplace-imported skills can still change agent behavior in surprising ways, so teams should review community packs before syncing them broadly.