lynx-check-css-support — Claude Code skill: how to install
lynx-check-css-support is a Claude Code skill that checks CSS property and value support across Lynx backends using bundled data.
Apache-2.0 201 installs ★ 28 updated 2026-10-24
npx skills add lynx-community/skills --skill lynx-check-css-support -a claude-codeWhat lynx-check-css-support does
The skill runs a local Node.js script query-css-compat.mjs against bundled compatibility records. It checks whether a CSS rule works on a target backend like Android or Harmony, pinpoints the introduced version, and flags nested values such as display: grid or filter: brightness().
All compatibility entries are frozen into the package during build time. Queries execute entirely offline, though you need Node.js installed locally to execute the CLI script.
Checking data freshness via --check-updates only reads the latest package version number from npm. The script never downloads new definitions on the fly, so dataset updates require bumping the skill dependency itself.
What it helps with
- find minimum Lynx versions for specific CSS properties
- verify style compatibility for Android or Harmony backends
- inspect nested CSS feature support without guessing browser parity
- check whether the bundled
@lynx-js/css-definesdataset is up to date
Example prompts for the agent
- Check if display: grid is supported on Lynx Android version 2.0
- Which Lynx backends support the filter property with brightness?
- Run lynx-check-css-support with --check-updates to inspect dataset freshness
How to install lynx-check-css-support
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-check-css-support -a claude-code2Manually: put the files in place
~/.claude/skills/lynx-check-css-support/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/lynx-check-css-support/
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-check-css-support -a codex2Manually: put the files in place
.agents/skills/lynx-check-css-support/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-check-css-support -a cursor2Manually: put the files in place
.cursor/skills/lynx-check-css-support/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lynx-community/skills skills/lynx-check-css-support2Manually: put the files in place
.github/skills/lynx-check-css-support/SKILL.md1Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-check-css-support -a gemini-cli2Platform CLI
gemini skills install https://github.com/lynx-community/skills --path skills/lynx-check-css-supportManually: put the files in place
.devin/skills/lynx-check-css-support/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lynx-community/skills --skill lynx-check-css-support -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about lynx-check-css-support
How to install lynx-check-css-support in Claude Code?
Run npx skills add lynx-community/skills --skill lynx-check-css-support -a claude-code in your terminal. The configuration writes to ~/.claude/skills/lynx-check-css-support/SKILL.md.
What does lynx-check-css-support do?
It queries the @lynx-js/css-defines compatibility database to report CSS property and nested value availability across Lynx engine versions.
Does running queries trigger network downloads?
No, compatibility data is bundled directly with the skill. The network is only queried when running --check-updates to check the latest npm release number.
Source text
SKILL.md · Apache-2.0
--- name: lynx-check-css-support description: Query @lynx-js/css-defines compat_data to check Lynx CSS property and nested feature/value support by rendering backend and Lynx version, or check whether a newer dataset version exists. Use when asked whether CSS is supported in Lynx or ReactLynx, which backends support it, when support was added, whether a style change is compatible, whether the bundled data is current, or when inspecting the raw definition JSON. --- # Check Lynx CSS Support Use the bundled CLI instead of inferring Lynx support from browser CSS behavior, documentation examples, or TypeScript types. Its data is pinned and bundled when the skill is built, so running a query never downloads or executes packages. Treat this skill as the authority for declared backend/version availability. For questions about how a property behaves, layout semantics, syntax, or usage examples, consult the official Lynx documentation. If a request asks both whether a feature is supported and how it behaves, query support here first, then consult the docs. ## Query support Resolve this skill directory, then run: ```bash node <skill-directory>/scripts/query-css-compat.mjs <property> [options] ``` Query the property's base compatibility across every backend: ```bash node <skill-directory>/scripts/query-css-compat.mjs display ``` Pass the user's backend and Lynx version when provided. Omitting `--backend` returns every backend. `--lynx-version` classifies availability for that target; it does not change the published `version_added` value. ```bash node <skill-directory>/scripts/query-css-compat.mjs display \ --feature grid \ --backend android \ --lynx-version 2.0 ``` Pass nested feature keys exactly as published. They are case-sensitive and may contain punctuation, such as `Flex`, `rotateX`, or `circle()`. If the exact key is unknown, inspect the property's `compat_data` with `--json` before querying the feature. ```bash node <skill-directory>/scripts/query-css-compat.mjs filter \ --feature brightness \ --backend harmony \ --lynx-version 3.5 \ --json ``` ## Report findings Give a concise answer containing: - The property and nested feature/value, if any. - The requested backend and Lynx version, or that all backends were compared. - The resulting `availability` and published `version_added` value or condition. - Any relevant notes, `partial_implementation`, deprecated, or experimental status. - The `@lynx-js/css-defines` version shown by the script. If a definition has no `compat_data`, report that compatibility is unspecified by the dataset. Do not interpret missing compatibility data as unsupported. Never claim backend support from the definition's top-level `version` or a value's `version` field when `compat_data.__compat.support` provides backend-specific evidence. Do not treat declared availability as proof of browser parity or complete runtime behavior. ## Interpret results Treat `version_added` as follows: - A numeric version string is the minimum Lynx version for that backend. - A non-numeric string is a conditional requirement such as a `targetSdkVersion` gate; preserve and report it verbatim. - `true` means supported without a numeric minimum in the dataset. - `false` means unsupported. - `null` means unknown. Treat `availability` as follows: - `available`: supported at the requested version, or supported at some version when no target was supplied. - `requires-newer-version`: supported only after the requested version. - `conditional`: support depends on the non-numeric condition shown in `version_added` and cannot be decided from the Lynx version alone. - `unavailable`: explicitly unsupported. - `unknown`: not established by the dataset. ## Keep data current Report the displayed package version with every compatibility answer. When the user asks whether the data is current, or freshness is important to the task, run: ```bash node <skill-directory>/scripts/query-css-compat.mjs --check-updates ``` Use `--json` when structured output is useful. The check reads only the latest numeric version from the public npm registry. It does not download dataset files, modify the bundled copy, or accept cache overrides. If an update is available, report both versions and recommend updating the skill. Compatibility data changes only through reviewed skill releases that bump the pinned dependency.
© lynx-community · Apache-2.0 · lynx-community/skills