jury
Score any website the way an Awwwards jury would, from evidence alone. Screenshots every page type on desktop, a throttled phone and reduced motion, measures LCP, CLS, FPS, axe, keyboard focus and hover feedback, audits SEO and metadata, then a fresh critic that never sees the code scores Design, Us…
Install / Use
npx skills add juliobsz/skills --skill juryInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of jury
jury scores 90/100 on our quality scale, 263rd of 642 Marketing skills we index (top 41%).
Its SKILL.md is 7.8 KB long, well organised into 13 sections with 2 code examples: a thorough specification that gives an agent plenty to work with.
With 1,041 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 21 days ago, so jury is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
jury compared with similar skills
All 4 of these similar skills score higher than jury; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| jury (this skill)by juliobsz | 90 | 1.0k | 21d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install jury?
- Run
npx skills add juliobsz/skills --skill jury. The install tabs above show the steps for each supported agent. - Which AI agents does jury work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is jury safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is jury still maintained?
- The repository was last updated 21 days ago, so jury is actively maintained.
Skill content
View source on GitHubname: jury description: Score any website the way an Awwwards jury would, from evidence alone. Screenshots every page type on desktop, a throttled phone and reduced motion, measures LCP, CLS, FPS, axe, keyboard focus and hover feedback, audits SEO and metadata, then a fresh critic that never sees the code scores Design, Usability, Creativity, Content and the six developer areas, with a ranked fix list. Use when someone asks to review, critique, score, rate or roast a website, portfolio or landing page, asks whether a site is good enough for Awwwards or Site of the Day, or wants design QA of a live URL or a local build. Not for building or redesigning a site; use /awwwards for that.
/jury
Score a website the way the Awwwards jury would: from what a visitor sees and what the browser measures, never from the code, the design notes or what the owner meant. Hand back a score card with evidence for every number and a ranked list of fixes.
Not affiliated with Awwwards. The criteria and weights are theirs and public (awwwards.com/about-evaluation); the scores are an estimate. Say so on every card.
Skill root: the directory containing this file ($SKILL; substitute the absolute path in
commands). The scripts need Node 20+ and Playwright, plus axe-core for the accessibility pass.
references/quality-bar.md has the system, the rubric and the critic brief.
references/calibration.md has the measured gap between this critic and real juries. It is for
you, for the score card. Never give it to the critic.
Why blind
Anyone who knows what a site is meant to do scores the intent instead of the screen. A juror
gets a URL and a few minutes. So the critic gets only screenshots and measurements: no source,
no DESIGN.md, no README, no pitch from the owner. If the user explains the idea, hold it until
the score is in, then compare (step 5).
Workflow
1. Target
- A URL: score what is deployed.
- A local project, no URL: build it and serve the production output. Never score a dev
server: unminified JS and dev overlays wreck WPO and add console noise.
- Next.js:
npm run build, thennpx next start -p 4400in the background. - Static output (Astro, Vite, Next
output: 'export'):node $SKILL/scripts/serve.mjs <dist|out> --port 4400in the background. - Anything else: its own production build and start commands.
- Next.js:
- A dev URL only (localhost with hot reload): build production instead if the project is here. If it isn't, score it and say the WPO numbers are pessimistic.
- Several URLs ("mine vs theirs"): run steps 3 to 5 for each, each with its own fresh critic, then put the cards side by side.
- Behind a login or password: it can't be scored. Ask for a public URL or a local build.
Evidence goes in .jury/<host>/ in the current directory (<host> such as example.com or
127.0.0.1-4400). Use absolute paths for it below.
2. Tools
The scripts resolve Playwright and axe-core from their working directory.
- If the current project already has Playwright (
node -e "require.resolve('playwright')"succeeds), run the scripts from there. - Otherwise don't add dependencies to someone's project for a review. Install once into a cache
folder outside it and run the scripts from that folder:
mkdir -p ~/.cache/jury && cd ~/.cache/jury && npm init -y > /dev/null && npm i -D playwright axe-core - If
shoot.mjsreports no Chromium, runnpx playwright install chromiumonce in that folder.
3. Evidence
node $SKILL/scripts/shoot.mjs <url> --crawl --nav --out <abs>/.jury/<host>/shots
node $SKILL/scripts/audit.mjs <url> > <abs>/.jury/<host>/audit.txt
shoot.mjs --crawltakes one page of every type (home, each top-level page, one item per collection) plus the 404. For each: desktop at 1440, a phone at 390 throttled to a mid-range device (4x CPU, slow 4G), reduced motion, keyboard focus, rest/hover pairs for pointer targets, idle motion, and page-transition frames. Allow a minute or two per page.audit.mjsexits with code 1 when it finds a FAIL. That is a finding, not a broken run.- For a quick look at one page, drop
--crawland pass--max 10to the audit. Say on the card that it covers one page. - Check the evidence is real before scoring. Open
shots/home/d-01-hero.pngandshots/summary.json. A bot challenge, a login wall, an error page, or a blank frame with errors inreport.jsonmeans there is nothing to score: stop and tell the user. A cookie banner is not a reason to stop. Visitors see it too, so it counts. - Crawling is light: at most 40 HTML pages for the audit and 8 page types for screenshots. Don't raise those limits on a site the user doesn't own.
4. Score
- With subagents: give a fresh one the critic brief from
references/quality-bar.md("Critic brief"), with its three paths filled in (the rubric,.jury/<host>/shots/,.jury/<host>/audit.txt). Give it nothing else, and nevercalibration.md. It reads every screenshot, so your own context stays small. - Without subagents: score it yourself under the same brief, from the evidence alone, and mark the card as a self-score.
- If you built or edited this site in this conversation, a self-score isn't blind. Use a subagent, or say on the card that the score is not independent.
5. Score card
Write .jury/<host>/scorecard.md and give the same card in chat:
# <site>: jury score
Estimate, not affiliated with Awwwards. <Independent critic | Self-score>, from <n> pages on <date>.
**The idea, as the critic read it:** one sentence
**Critic overall: 6.2** (0.4 Design + 0.3 Usability + 0.2 Creativity + 0.1 Content, on the critic's strict scale)
**Jury estimate: about 7.3** (critic + 1.1, measured on two recent Sites of the Day)
**Band, from the estimate:** below Honorable Mention (under 6.5) | Honorable Mention range (6.5 to 7.1) | Site of the Day range (7.2 and up)
| Criterion | Score | Evidence |
|---|---|---|
| Design (40%) | | file or report field, and what it shows |
| Usability (30%) | | |
| Creativity (20%) | | |
| Content (10%) | | |
| Developer | Score | Evidence |
|---|---|---|
| Semantics/SEO | | |
| Animations/Transitions | | |
| Accessibility | | |
| WPO | | |
| Responsive | | |
| Markup/Meta-data | | |
## Fixes, most score first
1. [Usability] m-03: what is wrong, and what to change
2. ...
## Measured
Mobile LCP and CLS, loader time, FPS, serious axe violations, overflow, `noHoverChange`,
`colorOnly`, idle motion, audit FAIL and WARN counts (from `summary.json` and the audit).
Not scored: anything stills can't show (how motion feels, sound).
Take the offset for the jury estimate from references/calibration.md (the 1.1 above is the
offset when this was written) and follow its rules: the critic's own numbers stay as scored, and
the developer areas get no jury estimate.
Then, in chat only:
- If the user told you what the site is meant to say, one line: does the critic's reading match? If not, the site isn't saying it, and that is the first Creativity fix.
- The two fixes that would move the overall most.
- An offer: fix the list in this project if it's here, or run
/awwwardsin it for a redesign.
Re-scoring after fixes
Run steps 3 to 5 again with a new critic, never the earlier one, and never show it the
earlier card: it would anchor on the old numbers. Before writing the new card, rename the old
one to scorecard-<n>.md, then show the change per category.
Rules
- No evidence, no points. Every score cites a screenshot file or a report field. Start each category at 6 and make the evidence earn every point above it.
- Don't argue a score up. Dispute one only by pointing at a screenshot the critic misread.
- Judge the site on screen. Don't propose a new concept; fix what's there.
- Specific, not cruel: "m-03: the title wraps to five lines at 390 px; drop it to 14vw", never "the typography needs work". Someone made this.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
