.claude/skills/vercel-insightsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Reports a Vercel site's errors, traffic and speed: runtime error logs, failing requests, page views, visitors, top pages, referrers, and Core Web Vitals. Trigger on requests like "what errors did my site have in the last 30 minutes", "why am I getting 500s", "show me the logs", "how is my traffic this week", or "which pages are slowest". Read only.
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/vercel-insightsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/vercel-insightsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/vercel-insightsRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @anatoli-iliev/vercel-insightsclawhub inspect @anatoli-iliev/vercel-insights --version 1.1.1This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:0779ad6878d42b2ceb68f2a888b77b389442114391aa741727b1c6fcccb0c6cdbin/vercel-insightsCHANGELOG.mdCONTRIBUTING.mddocs/api-notes.mddocs/cli-contract.mddocs/openclaw-setup.mdexamples/example_outputs.mdexamples/github-action-budget.ymlLICENSEpyproject.tomlREADME.mdskill-card.mdSKILL.mdtests/conftest.pytests/helpers.pytests/test_any_metric.pytests/test_budgets.pytests/test_cli.pytests/test_entrypoint.pytests/test_http.pytests/test_list_metrics.pytests/test_logs_cli.pytests/test_logs_render.pytests/test_logs.pytests/test_missing_dependency.pytests/test_odata.pytests/test_owner_scope.pytests/test_presets.pytests/test_projects.pytests/test_render.pyDocumentation and packaging only, answering the scan findings against 1.1.0. No behaviour changed, no feature was added or removed, and the test suite is unchanged at 1371 passing offline. The design record and implementation plan no longer ship inside the skill. They remain in git history, reachable at tag v1.1.0 and through pull request 24. A scanner reads a shipped document as live guidance, so a historical record of a defect that was found and fixed reads as a current one, and a historical plan's example trigger phrases read as routing instructions. A real account's identifiers are out of the published tree. The project id, request and deployment ids, invocation id, domains and route names in the example output and in the recorded API row were replaced with fictional values of the same shape. What made those examples worth having is preserved: they are still real captured output, th…
Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.
These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.
sha256:148137c6f956af6310668650cfef1084729a7c97701fa22a1a93b3b45c5d2dc5sha256:7218d4e1c2f74653ebba32391aa840528fb3708f39d41f16ad18d155d482ff3fsha256:16c2d4f9a08c9ff306bbcef9aee5a41f4221eddc3cb2f0eef026eef111c15d2b