297 件 ・ 関連度順
概要と使いどころ
App Intents for Siri, Shortcuts, Spotlight, and Apple Intelligence integration including intent modes, interactive snippets, visual intelligence, and entity indexing. Use when implementing Siri integration, App Shortcuts, or Spotlight indexing.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, browser heavy. Unions every sitemap each property declares without a browser, builds the candidate set from URLs not already in the indexing ledger, then drives the member's own search performance console to inspect each candidate and request indexing inside an account wide allowance. Spends what is left on sitemap health, which is unmetered. It inspects, requests, and views or submits sitemaps inside that console and does nothing else there, ever, and it never removes a sitemap.
日本語の概要は準備中です。原文の説明を表示しています。
Use ManagedCode.MarkItDown when a .NET application needs deterministic document-to-Markdown conversion for ingestion, indexing, summarization, or content-processing workflows. USE FOR: ManagedCode.MarkItDown integration; document ingestion flows; Office or rich-text conversion to Markdown; indexing and summarization pipelines. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
Implements the right to be forgotten in search engines under GDPR Article 17 and the CJEU Google Spain ruling (C-131/12). Covers delisting request procedures, criteria assessment balancing privacy against public interest, and geographic scope determination. Activate for right to be forgotten, search delisting, Google Spain, de-indexing queries.
日本語の概要は準備中です。原文の説明を表示しています。
Google Search Console indexing assistant. Use when the user wants to track page indexing status, compare sitemap against GSC indexed pages, manage submission tracking, or move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list. Maintains two tracking files (indexed.md, to-index.md) with prioritization support.
日本語の概要は準備中です。原文の説明を表示しています。
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuningUse when "adding search to, algolia, instantsearch, search api, search functionality, typeahead, autocomplete search, faceted search, search index, search as you type, algolia, search, instantsearch, indexing, relevance, faceted-search, autocomplete" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Algolia Search Integration workflow skill. Use this skill when the user needs Expert patterns for Algolia search implementation, indexing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Designs product and site search for end users. Use when choosing search engines, indexing, reindexing, relevance tuning, facets, autocomplete, merchandising, or search analytics.
日本語の概要は準備中です。原文の説明を表示しています。
Semantic codebase search, code indexing, and prompt enhancement via standalone CLI. Use when: (1) Semantic code search with natural language queries, (2) Code indexing for remote codebase retrieval, (3) Prompt enhancement with codebase context, (4) Before grep/find/glob operations for better accuracy, (5) Complex requirements clarification, (6) Large codebase navigation. Triggers: "search context", "enhance prompt", "find code that", "index project", "clarify requirements". IMPORTANT: Always use ace-tool BEFORE grep/find/glob for semantic-level code location.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Apply practical DAG decomposition, transitive-edge reduction, and reachability indexing to dense dependency graphs. Use when low width and repeated queries justify preprocessing. NOT for cyclic graphs, one-off graph checks, or exact-minimum-chain requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Audit Bing search visibility, Webmaster Tools evidence, and IndexNow readiness when authorized tools are available. Use for Bing indexing, link, crawl, or Microsoft search visibility work; not for Google indexing assumptions.
日本語の概要は準備中です。原文の説明を表示しています。
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query writing unless user asks for performance or index help. Prefer indexing as optimization strategy. Use MongoDB MCP when available.
日本語の概要は準備中です。原文の説明を表示しています。
Database optimization v3 — query plans, partitioning, indexing, connection pooling, PostgreSQL, MySQL
日本語の概要は準備中です。原文の説明を表示しています。
Expert en optimisation de bases de données (query plans, indexing strategies, partitioning, vacuum)
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Access Google Search Console for SEO data such as queries, clicks, impressions, rankings, and indexing status across sites. Use when diagnosing search performance or indexing issues.
日本語の概要は準備中です。原文の説明を表示しています。
Google Analytics 4, Search Console, and Indexing API toolkit. Analyze website traffic, page performance, user demographics, real-time visitors, search queries, and SEO metrics. Use when the user asks to: check site traffic, analyze page views, see traffic sources, view user demographics, get real-time visitor data, check search console queries, analyze SEO performance, request URL re-indexing, inspect index status, compare date ranges, check bounce rates, view conversion data, or get e-commerce revenue. Requires a Google Cloud service account with GA4 and Search Console access.
日本語の概要は準備中です。原文の説明を表示しています。
Apply practical DAG decomposition, transitive-edge reduction, and reachability indexing to dense dependency graphs. Use when low width and repeated queries justify preprocessing. NOT for cyclic graphs, one-off graph checks, or exact-minimum-chain requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Apply practical DAG decomposition, transitive-edge reduction, and reachability indexing to dense dependency graphs. Use when low width and repeated queries justify preprocessing. NOT for cyclic graphs, one-off graph checks, or exact-minimum-chain requirements.
日本語の概要は準備中です。原文の説明を表示しています。
PostgreSQLのテーブル設計、検索を速める索引、行単位のアクセス制御を見直し、遅いSQLの調査や接続設定の改善に役立つ実装例を参照するスキル。
MySQLとMariaDBのテーブル設計や遅いSQLを見直し、インデックス、更新処理、接続管理、複製の遅延を点検して、修正案と検証手順をまとめるスキル。
Itôのバスケットや予測市場のデータを閲覧・整理し、手元の調査メモとの比較、出典付きの市場概要、人が確認するための計画シートを作成します。