New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Sanity Radar

by sanity-io in sanity-io/sanity

Studio Radar, the repo-health dashboard at radar.sanity.dev (source in dev/radar) — what each tool shows, where the data lives, how to query benchRun / gitCommit / gitTag / bisectSession documents…

OfficialMITAuto-check passed

Install Sanity Radar

skills CLI
$ npx skills add sanity-io/sanity --skill sanity-radar -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sanity-io/sanity sanity-radar --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sanity-io/sanity.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sanity-radar .claude/skills/sanity-radar && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sanity-radar
GitHub stars
6.4k
Token cost
~2.9k tokens
SKILL.md length
798 words
Files
2 (incl. references)
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

Studio Radar, the repo-health dashboard at radar.sanity.dev (source in dev/radar) — what each tool shows, where the data lives, how to query benchRun / gitCommit / gitTag / bisectSession documents…

  • Asked about studio performance trends
  • SKILL.md covers Tools (URL path = tool name), The data, Working on the dashboard and Operations
  • Calls pnpm and gh; needs RADAR_SANITY_WRITE_TOKEN and GITHUB_TOKEN
  • The bench dataset

What it does

Sanity Radar is an agent skill from sanity-io/sanity, published by the product's own GitHub organization. Studio Radar, the repo-health dashboard at radar.sanity.dev (source in dev/radar) — what each tool shows, where the data lives, how to query benchRun / gitCommit / gitTag / bisectSession documents with GROQ (read token required), and how to run, test and change the dashboard code. Use when asked about studio performance trends, drift flags, the bench dataset, release markers, the Bisect or Comparisons tools, "what did the daily bench say", or when editing anything under dev/radar.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/groq-recipes.md`).

The repository describes itself as: Sanity Studio – Rapidly configure content workspaces powered by structured content. The licence is MIT.

When your agent uses it

  • Asked about studio performance trends
  • The bench dataset
  • Release markers
  • Comparisons tools

Example prompts

  • “what did the daily bench say”
  • “/sanity-radar”

Requirements

  • A credential in RADAR_SANITY_WRITE_TOKEN
  • A credential in GITHUB_TOKEN

What it can do on your machine

Read from SKILL.md and the folder at commit efa15fb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • radar.sanity.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • RADAR_SANITY_WRITE_TOKEN
    • GITHUB_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sanity Radar loads about 2.9k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 125 tokens; SKILL.md has 798 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~125
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sanity-io/sanity at commit efa15fb, republished under its MIT licence (© sanity-io). 798 words, ~2,897 tokens.

Download SKILL.mdSave it as .claude/skills/sanity-radar/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
sanity-radar
description
Studio Radar, the repo-health dashboard at radar.sanity.dev (source in dev/radar) — what each tool shows, where the data lives, how to query benchRun / gitCommit / gitTag / bisectSession documents with GROQ (read token required), and how to run, test and change the dashboard code. Use when asked about studio performance trends, drift flags, the bench dataset, release markers, the Bisect or Comparisons tools, "what did the daily bench say", or when editing anything under dev/radar.

Studio Radar

Radar answers repo-health questions without opening CI logs: is studio performance drifting on main, what did a run look like, which commit broke it, what shipped when. It is a Sanity Studio (dev/radar, deployed at https://radar.sanity.dev) reading a dataset that CI writes. The design record is dev/radar/SPEC.md — read the section for the view you touch, and update it when behavior changes. For regression hunting use sanity-radar-investigate; for producing the data use sanity-bench.

Tools (URL path = tool name)

ToolPathShows
Trends/trendsSmall multiples per scenario·metric on main: p50 line, p75–p90 band, host calibration (dotted), drift baseline overlay (dashed before / solid after), release ticks. Default view.
Releases/releasesEvery synced v* tag: dist-tags, downloads, changelog links, regressions bisect attributed to it.
Bisect/bisectGuided first-parent bisect over gitCommit using each commit's test-studio preview build.
Diagnostics/diagnosticsPaste a studio diagnostics JSON, render it (in-studio twin of dev/studio-diagnostics-viewer).
Structure/structureRaw documents.
Comparisons/comparisonsStored mode: "ab" runs from A/B dispatches, verdict per metric.

Trends URL state, all shareable: ?range=30|90|all, ?branches=main,<branch>, ?layers=-band,-calibration (hide layers), ?tab=<metric group>, ?max=<series key> (one chart maximized). Releases: ?path=<test-studio path> (the path field under the header) opens every release's Test Studio link at that path. Clicking a point opens the run popover: value, percentiles, host, release context, links, and under "Suspect a regression?" the GitHub compare of the gap, Copy A/B vs previous run (the gh workflow run bench.yml … ab_from/ab_to command) and Copy investigation prompt (a paste-ready brief for an agent).

The data

Project mhfozd0z, dataset bench, private: reads need a token with access to the project (your CLI token via sanity debug --secrets, or a viewer token from sanity.io/manage; the deployed studio authenticates through your login). Writes need RADAR_SANITY_WRITE_TOKEN, which only CI has; never write from a laptop. Ids are built in one place, @repo/utils/radar-ids: lowercase, dashes, no dots (a dot makes an id a path like drafts.x, which the API scopes differently).

TypeWritten byIdKey fields
benchRunbench store in .github/workflows/bench.ymlbench-run-<sha>-<run id> / bench-run-pr-<n>mode (absolute = time-series point, ab = investigation record), trigger (cron/release/backfill/dispatch/pr; absent = cron), git{sha, branch, committedAt, mergeBaseSha, prNumber}, runner{calibrationMs, cpuModel, runId…}, scenarios[]{scenario, mode, runner{calibrationMs, cpuModel}, metrics[]{label, unit, experiment/reference{summary{median,p75,p90}}, comparison{diff,lo,hi,verdict}}, resources, soak}, bundle{initialJsBytes, totalJsBytes}
gitCommitsync-git-metrics.yml (every push to main)git-commit-<sha>sha, parentSha (first-parent chain), committedAt, subject, prNumber, author, testStudioUrl
gitTagsame, releases and a daily npm floorgit-tag-v6-10-1tag, sha, taggedAt, major/minor/patch/prerelease, npm{distTags, weeklyDownloads, publishedAt, deprecated}
bisectSessionBisect tool (user-owned, liveEdit)bisect-session-<uuid>description (the issue), refines (weak ref to the session it narrows down — a chain counts as one regression), good/bad{sha}, releasesOnly, reproPath (test-studio path appended to every preview URL), marks[], result{firstBadSha, suspectShas, regression, note, severity (minor/major/critical), linearIssue, fixedIn}
releaseLineReleases tool (user-owned, liveEdit)release-line-v<major>major, eolMarkedAt, eolMarkedBy, note — existence means the major is end of life; reinstating deletes it
driftAckTrends drift feed (user-owned)drift-ack-<slug of metricKey:branch>state (silenced/snoozed/fixed), baselineValue, until

Rules that every consumer follows (the dashboard's queries are the reference, tools/*/data.ts):

  • Project, never fetch sessions. Documents carry per-session sample arrays; a bare *[_type == "benchRun"] is megabytes.
  • Time series = mode == "absolute", ordered by coalesce(git.committedAt, startedAt) (backfill runs have a historical committedAt and a recent startedAt). PR-branch runs share the type — filter git.branch == "main" for the main line.
  • Same-sha runs are one point. CI re-measures commits; the charts merge them by median.
  • Absolute numbers are host-relative. Always read runner.calibrationMs (higher = slower host) and runner.cpuModel next to any value; only A/B comparison.verdicts are host-independent.
  • git.sha is the join key to gitCommit; benchRun.git.commit is a weak reference that dangles for PR-branch runs.

Ready-made queries: references/groq-recipes.md.

Show full SKILL.md (213 more words)Show less

Working on the dashboard

bash
pnpm radar                                  # sanity dev on http://localhost:3399 (needs a Sanity login; reads live data)
pnpm vitest run --project=radar             # pure modules: trend math, drift, bisect, git parsers
pnpm build:radar                            # production build (turbo)
pnpm --filter radar sync-git -- --dry-run   # preview the git-history sync (needs GITHUB_TOKEN)
  • Realtime everywhere: useDocumentStore().listenQuery + useObservable, never one-shot client.fetch. New cron runs must appear without a reload.
  • Charts are visx primitives (@visx/scale|shape|group|axis|responsive) inside @sanity/ui layout; no chart library.
  • Debug data sources (dev server only, toolbar picker; tools/trends/debugData.ts) render steady/drift/step/host-correlated/sparse/empty datasets and synthetic release tags — use them to exercise every encoding layer and the drift feed without live data. UI is verified through these, not unit tests.
  • One source of truth for "enough to care": drift thresholds import from perf/bench/stats/gate.ts. Don't invent a second statistic; SPEC.md records the baselines that were tried and rejected (step, weekday-matched) and why.
  • Honesty constraint: any surface showing a ms value must make host calibration visible (CALIBRATION_EXPLAINER is the one shared wording).
  • Studio conventions from AGENTS.md apply (no forwardRef, use-effect-event, no inline Translate components).

Operations

  • Daily main run: bench.yml cron 05:00 UTC; git sync 05:30. A missed day is repaired with a backfill dispatch (see sanity-bench). A gap in commits: gh workflow run sync-git-metrics.yml -f backfill=true.
  • Release markers only appear for tags whose commit has a gitCommit document (main-only by construction); a maintenance release cut from a branch is correctly absent.
  • Cron failures alert the CI Slack channel; a hole in the series with no alert means the store step was skipped, not that the run failed.

© sanity-io, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/sanity-radar of sanity-io/sanity.

  • SKILL.md
  • references/groq-recipes.md

Open the folder on GitHubat commit efa15fb

Compare with similar skills

Sanity Radar next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sanity Radar compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sanity Radar this skillsanity-io/sanity6.4k—~2.9kAutomated safety check: PassMIT
Codebase Health Dashboardgarrytan/gstack136k—~11kAutomated safety check: NotesMIT
Dashboardasgeirtj/system_prompts_leaks69k—~4.1kAutomated safety check: PassCC0-1.0
Studioremotion-dev/remotion63k—~376Automated safety check: PassCustom licence
DashboardInsForge/InsForge13k—~2.3kAutomated safety check: PassApache-2.0
Skin Health Analyzersickn33/agentic-awesome-skills47k2 repos~293Automated safety check: PassMIT

Similar skills

  • Codebase Health Dashboard

    garrytan/gstack

    Runs a project's own type checker, linter, test runner, dead-code detector and shell linter, combines them into a weighted 0-10 score and tracks the trend.

    136k GitHub stars~11k tokensUpdated today
    DevelopmentAuto-check: notes

  • Dashboard

    asgeirtj/system_prompts_leaks

    Use this for a dashboard, metrics page, KPI tracker, scorecard, data visualization or recurring report: a page or scroll story of charts, numbers and tables of data, whatever the data and wherever…

    69k GitHub stars~4.1k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

  • Studio

    remotion-dev/remotion

    Official

    Start Remotion Studio from packages/example and open it in the Codex browser.

    63k GitHub stars~376 tokensUpdated yesterday
    Media & CreativeAuto-check passed

  • Dashboard

    InsForge/InsForge

    A skill your agent uses when contributing to InsForge's shared dashboard package.

    13k GitHub stars~2.3k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Skin Health Analyzer

    sickn33/agentic-awesome-skills

    Analyze skin health data, identify skin problem patterns, assess skin health status.

    47k GitHub starsUsed in 2 repos~293 tokens
    Productivity & AutomationAuto-check passed

  • Live Dashboard

    NousResearch/hermes-agent

    Build self-updating dashboards from live sources. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

More from sanity-io/sanity

All 34 skills in this repo

  • Playwright CLI

    sanity-io/sanity

    Official

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    6.4k GitHub starsUsed in 18 repos~1.9k tokens
    Auto-check passed

  • Find Skills

    sanity-io/sanity

    Official

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities.

    6.4k GitHub starsUsed in 67 repos~1.2k tokens
    Auto-check passed

  • Vercel React Best Practices

    sanity-io/sanity

    Official

    React and Next.js performance optimization guidelines from Vercel Engineering.

    6.4k GitHub starsUsed in 129 repos~1.6k tokens
    Auto-check passed

  • Before And After

    sanity-io/sanity

    Official

    Add existing screenshots or screen recordings to a GitHub pull request as a before/after or preview block.

    6.4k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • React Devtools

    sanity-io/sanity

    Official

    React DevTools CLI for AI agents. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 3 repos~2.1k tokens
    Auto-check passed

  • TDD

    sanity-io/sanity

    Official

    Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.

    6.4k GitHub starsUsed in 20 repos~1k tokens
    Auto-check passed

Questions about Sanity Radar

What does Sanity Radar do?

Studio Radar, the repo-health dashboard at radar.sanity.dev (source in dev/radar) — what each tool shows, where the data lives, how to query benchRun / gitCommit / gitTag / bisectSession documents…. Sanity Radar is an agent skill from sanity-io/sanity, published by the product's own GitHub organization.dev (source in dev/radar) — what each tool shows, where the data lives, how to query benchRun / gitCommit / gitTag / bisectSession documents with GROQ (read token required), and how to run, test and change the dashboard code.

When should I use Sanity Radar?

Sanity Radar fits situations like: asked about studio performance trends; the bench dataset; release markers; comparisons tools.

How do I install Sanity Radar in Claude Code?

Run `npx skills add sanity-io/sanity --skill sanity-radar -a claude-code`. Or copy the skill folder (.agents/skills/sanity-radar in sanity-io/sanity) into .claude/skills/sanity-radar in your project. Claude Code loads it when a task matches its description.

How do I install Sanity Radar in Codex?

Run `npx skills add sanity-io/sanity --skill sanity-radar -a codex`. Or copy the skill folder (.agents/skills/sanity-radar in sanity-io/sanity) into .agents/skills/sanity-radar in your project. Codex loads it when a task matches its description.

Can I use Sanity Radar in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sanity-io/sanity --skill sanity-radar -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sanity-radar, .gemini/skills/sanity-radar, .github/skills/sanity-radar and .opencode/skills/sanity-radar in your project.

What does Sanity Radar need to run?

Going by SKILL.md and its folder, Sanity Radar needs the command-line tools its instructions call (pnpm and gh) and credentials named RADAR_SANITY_WRITE_TOKEN and GITHUB_TOKEN. Our summary lists: A credential in RADAR_SANITY_WRITE_TOKEN; A credential in GITHUB_TOKEN.

Does Sanity Radar access the network?

SKILL.md names 1 domain. As links in the text: radar.sanity.dev. This is read from the text; nothing was executed.

Is Sanity Radar safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sanity Radar use?

Sanity Radar is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sanity Radar use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Sanity Radar?

Skills that share tags, products or a category with Sanity Radar: Codebase Health Dashboard (garrytan/gstack, 136k stars), Dashboard (asgeirtj/system_prompts_leaks, 69k stars), Studio (remotion-dev/remotion, 63k stars) and Dashboard (InsForge/InsForge, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sanity Radar?

sanity-io (a GitHub organization, an official publisher) maintains it in sanity-io/sanity, which has 6,352 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 9, 2026.

Source: sanity-io/sanity on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.