'click' 검색 결과

Let an agent launched through cmux inspect and operate macOS apps using screenshots and accessible interface elements. It supports clicking, typing, scrolling, and dragging, with explicit user requests and permissions granted to the local helper.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Ask an agent to click controls in a macOS app
• Enter text into forms or editors
• Check the screen after an action

Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automate form entry and page navigation
• Capture screenshots and extract page data
• Explore web apps for bugs

Find content losing search impressions and clicks using Google Search Console. Rotate through pages based on refresh history, update dated copy, statistics, and internal links, and open a pull request for human review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find articles losing search impressions and clicks
• Refresh outdated copy and statistics in small weekly batches
• Fix internal links to renamed or retired pages

Use a computer connected to Kortix to read and write files, run shell commands, and operate desktop apps. The skill covers machine selection, access checks, screen inspection, and handling connection or permission errors.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reading and editing files on a connected computer
• Running commands on a selected laptop or server
• Clicking and typing in desktop applications

Automate browser tasks such as reading JavaScript-rendered pages, filling forms, clicking through workflows, and taking screenshots. Maintain login sessions, manage separate browsers, and capture network responses, with approval checks for sensitive actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Extracting content from pages that use JavaScript
• Automating form entry and page navigation
• Checking page appearance with screenshots

Analyze Google Ads Quality Score, a keyword-level quality rating, across expected click-through rate, ad relevance, and landing page experience. Identify weak components and their causes, then prioritize fixes by potential click-cost savings and conversion impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Monthly reviews of keyword Quality Scores
• Investigating unexplained increases in click costs
• Checking quality changes after landing page updates

Write Google Ads headlines, descriptions, and responsive search ad components. Create alternative messages for A/B testing, which compares ad versions, and develop copy ideas aimed at improving the click-through rate of existing ads.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Draft headlines and descriptions for a new ad group
• Create components for responsive search ads
• Compare different advertising messages with A/B tests

Improve page titles, meta descriptions, and social sharing previews with multiple alternatives for A/B testing, which compares different versions. Check character counts and preview search results to assess how each option will appear.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Revising titles for pages with low click-through rates
• Drafting multiple meta descriptions for comparison
• Improving link previews shared on social media

Use connected Google Search Console data to check clicks, impressions, search position, and traffic changes by query or page. Inspect indexing status and manage sitemap submissions or removals that have been approved.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking clicks and rankings by search query
• Comparing page performance and traffic changes
• Inspecting whether a URL is indexed

Turn documented app journeys into a test plan covering normal use, edge cases, and failures. Run automated browser tests where possible, check remaining steps manually, and record reproduced bugs with severity, evidence, and fix status.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check every user journey before release
• Add automated browser tests with Playwright
• Test unusual inputs and access restrictions

Automate website navigation, form filling, clicks, data extraction, and screenshots through the browse CLI, a command-line tool. Choose a local browser or a remote Browserbase session to suit the website and task.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating form entry and button clicks
• Extracting page text as Markdown
• Taking screenshots to check page layouts

Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use `test-scenario`.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Click page elements by CSS selector or text content. When you need to click buttons, links, or select options. PREREQUISITE - must use browser_navigate to open target page first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designing quizzes, personality assessments, and recommendation tools that segment users into actionable categories rather than generating clicks for clicks' sake. Question architecture, scoring algorithms, result categorization, recommendation mapping, lead capture integration. Honest about clickbait-quiz (engagement only), vanity-result (entertaining, not useful), and actionable-segmentation (genuine categorization that drives next-step recommendations) patterns. Triggers on quiz, assessment, personality test, recommendation tool, scorecard, diagnostic, fit evaluator, what-type-of-X-are-you, persona quiz. Also triggers when an audience needs a categorization-driven lead magnet, when a vanity quiz is producing engagement but no qualified leads, or when an assessment is being scoped for the first time.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Lift a clickable card toward the viewer on hover with a deepening shadow — a tactile, responsive cue. Pure CSS, no JS. Only use on actually-clickable cards (motion implies clickability). Honors prefers-reduced-motion (static). Avoid on very dense grids where many lifts feel noisy.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for idle/clicker games including big number handling (mantissa + exponent system), exponential growth curves (cost_growth_factor 1.15x), generator systems (auto-producers), offline progress calculation, prestige systems (reset for permanent multipliers), number formatting (K/M/B suffixes, scientific notation). Use for incremental games, idle games, or cookie clicker derivatives. Trigger keywords: idle_game, big_number, exponential_growth, generator_system, offline_progress, prestige_system, number_formatting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert blueprint for idle/clicker games including big number handling (mantissa + exponent system), exponential growth curves (cost_growth_factor 1.15x), generator systems (auto-producers), offline progress calculation, prestige systems (reset for permanent multipliers), number formatting (K/M/B suffixes, scientific notation). Use for incremental games, idle games, or cookie clicker derivatives. Trigger keywords: idle_game, big_number, exponential_growth, generator_system, offline_progress, prestige_system, number_formatting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Thin Bevy genre router for Idle clicker. Keywords: Bevy, Idle clicker, genre, ECS, router.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Point at something on the human's macOS screen with a big arrow and a sign ("Franz, click HERE") using the bigarrow CLI. Use whenever the human has to look at, click, type into or choose a specific spot, button, field, window, tab or menu: show me where, point to it, which button, where do I click, zeig mir wo, guide me through this UI, the human must approve or sign something, or you need the human's hand and they may not be looking at the terminal. Mandatory when it is time-critical: a code that expires, a login or payment page that times out, a build waiting on the human.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fix ClickHouse query errors in Rust when using clickhouse-rs crate. Use when: (1) "string is not valid utf8" errors - typically FixedString columns need CAST to String, (2) "tag for enum is not valid" errors - typically Option<T> fields receiving non-NULL values, (3) Sum/count aggregations returning Float64 but Rust expects u64, (4) LEFT JOIN results with empty strings where Rust expects Option::None, (5) "not enough data, probably a row type mismatches a database schema" - query SELECT returns fewer columns than the Rust Row struct expects (common when multiple query functions share the same struct but one function is missing columns added later), (6) Garbled/corrupted data when INSERTing to FixedString(N) columns using String Rust type - silently corrupts data (no error!) because String adds a length prefix but FixedString expects exactly N raw bytes. Fix: use [u8; N] with #[serde(with = "BigArray")] from serde-big-array, (7) "the trait bound `[u8; 64]: serde::Serialize` is not satisfied" when using [u8; N] arrays in Row structs - need #[serde(with = "BigArray")] annotation from serde-big-array crate.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fix HTTP 500 / ClickHouse "column not found" errors when filtering by a MATERIALIZED column through a VIEW that doesn't expose it. Use when: (1) a WHERE clause references alias.column on a view but the column is MATERIALIZED on the underlying table, (2) the query works on the raw table but fails through the view, (3) adding a new filter param to an API causes 500 even though the column exists in the base table. Fix by using a subquery against the base table instead of referencing the column directly on the view. Applies to ClickHouse views over tables with MATERIALIZED or ALIAS columns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design click/first-click tests to evaluate navigation and information findability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MUST USE when designing ClickHouse architectures, selecting between ingestion or modeling patterns, or translating best practices into workload-specific system designs. Complements clickhouse-best-practices with decision frameworks and explicit provenance labels.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.