Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for developers who already like the OpenClaw ecosystem and want a more inspectable way to define, run, and monitor agent pipelines.
Who should use it
Who should skip it
Skip CCLucky-uu/TaskMeld for now if you are only tracking items with a 'try now' verdict.
About this signal
CCLucky-uu/TaskMeld is tracked by RepoRadar as a agent pipeline in the AI Automation section. It was first seen on 2026-06-30 and last updated on 2026-06-30. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. The standout signals for CCLucky-uu/TaskMeld are workflow potential (8.6) and open-source/build quality (8.4), while maturity (5.7) 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 CCLucky-uu/TaskMeld a composite score of 7.8 out of 10, placing it in the Silver 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
The init flow can auto-install OpenClaw and configure gateway access, so review what it is going to install and keep first runs on a trusted local machine; Remote gateway mode relies on URL and token configuration for agent execution, so keep it on localhost or a protected network segment until you have audited the run surface.