'console' 검색 결과

Develop HTML and JavaScript web games through small changes and repeated Playwright tests, which automate browser actions. Inspect gameplay screenshots, text representations of game state, and console errors to check controls, outcomes, and newly added features.

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

• Adding features to a browser game
• Testing movement, jumping, and attacks
• Checking score changes and win or lose transitions

Audit a website for search visibility problems across indexing, technical performance, page content, and links. Produce findings with supporting evidence, estimated impact, and specific fixes organized into a prioritized action plan.

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

• Investigate why important pages are missing from search
• Review page titles, descriptions, and headings
• Check technical SEO after a site migration

Retrieve Google Workspace audit logs, which record account activity, and usage reports through gws. Review activity in applications such as the Admin console and Google Drive, or inspect statistics for the organization, users, and entities.

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

• Reviewing Admin console and Google Drive activity
• Checking organization usage statistics
• Retrieving usage reports for users

Control interactive command-line programs through tmux by sending keystrokes, reading terminal output, and waiting for prompts. Use separate sessions to operate Python consoles or run multiple coding agents while checking their progress and results.

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

• Operate an interactive Python console
• Run multiple coding agents in parallel
• Wait for prompts and inspect terminal output

Audit a website’s technical setup, page elements, and content for search visibility issues. Produce page and site health scores, evidence-backed findings, and a prioritized action plan covering urgent fixes, practical improvements, and longer-term work.

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

• Investigating falling search traffic or rankings
• Reviewing page titles, headings, and internal links
• Checking SEO before or after a site migration

Group keywords by what searchers want and assign each group to an existing or proposed page. Produce a page map, priorities, and content briefs, while checking whether multiple pages compete for the same searches.

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

• Mapping keyword lists to pages
• Planning new pages and updates
• Checking competition between pages on the same site

Operate Chrome or Brave using signed-in browser sessions to verify deployed pages, reproduce bugs, inspect page structure, and examine errors or network traffic. An optional macOS bridge extends control to native applications and operating system input.

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

• Verify page appearance after deployment
• Reproduce blank pages and disappearing content
• Inspect console errors and network traffic

Inspect KubeSphere clusters with read-only commands. List clusters, view detailed configuration, identify host and member roles, and review connection types, readiness indicators, and KubeSphere and Kubernetes versions without changing cluster resources.

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

• List clusters registered in KubeSphere
• Check cluster readiness
• Review KubeSphere and Kubernetes versions

Test local web applications with Python scripts using Playwright, a browser automation tool. Inspect rendered pages, exercise interface controls, capture screenshots and console logs, and use a helper to manage one or more application servers during tests.

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

• Verifying buttons, links, and form inputs in a local app
• Investigating unexpected interface behavior
• Capturing screenshots and browser console logs

Automate browser tasks such as clicking, filling forms, and switching tabs. Inspect page structure, console messages, and network requests, capture screenshots or videos, and work with Playwright tests to check and investigate web page behavior.

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

• Checking form entry and submission flows
• Investigating console errors and network requests
• Capturing screenshots and videos of browser actions

Inspect and control live Chrome pages to investigate display problems, console errors, failed requests, and slow loading. Capture screenshots, automate page interactions, and record performance traces to identify where delays or layout shifts occur.

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

• Investigating page errors and failed network requests
• Finding causes of slow loading and layout shifts
• Capturing screenshots of pages or individual elements

Turn a topic or URL into a keyword plan using Google search volumes, advertising cost per click, and existing rankings. Group related terms into page topics and prioritize where to create or improve content.

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

• Find keyword ideas from a topic or URL
• Plan related articles around a central topic
• Choose between new pages and existing page improvements

Analyze actual GA4 visits from AI services such as ChatGPT and Perplexity. Compare traffic trends, landing pages, and conversions, then identify page patterns and specific content changes that may improve visibility in AI search.

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

• Measuring website visits from AI services
• Comparing AI traffic trends and conversions
• Finding common patterns in pages receiving AI traffic

Prepare screenshots and network traffic records for bug bounty submissions by masking session secrets and personal data while preserving useful verification details. The skill covers capture setup, HAR cleanup, evidence filenames, and credential handling after submission.

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

• Masking secrets in evidence screenshots
• Cleaning HAR files before submission
• Capturing evidence in Burp Suite and Chrome DevTools

Use RQL, a language that chains search and editing steps, to inspect and change Unity Editor content. Find objects, summarize data, update properties, and manage scenes, prefabs, assets, selection, and Play Mode.

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

• Find scene objects and summarize their properties
• Update lighting or object settings in bulk
• Create and manage scenes, prefabs, and assets

Discover keywords from a starting term or niche for SEO and AI search content planning. Compare search volume, competition, search intent, and business relevance, then prioritize opportunities and group related topics to guide content choices.

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

• Finding keyword ideas from a topic
• Prioritizing keywords by demand and competition
• Grouping related topics for content planning

Finds and rewrites code by its syntax structure across 25 languages. Use it to locate matching calls or declarations, preview bulk changes, and run reusable YAML rules that check code or apply fixes.

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

• Finding calls or functions with a specific structure
• Previewing and applying bulk code changes
• Checking code with reusable YAML rules

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data console, or any screen whose job is to show many numbers at once. Covers the layout sequence, the SVG geometry, the accessibility contract per chart type, and the contrast traps that only appear in dark mode.

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

Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".

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

Credentialed Google API calls for a blog: PageSpeed Insights, CrUX history, Search Console performance and URL Inspection, GA4 organic traffic, Cloud NLP entities, YouTube video search, Google Ads Keyword Planner, and the Indexing API (job and livestream pages only). Uses the user's Google credentials, quotas, and sometimes billing, and asks for consent before the first call. Runs only on an explicit request: /blog google, "run PageSpeed on this blog URL", "pull my Search Console data", "inspect this URL's index status", "set up Google API credentials". Shares config with claude-seo at ~/.config/claude-seo/google-api.json.

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

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", "google api setup", "real CWV data", "impressions", "clicks", "CTR", "position data", "LCP", "INP", "CLS", "FCP", "TTFB", or "Lighthouse scores".

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

Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".

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

Find out why something in a running web app does not work, when the console is empty and the code looks correct. Reads the click, the request, the store and the console together and returns the file:line to open. Use when a button does nothing, a form will not submit, data will not load, a page renders blank or stale, a modal will not close, or the user says "it's broken" and the code review says it is fine.

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

Use picocom to interact with IoT device UART consoles for pentesting operations including device enumeration, vulnerability discovery, bootloader manipulation, and gaining root shells. Use when the user needs to interact with embedded devices, IoT hardware, or serial consoles.

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