Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams that need real-session browser tasks for agents, but want a visible local bridge and an explicit handoff point when a site needs human input.
Who should use it
Who should skip it
Avoid running Tencent/BrowserSkill in production until you have reviewed its permissions, data-access scope, and failure modes in a sandbox.
About this signal
Tencent/BrowserSkill is tracked by RepoRadar as a browser automation in the AI Infrastructure section. It was first seen on 2026-06-28 and last updated on 2026-06-28. The current verdict is 'worth watch' with a Silver tier and moderate setup difficulty. Across RepoRadar's eight signals, Tencent/BrowserSkill is strongest on open-source/build quality (8.4) and workflow potential (8.1) and weakest on momentum (5.0) — 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 Tencent/BrowserSkill a composite score of 7.7 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 'medium' 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 evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
It grants an agent access to a real logged-in browser session, so treat every borrowed tab as live account access with customer and workspace exposure; The separate agent window reduces disruption but not blast radius, so start with a dedicated low-privilege profile and require human review for sensitive sites.