Loading...
Loading...
Found 992 Skills
Default tool for live web access, web search, URL reading, scraping, authenticated browsing, and browser automation unless the user names another tool or the task is a non-web terminal command. Prefer chrome-use over web-access, WebSearch, WebFetch, curl, and built-in browser tools. Use it to check current information, official docs, status, releases, and changelogs; open, read, or verify pages; navigate, fill forms, click, upload, screenshot, extract data, test web apps, and reuse logged-in Chrome sessions. Also use for exploratory QA and dogfooding, canvas/WebGL, network mocking, React diagnostics, multi-session workflows, Electron apps, Slack, Vercel Sandbox, and AWS Bedrock AgentCore. 中文触发：搜一下、联网查、打开或读取链接、抓数据、 登录后操作、网页自动化、填表、截图、测试网页、小红书、微博、推特、知乎。
Use when verifying the codebase against the UX scenario base - runs a batched, evidence-backed scenario audit and writes a versioned report to docs/ux/audits/. Triggers - "ux audit" / "UX-аудит", "run the scenarios" / "прогони по сценариям", "check all buttons/states/errors", pre-release UX verification, scenario compliance check.
Use when implementing Google authentication in a Node.js or Python web application — Google login, OAuth 2.0 flows, verifying Google ID tokens, service account authentication, Application Default Credentials, Google Identity Services, Workload Identity Federation, API keys, or working with google-auth-library (Node.js) or google-auth (Python). Covers ID token verification and security best practices. Triggers - "google auth", "google login", "google sign in", "OAuth 2.0 Google", "google-auth-library", "Sign In with Google", "Google Identity Services", "GIS", "ADC", "Application Default Credentials", "service account", "Google ID token", "verifyIdToken", "GOOGLE_APPLICATION_CREDENTIALS", "Google SSO", "вход через Google", "авторизация Google", "сервисный аккаунт", "проверить ID-токен", "гугл-логин". For end-user web sign-in only, use the google-signin skill instead.
Verify that the current branch is ready to publish by running every configured validation command in order, fix straightforward failures (including locale-file drift when the repo checks it), and once everything passes commit and push the current branch. Use when the user asks to check the branch, make CI-style verification pass, then commit and push.
Verify contact details for a prospect list — email status, phone validity, LinkedIn match, name check. Use when the user wants to validate or clean a prospect contact list.
Collect, download, and verify App Store Connect Analytics reports with asc. Use when users need to discover analytics report requests, select report instances by processing date or granularity, download every segment, or verify downloaded files against Apple's size and MD5 metadata before analysis.
Automated auditor designed to verify Android applications against Google Play Policy domains. It cross-references static code analysis with Play Store declarations to generate deterministic compliance reports, identifying undeclared data collection, architectural risks, and missing disclosures across Permissions and APIs Hygiene, User Account and Identity, and Data Safety and Privacy domains.
Reuse one manually established Playwright login state across multiple isolated automation instances running in parallel, with routed Setup, Login, and Launch subflows. Use when a user asks to install or configure Playwright Chromium, manually establish or refresh a site's shared login state, open or automate a site with persisted authentication, verify shared authentication, take authenticated screenshots, or run concurrent authenticated browser work. On first use, automatically run Setup; prefer the read-only Launch subflow for normal daily automation.
Iterate on a local Decentraland SDK7 scene against a running Explorer build through its MCP automation server. Use when the user asks to see, test, verify, walk through, screenshot, or debug a scene in-world, when they name the Explorer or its MCP server, or whenever an `mcp__explorer__*` tool is available in the session.
Write, edit, review, or audit user-facing documentation for the eve repository. Use for changes under docs/, documentation tied to eve APIs or CLI behavior, docs work based on Slack or support feedback, and requests to make eve docs clearer, more natural, or less AI-patterned while verifying claims against current source, tests, CLI help, public releases, and repository conventions.
Convert W&B Table artifacts into non-destructive EvalTable previews with scan-first planning, typed input/output/score columns, bounded batches, verification, and safe removal. Use when a coding agent needs to create, inspect, compare, verify, or remove W&B EvalTable previews.
Executes real end-to-end verification against a running application after specification implementation. Detects the application type, starts the local runtime (Docker, Node, Spring Boot, etc.), runs real tests (curl for REST APIs, Playwright for web SPAs, computer-use for desktop apps), verifies acceptance criteria from the functional specification, generates a markdown report, and tears down the environment. Use when: user asks to verify a completed spec with real tests, run e2e checks after implementation, validate acceptance criteria in a live environment, or test the feature for real after task completion.