Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it.
$ npx skills add awss1i/assay --skill checking-a-page -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install awss1i/assay checking-a-page --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/awss1i/assay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/assay/skills/checking-a-page .claude/skills/checking-a-page && rm -rf skills-srcUse ~/.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/
Install the "checking-a-page" agent skill from https://github.com/awss1i/assay/tree/main/plugins/assay/skills/checking-a-page into .claude/skills/checking-a-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-a-page", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/awss1i/assay/tree/main/plugins/assay/skills/checking-a-pageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add awss1i/assay --skill checking-a-page -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install awss1i/assay checking-a-page --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awss1i/assay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/assay/skills/checking-a-page .agents/skills/checking-a-page && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "checking-a-page" agent skill from https://github.com/awss1i/assay/tree/main/plugins/assay/skills/checking-a-page into .agents/skills/checking-a-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-a-page", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add awss1i/assay --skill checking-a-page -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install awss1i/assay checking-a-page --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awss1i/assay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/assay/skills/checking-a-page .cursor/skills/checking-a-page && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "checking-a-page" agent skill from https://github.com/awss1i/assay/tree/main/plugins/assay/skills/checking-a-page into .cursor/skills/checking-a-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-a-page", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/awss1i/assay.git --path plugins/assay/skills/checking-a-page--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add awss1i/assay --skill checking-a-page -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install awss1i/assay checking-a-page --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awss1i/assay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/assay/skills/checking-a-page .gemini/skills/checking-a-page && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "checking-a-page" agent skill from https://github.com/awss1i/assay/tree/main/plugins/assay/skills/checking-a-page into .gemini/skills/checking-a-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-a-page", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install awss1i/assay checking-a-pageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add awss1i/assay --skill checking-a-page -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/awss1i/assay.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/assay/skills/checking-a-page .github/skills/checking-a-page && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "checking-a-page" agent skill from https://github.com/awss1i/assay/tree/main/plugins/assay/skills/checking-a-page into .github/skills/checking-a-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-a-page", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add awss1i/assay --skill checking-a-page -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install awss1i/assay checking-a-page --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/awss1i/assay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/assay/skills/checking-a-page .opencode/skills/checking-a-page && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "checking-a-page" agent skill from https://github.com/awss1i/assay/tree/main/plugins/assay/skills/checking-a-page into .opencode/skills/checking-a-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-a-page", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
checking-a-pageCheck that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it.
Checking A Page is an agent skill from awss1i/assay. Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Use after creating or editing an HTML page, or the JavaScript or CSS that a page loads.
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering HTML artifacts. It works with JavaScript, Playwright and Python. The repository describes itself as: Drives your web page in a real browser and tells you what broke. No tests to write, no LLM. The licence is MIT.
Read from SKILL.md and the folder at commit 80df875. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
npmFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Checking A Page loads about 712 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 467 words of instructions outside code blocks.
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.
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.
The full file from awss1i/assay at commit 80df875, republished under its MIT licence (© awss1i). 467 words, ~712 tokens.
.claude/skills/checking-a-page/SKILL.md (or your agent's skills folder).A page you have just written has no tests yet. assay opens it in a real
browser, finds every control on it, uses all of them, and reports what it did
and what happened.
When the work is done, not while you are still making changes. Run it once at the end, after the last edit, on each page you changed.
That includes changes to the JavaScript or CSS a page loads, not only the HTML. The page is often a folder or two above the file you changed.
assay <the page you changed> --one-linePoint it at the page itself, such as todo.html or dist/index.html. A
folder works too and opens the index.html inside it. It needs no key,
network or configuration. A small page takes seconds, and a busy one can take a
minute or more.
Put its output, verbatim, as the last thing in your reply. It is already one line, or one line and a short list. Do not summarise it, reformat it, add to it, or write your own version.
It looks like this, and the numbers and wording are assay's own:
assay: checked <page>, <n> checks, nothing flagged.Print it whether it flagged anything or not. If you print nothing, the reader can't tell a clean page from a check that never ran.
If the command did not run, say so instead, in your own words, naming the page and quoting what the shell actually said. Never describe a check that did not happen as one that passed, and never guess at a cause. If the shell printed an error, quote it. If you didn't see one, say only that it did not run.
Report it and stop. Do not edit code in response to a finding in the same reply.
assay doesn't know what the page is for. It presses what the page offers and reports what followed, so a finding is a place to look, not a confirmed bug. A control can correctly do nothing in the state it was pressed in, and a value can be limited on purpose. Changing working code because of a finding nobody has checked is the mistake to avoid, which is why you report instead of fixing.
If the person you are working with asks you to fix it, then fix it.
npm install
for you, because installing dependencies executes their setup scripts.© awss1i, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/assay/skills/checking-a-page of awss1i/assay.
Open the folder on GitHubat commit 80df875
Checking A Page 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Checking A Page this skillawss1i/assay | 102 | — | ~712 | Automated safety check: Pass | MIT | |
| Anti Detect Browserantibrow/anti-detect-browser-skills | 932 | — | ~9.8k | Automated safety check: Warn | MIT | |
| Ibm A11y Route Scanlangflow-ai/langflow | 156k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Language Supportlive-codes/livecodes | 1.5k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Sdf Artshaun8149/sdf-js | 421 | — | ~9.7k | Automated safety check: Pass | Custom licence | |
| Web Design EngineerConardLi/garden-skills | 13k | — | ~8.8k | Automated safety check: Pass | MIT |
antibrow/anti-detect-browser-skills
Drive Chromium from standard Playwright APIs with a real-device fingerprint applied in the kernel, one persistent isolated profile per identity, and a per-profile proxy whose exit IP sets timezone…
langflow-ai/langflow
Batch-scan Langflow frontend routes for accessibility issues using the Python IBM Equal Access scanner (scripts/a11y/a11yscan.py) and produce JSON/Markdown/HTML reports.
live-codes/livecodes
Work with 90+ supported languages, compilers, CSS processors, and WASM-compiled languages for markup, style, and script editors.
shaun8149/sdf-js
Generate sdf-js code from a natural-language scene description.
ConardLi/garden-skills
Builds polished browser-rendered HTML, CSS, JavaScript and React pages, dashboards, prototypes and slide decks, aiming for a stunning rather than merely functional result.
SourceWeft/SourceWeft
Builds and revises polished offline HTML reports, landing pages, infographics and interactive visualizations as a single file, with viewport QA before delivery.
Works with
Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it. Checking A Page is an agent skill from awss1i/assay. Check that a web page you wrote or changed actually works, by opening it in a browser and driving every control on it.
Checking A Page fits situations like: tasks that involve HTML artifacts.
Run `npx skills add awss1i/assay --skill checking-a-page -a claude-code`. Or copy the skill folder (plugins/assay/skills/checking-a-page in awss1i/assay) into .claude/skills/checking-a-page in your project. Claude Code loads it when a task matches its description.
Run `npx skills add awss1i/assay --skill checking-a-page -a codex`. Or copy the skill folder (plugins/assay/skills/checking-a-page in awss1i/assay) into .agents/skills/checking-a-page in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add awss1i/assay --skill checking-a-page -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/checking-a-page, .gemini/skills/checking-a-page, .github/skills/checking-a-page and .opencode/skills/checking-a-page in your project.
Going by SKILL.md and its folder, Checking A Page needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Checking A Page is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 712 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Checking A Page: Anti Detect Browser (antibrow/anti-detect-browser-skills, 932 stars), Ibm A11y Route Scan (langflow-ai/langflow, 156k stars), Language Support (live-codes/livecodes, 1.5k stars) and Sdf Art (shaun8149/sdf-js, 421 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
awss1i (a GitHub user) maintains it in awss1i/assay, which has 102 GitHub stars. The repository was last updated on October 8, 2026.
Source: awss1i/assay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
