Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

can i use

v1.0.0

Query browser compatibility for CSS/JS features using caniuse-cli. Use when user asks about browser support, compatibility, "can I use X", "does X work in IE...

0· 65·0 current·0 all-time
by周祺@zhouqicf

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for zhouqicf/caniuse.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "can i use" (zhouqicf/caniuse) from ClawHub.
Skill page: https://clawhub.ai/zhouqicf/caniuse
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install caniuse

ClawHub CLI

Package manager switcher

npx clawhub@latest install caniuse
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (querying browser compatibility) match the SKILL.md: it only directs use of the caniuse CLI and provides feature-name mappings. Nothing requested (env vars, binaries, configs) is outside that purpose.
Instruction Scope
Runtime instructions are narrowly scoped to checking for the caniuse binary and running `caniuse <feature>`, mapping user terms to caniuse feature names, and formatting results. The instructions do not ask the agent to read unrelated files, environment variables, or exfiltrate data.
Install Mechanism
There is no install spec (instruction-only). The SKILL.md suggests installing `@bramus/caniuse-cli` via npm if missing, which is a reasonable, transparent recommendation rather than an automated download.
Credentials
The skill requests no environment variables or credentials. The only implicit requirement is the availability of the caniuse CLI (or the ability to install it), which is proportional to the task.
Persistence & Privilege
always is false and the skill has no install-time persistence or requests to modify other skills or system-wide settings. It does not require elevated or permanent privileges.
Assessment
This skill is a simple instruction-only wrapper for the caniuse CLI and appears safe and coherent. Before installing the suggested npm package yourself, verify you trust the package name (@bramus/caniuse-cli) and your environment's npm/global-install policy (global installs may require elevated privileges). Note that the agent will attempt to run shell commands (which is expected here); if you prefer, run `caniuse` locally and paste results instead of installing anything in a sensitive environment.

Like a lobster shell, security has layers — review code before you run it.

latestvk974p5panfnv0wafxba319jv1x84qckt
65downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Browser Compatibility Query

Query browser compatibility data for web features using the caniuse CLI tool.

Prerequisites Check

Before querying, verify caniuse-cli is installed:

which caniuse || echo "NOT_INSTALLED"

If not installed, tell the user:

caniuse-cli is not installed. Install it with:

npm install -g @bramus/caniuse-cli

Querying Compatibility

Run the caniuse command with the feature name:

caniuse <feature-name>

Feature name formats:

  • Hyphenated: caniuse viewport-units
  • Quoted phrases: caniuse "viewport units"
  • With special chars: caniuse @property

Common feature name mappings (user term → caniuse query):

  • :has() selector → css-has
  • :where() selector → css-where
  • :is() selector → css-matches-pseudo
  • container queries → css-container-queries (size) or css-container-queries-style (style)
  • CSS nesting → css-nesting
  • subgrid → subgrid
  • aspect-ratio → css-aspect-ratio
  • gap in flexbox → flexbox-gap
  • CSS grid → css-grid
  • flexbox → flexbox

JS/API features:

  • ES modules → es6-module
  • async/await → async-functions
  • optional chaining → mdn-javascript_operators_optional_chaining
  • fetch API → fetch
  • service workers → serviceworkers
  • WebGPU → webgpu

Presenting Results

After running the command:

  1. Show the compatibility table as returned by caniuse

  2. Highlight key findings:

    • Which major browsers fully support it
    • Any browsers with partial support (note the limitations)
    • Browsers that don't support it at all
  3. Call out important notes if the output includes numbered notes (these often contain critical info about prefixes, flags, or partial implementations)

  4. Give practical advice based on the results:

    • If widely supported: "Safe to use in production"
    • If partial support: "Works but check the notes for limitations"
    • If poor support: "Consider a polyfill or fallback"

Handling Unknown Features

If caniuse returns "Nothing was found":

  1. Check the mapping table above — many features have specific caniuse names (e.g., :has()css-has)

  2. Try common prefixes:

    • CSS properties: try css- prefix (e.g., css-grid, css-variables)
    • MDN data: try mdn- prefix for JS features
  3. Try variations:

    • Remove special characters: :has()has or css-has
    • Use hyphens: "container queries" → container-queries
  4. If still not found, tell the user:

    This feature might not be in the caniuse database, or uses a different name. Check https://caniuse.com to find the correct feature name.

Comments

Loading comments...