Resolve any IMDb title URL / tt-ID / free-form title reference (movie, TV series, episode, mini-series, short) to its current IMDb rating, total vote count, rating distribution per 1-10 bucket, Metascore, and core title metadata (cast, directors, writers, genres, runtime, certification, plot, languages, countries, poster, canonical URL). Read-only.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionget-ratingExecute the skills CLI command in your project's root directory to begin installation:
Fetches get-rating from imdb.com/get-rating-16ss93 and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate get-rating. Access via /get-rating in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
| name | get-rating |
| title | IMDb Title Rating Lookup |
| description | >- Resolve any IMDb title URL / tt-ID / free-form title reference (movie, TV series, episode, mini-series, short) to its current IMDb rating, total vote count, rating distribution per 1-10 bucket, Metascore, and core title metadata (cast, directors, writers, genres, runtime, certification, plot, languages, countries, poster, canonical URL). Read-only. |
| website | imdb.com |
| category | entertainment |
| tags | - imdb - ratings - movies - tv - metadata - read-only - aws-waf |
| source | 'browserbase: agent-runtime 2026-05-18' |
| updated | '2026-05-18' |
| recommended_method | browser |
| alternative_methods | - method: api rationale: >- IMDb's public suggestion API (v3.sg.media-imdb.com/suggestion/{x}/{slug}.json) resolves free-form text to a tt-ID + basic metadata (title, year, type, top cast, poster) with no auth, no anti-bot, and no proxy required — but does NOT expose the user rating, vote count, distribution, runtime, plot, languages, countries, or Metascore. Useful as a name-resolution shortcut before the browser fetch, not as a standalone replacement. - method: cli rationale: >- IMDb publishes daily bulk TSVs at datasets.imdbws.com (title.basics.tsv.gz + title.ratings.tsv.gz). Provides rating + numVotes only — no distribution, no Metascore, ~24h stale, hundreds of MB per file. Reasonable for batch enrichment of large tt-ID sets, not for interactive single-title lookups. |
| verified | true |
| proxies | true |
Given an IMDb title URL, IMDb title ID (tt...), or free-form title reference (movie / TV show / TV episode / mini-series / short / documentary), return the current IMDb rating, total vote count, rating distribution (votes per 1-10 bucket when shown), and the core title metadata: primary title, original title (when different), title type (movie / tvSeries / tvEpisode / tvMiniSeries / short / documentary / videoGame), release year (or year range for series), MPAA / TV certification, runtime in minutes, genres, Metascore (when present), top-billed cast with role names, directors, writers, primary poster URL, short + long plot summary, language(s), country/countries of origin, and the canonical IMDb URL. For TV episodes additionally return parent series ID + title and season/episode numbers. Read-only — never click Rate, Add to Watchlist, Sign In, or any mutation control.
tt-ID per row.tt-ID before scraping any other IMDb subpage.aggregateRating for any IMDb title type, including TV episodes (/title/tt.../episodes/).The optimal flow is two-staged:
tt-ID via IMDb's public-but-undocumented suggestion API (no auth, no anti-bot, no proxy). This is the same JSON the IMDb search-bar typeahead uses. Always use this first unless the caller already passed a tt-ID or a /title/tt.../ URL.https://www.imdb.com/title/{ttId}/ and extract from its static HTML — primarily the <script type="application/ld+json"> block and the <script id="__NEXT_DATA__" type="application/json"> blob. The title page is protected by AWS WAF (AwsWafIntegration token challenge) which returns a 202 with a ~2 KB JS-challenge body to non-browser HTTP clients (including browse cloud fetch, even with --proxies). Drive it from a real browser session: browse open --remote against a Browserbase session created with --verified --proxies. The WAF clears automatically when JS executes.tt-ID (skip if you already have the ID)The suggestion API is rooted at https://v3.sg.media-imdb.com/suggestion/{firstChar}/{slug}.json. The {firstChar} path component is ignored server-side — any of h, t, or the actual first character of {slug} returns the same response. Build {slug} from the user query by replacing spaces with _ and lowercasing:
SLUG=$(echo "$query" | tr '[:upper:]' '[:lower:]' | tr ' ' '_' | sed 's/[^a-z0-9_]//g')
browse cloud fetch "https://v3.sg.media-imdb.com/suggestion/t/${SLUG}.json"
Response shape — d[] is an ordered list of matches:
{"d":[
{"id":"tt0111161","l":"The Shawshank Redemption","q":"feature","qid":"movie",
"rank":78,"s":"Tim Robbins, Morgan Freeman","y":1994,
"i":{"imageUrl":"https://m.media-amazon.com/...","height":1800,"width":1200}},
...
]}
Key fields:
id — the tt-prefixed title ID. This is your handoff to step 2.l — title.q — human-readable type ("feature", "TV series", "TV mini-series", "TV episode", "TV short", "short", "TV movie", "video", "podcastSeries", "videoGame").qid — machine type (movie, tvSeries, tvMiniSeries, tvEpisode, tvShort, short, tvMovie, video, podcastSeries, videoGame).y — year (a single integer). Series additionally carry yr as a "YYYY-YYYY" range string (open-ended ongoing series have "YYYY-").rank — IMDb popularity rank (lower = more popular). Do not confuse with the user rating — rank is MOVIEmeter-style popularity, NOT the 0.0-10.0 user score. The user rating is not exposed via the suggestion API at all.s — short top-cast string (comma-separated names, no roles).i — poster image URL + native dimensions.Disambiguation heuristics (run in order until a single best match is left):
"the matrix 1999"), filter d[] to entries where y === year."TV", "series", "movie", "episode", "documentary"), filter d[] by matching qid.rank (most popular). If rank is missing on a candidate, treat as Infinity.rank values (within 10× of each other) and the query is ambiguous, emit a success: false, reason: "ambiguous_name" result with the top 3-5 candidates rather than guessing.For TV episodes: the suggestion API surfaces well-known episodes (e.g. "breaking bad ozymandias" → tt2301451) but tends to under-rank lesser-known episode pages. If the query says "season N finale" / "S5E14" / etc. and the suggestion API returns the parent series instead of the episode, fall back to resolving the series first, then navigating to /title/{seriesId}/episodes/?season={N} and reading the episode-list page (or jumping to /title/{episodeId}/).
SID=$(browse cloud sessions create --keep-alive --verified --proxies | jq -r '.id')
export BROWSE_SESSION="$SID"
browse open "https://www.imdb.com/title/${ttId}/" --remote
browse wait load --remote
browse wait timeout 1500 --remote # let lazy hydration settle
HTML=$(browse get html body --remote)
Both --verified and --proxies are required — without them the AWS WAF challenge stalls in browse cloud fetch and IP-blocks/rate-limits a vanilla Browserbase session within a few requests. With them, the title page renders normally (no captcha, no login wall).
<script type="application/ld+json">The first application/ld+json block on every IMDb title page is a schema.org Movie / TVSeries / TVEpisode object that contains everything you need for the headline rating + most metadata:
{
"@context": "https://schema.org",
"@type": "Movie",
"url": "https://www.imdb.com/title/tt0111161/",
"name": "The Shawshank Redemption",
"alternateName": "Cadena perpetua",
"image": "https://m.media-amazon.com/images/M/MV5B...jpg",
"datePublished": "1994-10-14",
"contentRating": "R",
"duration": "PT2H22M",
"genre": ["Drama"],
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": 9.3,
"ratingCount": 3050000,
"bestRating": 10,
"worstRating": 1
},
"actor": [{"@type":"Person","url":"...","name":"Tim Robbins"}, ...],
"director":[{"@type":"Person","url":"...","name":"Frank Darabont"}],
"creator": [{"@type":"Organization","url":"..."}, {"@type":"Person","url":"...","name":"Stephen King"}],
"description": "Over the course of several years, two convicts form a friendship..."
}
Parse it with a hardened regex (NOT JSON.parse on raw HTML; the block may contain HTML-entity-escaped characters in description):
const m = html.match(/<script type="application\/ld\+json">([\s\S]*?)<\/script>/);
const ld = JSON.parse(m[1]);
Field mapping (ld → output JSON):
| Output field | LD-JSON source |
|---|---|
titleId | parse from ld.url (/title/(tt\d+)/) |
title | ld.name |
originalTitle | ld.alternateName if present and !== ld.name, else null |
titleType | derive from ld["@type"] (Movie → movie, TVSeries → tvSeries, TVEpisode → tvEpisode, TVMiniSeries → tvMiniSeries, Short → short, VideoGame → videoGame); fall back to __NEXT_DATA__ (see 2b) when @type is generic. |
year | year part of ld.datePublished (or __NEXT_DATA__.releaseYear.year for safety). |
yearRange | series only — from __NEXT_DATA__ (2b). |
certification | ld.contentRating |
runtimeMinutes | parse ISO-8601 ld.duration (PT2H22M → 142). Some shorts use PT15M; some series use PT45M as per-episode runtime. |
genres | ld.genre (string → wrap in array) |
imdbRating | ld.aggregateRating.ratingValue |
voteCount | ld.aggregateRating.ratingCount |
actors | ld.actor[].name (typically top 5; IMDb truncates here — for the full top-billed list use __NEXT_DATA__, see 2b) |
directors | ld.director[].name (object or array — normalize to array) |
writers | ld.creator[] filtered to @type === "Person" |
posterUrl | ld.image |
shortPlot | ld.description (HTML-entity-decode after parse) |
canonicalUrl | ld.url |
aggregateRating may be absent when a title has fewer than 5 user votes (unrated). Handle missing-gracefully: emit imdbRating: null, voteCount: 0 rather than throwing.
<script id="__NEXT_DATA__" type="application/json">The LD-JSON block is insufficient for some required fields:
spokenLanguages).countriesOfOrigin).endYear).All of these live in the Next.js page-data blob:
const nm = html.match(/<script id="__NEXT_DATA__" type="application\/json">([\s\S]*?)<\/script>/);
const nd = JSON.parse(nm[1]);
const title = nd.props.pageProps.mainColumnData; // root for most title fields
const above = nd.props.pageProps.aboveTheFoldData; // root for rating + summary
Useful paths inside mainColumnData / aboveTheFoldData (paths stable across iters; field names match IMDb's internal GraphQL schema):
aboveTheFoldData.ratingsSummary.aggregateRating — same ratingValue (decimal).aboveTheFoldData.ratingsSummary.voteCount — same total as LD-JSON.mainColumnData.ratingsSummary.histogram.histogramValues — rating distribution, an array of 10 objects {rating: 10, voteCount: N} from rating 10 down to rating 1. The order is descending — always sort or map by rating rather than relying on positional index.aboveTheFoldData.metacritic.metascore.score — Metascore (or null when no Metascore).mainColumnData.cast.edges[] — full cast; each edge has node.name.nameText.text (actor name), node.characters[].name (role names), node.attributes[].text ("voice", "uncredited", etc.).mainColumnData.principalCredits[] — director/writer/creator grouped by role (category.id === "director" | "writer" | "creator").mainColumnData.spokenLanguages.spokenLanguages[].text — languages.mainColumnData.countriesOfOrigin.countries[].text — countries.mainColumnData.plot.plotText.plainText — short plot (same as LD-JSON description).mainColumnData.outline.plotText.plainText — outline (often null).mainColumnData.releaseYear.year + mainColumnData.releaseYear.endYear (endYear null for ongoing series).mainColumnData.series.series.id (parent series tt-ID), mainColumnData.series.series.titleText.text (parent series title), mainColumnData.series.episodeNumber.seasonNumber, mainColumnData.series.episodeNumber.episodeNumber.For the FULL plot summary (the multi-paragraph "Storyline" block), the __NEXT_DATA__ blob carries it at mainColumnData.summaries.edges[0].node.plotText.plaintext (or null if only a synopsis exists). When you need a longer plot than ld.description, prefer this path.
browse cloud sessions update "$SID" --body '{"status":"REQUEST_RELEASE"}'
There is no public API surface that returns the IMDb user-rating value. The suggestion API in step 1 is purely a name-resolver. The title-page HTML is the only path to the rating + distribution + Metascore. Don't waste cycles chasing caching.graphql.imdb.com or api.graphql.imdb.com — verified blocked / 500 to anonymous clients (see Site-Specific Gotchas).
www.imdb.com/title/* HTML request from non-browser clients. A bare browse cloud fetch (with or without --proxies) returns HTTP 202 and a ~2 KB body containing an awswaf.com/challenge.js token-acquisition handshake — not the real page. The challenge clears only when JS executes, so the title page must be loaded inside a real browser session. Verified across https://www.imdb.com/title/tt0111161/, /title/.../episodes/, /find/, /_next/data/..., /sitemap.xml, /_json/... — every WAF-protected path returns the same 1991-byte challenge.browse cloud fetch is NOT a viable surface for IMDb title pages. Use it only for the suggestion API (v3.sg.media-imdb.com) and robots.txt — both are WAF-exempt. All www.imdb.com paths the future agent cares about are WAF-protected.--verified --proxies on the Browserbase session. Bare sessions get WAF-challenged or IP-rate-limited after a handful of requests. --verified clears the challenge automatically; --proxies rotates the source IP to avoid the rate-limit ban that triggers around request 10-20 from the same datacenter IP.User-agent: anthropic-ai / Claude-Web / GPTBot / CCbot / Google-Extended → Disallow: / are present in https://www.imdb.com/robots.txt. The skill must drive a real browser (with a non-bot UA), not curl-fetch with an AI-bot UA. Browserbase's verified-browser path uses a real Chrome UA and clears this.{firstChar} path component is decorative. https://v3.sg.media-imdb.com/suggestion/h/the_matrix.json and /suggestion/t/the_matrix.json and /suggestion/0/the_matrix.json all return identical JSON. The IMDb search-bar typeahead conventionally sends the first character of the query; the server doesn't care.rank is MOVIEmeter popularity, NOT user rating. A common trap. The user rating (aggregateRating.ratingValue) is not in the suggestion JSON at all — only the title-page HTML carries it.aggregateRating is missing from the LD-JSON block when a title has fewer than ~5 user votes (typical for obscure shorts, unreleased titles, video-game expansions). Treat as imdbRating: null, voteCount: 0 rather than failing.__NEXT_DATA__, not in the LD-JSON block. The path is mainColumnData.ratingsSummary.histogram.histogramValues and the array is sorted descending by rating (10 → 1). Always map by rating field; do not assume index 0 == 10.actor array is truncated (typically 5 entries). For the full top-billed cast, parse __NEXT_DATA__.props.pageProps.mainColumnData.cast.edges[].PT2H22M → 142, PT45M → 45. For series, this is the per-episode runtime, not total — note that in the output if the title type is tvSeries/tvMiniSeries.datePublished for series is the series premiere date, not the year range. For a yearRange field on series, read __NEXT_DATA__.mainColumnData.releaseYear.year (start) and .endYear (null for ongoing).tt-ID has its own /title/tt.../ page with the same LD-JSON + __NEXT_DATA__ structure. To get parent-series context, read mainColumnData.series.series.id / .titleText.text and mainColumnData.series.episodeNumber.seasonNumber / .episodeNumber.pro.imdb.com). It loads without the WAF challenge but exposes MOVIEmeter / production-contact data, not the public user-rating. Don't use it for rating lookup.caching.graphql.imdb.com and api.graphql.imdb.com return 301 → 500 (or block) without a session-cookied request from a logged-in page context. Don't try to bypass the title-page HTML this way.https://datasets.imdbws.com/ (title.basics.tsv.gz, title.ratings.tsv.gz — only rating + numVotes, no distribution). Useful for batch enrichment of millions of tt-IDs; not appropriate for "what's the rating right now" lookups (24-hour staleness) or for distribution / Metascore (not in the dataset).ld.alternateName is the original-language title for foreign-language films (e.g. "Cadena perpetua" for tt0111161's Spanish release). It is also populated for some English-language films with regional retitles, so compare alternateName !== name before treating it as "original title"."Joe's Shanghai" as a movie title without disambiguation tricks.wss://connect.{region}.browserbase.com for CDP traffic, not just api.browserbase.com. Sandboxes that allowlist only the API host can run browse cloud fetch against the suggestion API but cannot drive the title page via browse open --remote — and the title page is mandatory for rating data. Verify CDP reachability before running.Single, consistent shape — variants by title type are reflected in titleType and the optional seriesContext block.
{
"success": true,
"titleId": "tt0111161",
"title": "The Shawshank Redemption",
"originalTitle": null,
"titleType": "movie",
"year": 1994,
"yearRange": null,
"certification": "R",
"runtimeMinutes": 142,
"genres": ["Drama"],
"imdbRating": 9.3,
"voteCount": 3050000,
"ratingDistribution": [
{"rating": 10, "voteCount": 1830000},
{"rating": 9, "voteCount": 580000},
{"rating": 8, "voteCount": 320000},
{"rating": 7, "voteCount": 150000},
{"rating": 6, "voteCount": 70000},
{"rating": 5, "voteCount": 38000},
{"rating": 4, "voteCount": 18000},
{"rating": 3, "voteCount": 12000},
{"rating": 2, "voteCount": 8000},
{"rating": 1, "voteCount": 25000}
],
"metascore": 82,
"cast": [
{"name": "Tim Robbins", "role": "Andy Dufresne"},
{"name": "Morgan Freeman", "role": "Ellis Boyd 'Red' Redding"},
{"name": "Bob Gunton", "role": "Warden Norton"},
{"name": "William Sadler", "role": "Heywood"},
{"name": "Clancy Brown", "role": "Captain Hadley"}
],
"directors": ["Frank Darabont"],
"writers": ["Stephen King", "Frank Darabont"],
"posterUrl": "https://m.media-amazon.com/images/M/MV5BMDAyY2FhYjctNDc5OS00MDNlLThiMGUtY2UxYWVkNGY2ZjljXkEyXkFqcGc@._V1_.jpg",
"shortPlot": "Over the course of several years, two convicts form a friendship, seeking consolation and, eventually, redemption through basic compassion.",
"fullPlot": "Chronicles the experiences of a formerly successful banker as a prisoner...",
"languages": ["English"],
"countries": ["United States"],
"canonicalUrl": "https://www.imdb.com/title/tt0111161/",
"seriesContext": null
}
{
"success": true,
"titleId": "tt11280740",
"title": "Severance",
"originalTitle": null,
"titleType": "tvSeries",
"year": 2022,
"yearRange": "2022-",
"certification": "TV-MA",
"runtimeMinutes": 60,
"genres": ["Drama", "Mystery", "Sci-Fi", "Thriller"],
"imdbRating": 8.7,
"voteCount": 450000,
"ratingDistribution": [ {"rating": 10, "voteCount": 0}, ... ],
"metascore": 87,
"cast": [ {"name": "Adam Scott", "role": "Mark Scout"}, ... ],
"directors": [],
"writers": ["Dan Erickson"],
"posterUrl": "https://...",
"shortPlot": "...",
"fullPlot": "...",
"languages": ["English"],
"countries": ["United States"],
"canonicalUrl": "https://www.imdb.com/title/tt11280740/",
"seriesContext": null
}
{
"success": true,
"titleId": "tt2301451",
"title": "Ozymandias",
"originalTitle": null,
"titleType": "tvEpisode",
"year": 2013,
"yearRange": null,
"certification": "TV-MA",
"runtimeMinutes": 48,
"genres": ["Crime", "Drama", "Thriller"],
"imdbRating": 10.0,
"voteCount": 250000,
"ratingDistribution": [ ... ],
"metascore": null,
"cast": [ ... ],
"directors": ["Rian Johnson"],
"writers": ["Vince Gilligan", "Moira Walley-Beckett"],
"posterUrl": "https://...",
"shortPlot": "...",
"fullPlot": "...",
"languages": ["English"],
"countries": ["United States"],
"canonicalUrl": "https://www.imdb.com/title/tt2301451/",
"seriesContext": {
"seriesId": "tt0903747",
"seriesTitle": "Breaking Bad",
"seasonNumber": 5,
"episodeNumber": 14
}
}
// Unrated (fewer than ~5 user votes — aggregateRating missing from LD-JSON)
{
"success": true,
"titleId": "tt99999999",
"title": "Some Obscure Short",
"titleType": "short",
"imdbRating": null,
"voteCount": 0,
"ratingDistribution": [],
"metascore": null,
...
}
// Free-form input could not be confidently resolved to a single tt-ID
{
"success": false,
"reason": "ambiguous_name",
"query": "severance",
"candidates": [
{"titleId": "tt11280740", "title": "Severance", "year": 2022, "titleType": "tvSeries", "rank": 150},
{"titleId": "tt0464196", "title": "Severance", "year": 2006, "titleType": "movie", "rank": 8508}
]
}
// Free-form input returned zero matches from the suggestion API
{
"success": false,
"reason": "title_not_found",
"query": "ksjdhfksjdhfksjdhf"
}
// WAF challenge could not be cleared (rare with --verified --proxies; document and retry on a fresh session)
{
"success": false,
"reason": "anti_bot_block",
"titleId": "tt0111161",
"detail": "AWS WAF AwsWafIntegration challenge did not clear after 3 attempts"
}
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
booking.com/search-hotels-asq6cc
aliexpress.com/search-product-p0h8a7
nav.com/get-smb-funding-2s1rpm
ibelick/ui-skills
google.com/search-flights-ts4g1f
shopee.com.my/search-products-5epzg0
get-rating has been reliable in day-to-day use. Documentation quality is above average for community skills.
get-rating fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added get-rating from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: get-rating is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: get-rating is focused, and the summary matches what you get after install.
get-rating has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: get-rating is focused, and the summary matches what you get after install.
Keeps context tight: get-rating is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added get-rating from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
get-rating fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 69