Tap
WarnAudited by ClawScan on May 10, 2026.
Overview
Tap appears purpose-built for browser automation, but it can control logged-in browser sessions and publish content without documented per-action approval safeguards.
Review this skill carefully before installing. It is coherent for browser automation, but use it with explicit human approval for any posting, form submission, purchase, deletion, or account change, and consider running it in a separate browser profile with only the accounts and tabs you intend to automate.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent using this skill could click buttons, type into forms, make page-context requests, or post content through accounts already open in the browser.
The skill exposes generic browser-control and page-context request tools, plus workflows that publish content to public services. The artifacts do not describe per-action approval, allowlists, or safeguards before account-impacting actions.
`page.click({ target })`, `page.type({ selector, text })`, `page.fetch({ url })` ... `tap.run x/post` ... `xiaohongshu/publish` ... `telegraph/publish`Install only if you want broad browser automation. Require explicit confirmation before posting, submitting forms, purchasing, deleting, or changing account data, and consider using a separate browser profile.
If you are signed in to a website, Tap may be able to act with your account permissions on the active tab.
Debugger-based active-tab automation is central to the skill, but it means the tool can act within authenticated browser pages even though no explicit credential is declared.
The extension requires `debugger` permission to send CDP commands to the active tab ... Tap operates on the active browser tab when invoked.
Use a dedicated browser profile or log out of sensitive sites before using Tap, and avoid granting access on financial, admin, or production accounts unless necessary.
Your safety depends on the external Tap binary, extension, and installed community scripts matching the documented behavior.
The runnable binary, Chrome extension, and optional community scripts come from external sources that were not included in the provided artifact set.
Download the latest binary from GitHub Releases ... Download `tap-extension.zip` ... `tap install` clones scripts from `tap-skills`.
Verify the Homebrew formula, release artifacts, extension manifest, and community `.tap.js` scripts before use; prefer pinned versions and trusted commits where possible.
A saved automation script may keep running in future sessions even after the website or your intended use changes.
Saved taps are persistent automation instructions that can be reused across future runs; this is disclosed and purpose-aligned, but persistent scripts can become stale or unsafe if not reviewed.
`forge.save({ site: "example", name: "data" })` persists the skill ... User-forged taps are stored locally in `~/.tap/taps/`.Review and prune saved taps under `~/.tap/taps/`, especially before using them on authenticated or high-impact sites.