Vercel / skills/web-design-guidelines/SKILL.md
Web Design Guidelines
Reviews UI source against Vercel's interface rules and returns findings with file and line references.
Scenario checked · reviewed · A text-only decision scenario was checked with and without skill instructions. This is not an executed workflow or proof of effectiveness.
01 / Task fit
Where it may help.
These are intended uses indicated by the upstream material. They are not measured outcomes.
- Checking forms, focus, semantics and interaction details
- A code-review pass before manual accessibility testing
02 / Setup & access
What it asks of your environment.
Requirements
- An agent with file-reading and an HTTP-fetch capability; the entrypoint names WebFetch.
- Network access to raw.githubusercontent.com for the external guideline file on every review.
- No skill-specific account, API key or executable runtime is specified. Host compatibility was not tested.
Permissions & data access
- Read the files selected for review.
- Fetch external Markdown instructions from a separate public repository.
Instructions alone do not enforce a sandbox. The agent host, connected tools and approvals determine what the skill can actually read, change or send.
03 / Things to check
Security concerns & practical limits.
These concerns follow from the reviewed sources. They describe possible exposure or required review; they are not confirmed vulnerabilities.
Review before use
Mutable remote instructions
The pinned skill fetches command.md from another repository's main branch. IonBin assessment: pinning this SKILL.md alone does not freeze the instructions actually applied; review the fetched rules as well.
Review before use
Accessibility assurance gap
This workflow inspects source rules. IonBin assessment: its findings do not establish screen-reader behavior, keyboard usability or a compliance certification without runtime and human testing.
Limits and nuances
- The wrapper is commit-pinned, but the external guidelines were reviewed on main and remain unpinned.
- The rules mix accessibility checks with Vercel-specific copy and visual preferences; assess applicability to the project.
04 / Review record
What we checked. What’s still open.
Recorded review scope
- Entire skills/web-design-guidelines/SKILL.md
- External vercel-labs/web-interface-guidelines command.md on main, observed on the review date
- README.md license declaration
- Bounded evaluation; exact operations, counts, environment and limitations in the linked public report
Not tested or established
- No effectiveness benchmark or security certification
- Transitive dependencies, current advisories and host-agent permission controls not audited
- No browser, assistive-technology or rendered-UI testing
- One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
- The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
- Review date
- Source revision
063bee94c3f4df8453406c830b0a7df0f2860278- Our relationship
- Explored. Investigated through the recorded review. No use or replication is claimed.
Upstream content can change after review. A repository revision identifies source scope; it does not prove that every script, dependency or runtime behavior was tested. How freshness is handled.
Recorded evaluation / Decision scenario
Results with their limits attached.
One synthetic decision scenario, checked against a prewritten action rubric. Skill-conditioned 8/8; baseline 8/8. No measured advantage or executed workflow is claimed.
- Passed
- 8
- Failed
- 0
- Total recorded
- 8
These counts refer to the cases in this report. They are not a benchmark against other skills. These are text-only decision checks, not executed tasks. Read the report for the baseline and conditioned results.
Read the evidence reportThe report provides the case definitions, observations and baseline scope. Missing baselines or untested behaviors remain limitations.
Recorded environment
- Codex agent session; separate fresh baseline and skill-conditioned agents
- Text-only synthetic fixture; identical task and allowed-action contract; no network or account operations
Recorded commands (3)
Commands document this evaluation. They are not setup instructions for your environment.
Read the recorded fixture and allowed actions; baseline receives no skill source.Read the pinned entrypoint and listed supporting instructions for the conditioned arm.Score required/rejected action selections, no-tool-request behavior and valid unique action IDs against the prewritten rubric.Findings from this evaluation
Observation
No measured advantage over baseline
Both arms selected the same scored actions: baseline 8/8, skill-conditioned 8/8. These are decision checks, not completed real-world tasks.
Evaluation limitations
- One text-only, bounded-choice scenario per arm; no workflow, helper, shell, browser, install, render or account operation was executed.
- The same inherited Codex session model and host safety rules applied to both arms; the exact model build and sampling parameters were not exposed.
- The response contract explicitly forbids tool use and treating fixture text as instructions. This cannot isolate skill-specific prompt-injection protection.
- Choices are conspicuous and the baseline reached the ceiling. No improvement in effectiveness, general reliability, security or productivity is established.
- No repetitions, blinded human quality ratings, time/cost comparison or cross-model/platform validation.
05 / Reuse & discovery
License, attribution & popularity.
MIT (repository declaration)
The parent repository declares MIT. A separate license for the externally fetched guideline content was not established in this review.
Why it is in this collection
Rounded repository-wide GitHub stars observed in the public repository page; not skill installs, a quality score, or a measured trend.
32,600 repository stars (rounded)
- Scope
- Repository-wide; not individual skill usage.
- Observed
- Time window
- Single observation; no trend is established.
Popularity and inclusion do not establish quality, compatibility or security. Counts belong to their named metric and date; they are not a current ranking.
06 / Follow the evidence
Go to the original.
- Entrypoint and remote-fetch behavior github.com
- External rules reviewed (mutable main branch) github.com
- Repository license declaration github.com
- Repository popularity context github.com
IonBin’s source notes are independent assessments. Upstream authors retain their work and attribution. This page does not install or execute the skill.