「search skill」の検索結果

Use this skill when the user wants the full existing-registry Trust Magnitude inspector: understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".

日本語の概要は準備中です。原文の説明を表示しています。

Generate a prioritized review queue of registry skills and catalog items that need attention. Use this skill whenever someone asks: "what needs review?", "what's overdue for audit?", "where are the weak spots in the registry?", "what should I audit next?", "run a health check on the registry", "show me flagged skills", "find problems in the registry", "what skills need fixing?", or "triage the registry". This is the triage layer — it surfaces candidates ranked P0–P4 so that focused work (via /gaia-audit) targets the right things first. Run this before any audit pass. Also invoke proactively when a PR changes registry/named/ at scale, or before a release, to catch regressions early.

日本語の概要は準備中です。原文の説明を表示しています。

Curate Gaia bot crawler branches into real-skill catalog entries and clean up processed bot/* branches. Use when the user says: "process bot branches", "curate the crawl output", "clean up bot proposals", "run bot curation", "merge the crawler results", "review bot/* branches", "ingest crawler data", or explicitly types /gaia-bot-curate. Also triggers when the user asks to review pending `bot/*` branches, turn crawler JSON proposals into registry nodes, decide which crawled skills to accept vs reject, or batch-add skills from an automated crawl run. This skill handles the full pipeline: fetch remote bot branches, triage proposals, run `gaia dev` mutations, validate, open a PR, and delete consumed bot branches.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user wants to understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever the user wants to see how their branch will look on the live Gaia website before merging — "preview this branch", "show me what this looks like", "deploy a preview", "trigger a design preview", "can I see the site with these changes", "preview the skill profile", "check how this renders on the site", "spin up a preview deployment". This skill dispatches a Cloudflare Worker preview deployment for the current branch via GitHub Actions — no local build tooling required. Ideal for containerized environments, design reviews, and confirming that newly curated skills or profile pages render correctly before a PR is merged to main. The preview does NOT regenerate docs; it deploys `docs/` from the branch as-is. If your change depends on regenerated Class S artifacts, run `gaia dev docs` and commit those first — the preview then reflects them.

日本語の概要は準備中です。原文の説明を表示しています。

Firecrawl gives AI agents and apps fast, reliable web context with strong search, scraping, and interaction tools. One install command sets up three skill segments: live CLI tools, app-integration build skills, and outcome-focused workflow skills. Route the reader to the right usage path after install.

日本語の概要は準備中です。原文の説明を表示しています。

Triage and classify pending Gaia skill intake batches in registry-for-review/. Use for gaia push intake proposals, draft skill batches, and deciding whether proposals should proceed to canonical curation. This skill is read-only and never promotes skills itself.

日本語の概要は準備中です。原文の説明を表示しています。

Check Spring Boot skill content freshness against latest research and flag skills needing updates. Use when running /spring-refresh, or when user mentions "refresh spring skills", "spring boot update check", "skill freshness", "stale spring content", "update spring boot skills".

日本語の概要は準備中です。原文の説明を表示しています。

Full-spectrum product research pipeline. Runs competitive analysis, technology trend scouting, user feedback analysis, and feature ideation. Triggers: on: research, competitive research, market research, feature discovery, what should we build next.

日本語の概要は準備中です。原文の説明を表示しています。

Design a research study. Use when the user says "study design", "design my research", "what research method should I use", "how do I test this hypothesis", "research plan", "methodology section", "experimental design", "survey design", "qualitative study design", "how to structure my study", "sample size", "data collection plan", or needs to plan how to test a research question or hypothesis - even if they don't explicitly say "study design".

日本語の概要は準備中です。原文の説明を表示しています。

Build or refine the Ideal Customer Profile (ICP) and personas using the Jobs-to-be-Done framework (Clayton Christensen / Bob Moesta). Use when the user asks for ICP research, persona development, "who are our customers", buyer personas, audience research, "build our ICP", target customer definition, or wants to update persona docs. JTBD interview questions, three job dimensions (functional/emotional/social), and the Four Forces of Progress are wired into every persona. Writes to knowledge/icp/personas.md so all other skills get smarter. For the individual buyer persona rather than the segment, see customer-persona. For sourcing real customer language, see customer-research.

日本語の概要は準備中です。原文の説明を表示しています。

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".

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing or reviewing list views, compact layouts, highlights panels, and search-result presentation so users can scan, find, and act on records quickly across desktop and mobile. Covers the deployable ListView, CompactLayout, SearchLayouts and ProfileSearchLayouts metadata: filterScope, booleanFilter, sharedTo, compactLayoutAssignment, and the package.xml shapes for each. Triggers: 'too many list views', 'compact layout not showing the right fields', 'search layouts vs list views', 'mobile highlights panel', 'list view missing after sandbox refresh', 'deploy a list view between orgs', 'list view column deployed blank', 'compact layout deploy failed', 'compact layout was named in package.xml but was not found in zipped directory'. NOT for page layouts or record types — use admin/record-types-and-page-layouts. NOT for Dynamic Forms — use admin/dynamic-forms-and-actions.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when configuring or troubleshooting the Salesforce CPQ Guided Selling wizard: Quote Process records, ProcessInput questions that filter products by field value, mapping answers to Product2 classification fields, and search type choice (Standard, Enhanced, Custom). Trigger keywords: CPQ guided selling, quote process wizard, product selection wizard, SBQQ__QuoteProcess__c, SBQQ__ProcessInput__c, guided product selection, auto select product, product search plugin. NOT for bundles, product options, or product rules — use admin/cpq-product-catalog-setup. NOT for writing a custom ProductSearchPlugin in Apex — use apex/cpq-apex-plugins.

日本語の概要は準備中です。原文の説明を表示しています。

Produce a researched long-form article from a topic prompt via an orchestrated pipeline - research agent (first-person sources, working-definition gate), narrative-architecture outline, writer/cold-reviewer loop with an explicit ACCEPT/REVISE verdict contract, then a catalog-deslop pass with a regression gate. The orchestrator dispatches subagents only; the writer never judges its own draft. Use when the user says "article factory", "write an article about X", "run the article pipeline", or asks for a researched long-form piece produced end-to-end. For essays and micro posts in the user's own voice without a research stage, use the prose skill instead.

日本語の概要は準備中です。原文の説明を表示しています。

Search the web with LLM-optimized results via the Tavily CLI. Use this skill when the user wants to search the web, find articles, look up information, get recent news, discover sources, or says "search for", "find me", "look up", "what's the latest on", "find articles about", or needs current information from the internet. Returns relevant results with content snippets, relevance scores, and metadata optimized for LLM consumption. Supports domain filtering, time ranges, and multiple search depths.

日本語の概要は準備中です。原文の説明を表示しています。

Research current job markets and hiring requirements, analyze recent job descriptions (JDs), compare them with a user's resume, projects, skills, and constraints, and turn evidence gaps into prioritized career actions. Use when students, job seekers, or career changers ask about current role or industry outlook (including “现在行情怎么样”), whether a role or JD fits them (including “这个JD适合我吗”), cross-platform JD sampling, resume evidence gaps or truthful tailoring, what career skill to learn next, target-role course or certificate decisions, application readiness, or a capacity-bounded 30/60/90-day job-search plan. Do not use for unrelated personal or education advice, simple factual lookups, automatic job applications, or unsupported resume rewriting.

日本語の概要は準備中です。原文の説明を表示しています。

Transparent, rigorous research with full methodology — not a black-box API wrapper. Conducts exhaustive investigation through mandated 2-cycle research per theme, APA 7th citations, evidence hierarchy, and 3 user checkpoints. Self-contained using native OpenClaw tools (web_search, web_fetch, sessions_spawn). Use for literature reviews, competitive intelligence, or any research requiring academic rigor and reproducibility.

日本語の概要は準備中です。原文の説明を表示しています。

Search and analyze Reddit discussions for market research, product feedback, and community insights using Xpoz. Use when asked to "search Reddit", "what does Reddit think about X", "Reddit feedback on X", "subreddit analysis", or "Reddit market research".

日本語の概要は準備中です。原文の説明を表示しています。

Produces an attorney-ready memo from a corpus of legal documents supplied by the user. Use when a user shows up with a folder, zip, or vault of case documents and asks for a case summary, case evaluation, litigation package, intake memo, matter overview, or "can you summarize this case for me." The skill ingests the corpus into a searchable index, OCRs anything non-searchable, inventories and diagnoses the practice area, loads the appropriate practice-area playbook module(s) (PI/tort, commercial litigation, IP infringement, or user-authored extensions), iteratively searches the corpus across eight core dimensions plus any module-specific dimensions, defers specialized document clusters (depositions, medical records, discovery, liens) to dedicated sibling skills, and synthesizes a cited memo.

日本語の概要は準備中です。原文の説明を表示しています。

Search and install skills from skills.sh marketplace when internal skills are insufficient

日本語の概要は準備中です。原文の説明を表示しています。

Find UX pains and opportunities fast through competitor scans, pattern research, and web search. Surfaces how others solve the same flow, common failure modes, and conventions users already expect. Use when the user says "research this UX", "how do others do X", "competitor scan", "find UX patterns", "what's the convention for Y", or before ideating a flow. Part of the Product Design set. Uses web search/fetch tools.

日本語の概要は準備中です。原文の説明を表示しています。

Route ordinary public-web information tasks to the correct Tavily CLI operation. Use when the task concerns publicly accessible webpages and needs web discovery, clean extraction, URL mapping, same-site crawling, or public-web-only research, but the exact Tavily operation is not yet clear or several operations must be sequenced. Prefer the specific leaf skill when intent is clear: tavily-search for discovery without a URL, tavily-extract for known URLs, tavily-map for URL/site-structure discovery, tavily-crawl for content from many pages on one site, tavily-research for cited multi-source synthesis, and tavily-dynamic-search for programmatic filtering with context isolation. Do not use for named social/community/media/career/code platforms, login or cookie-dependent content, platform-native discussions, or cross-platform collection; use Agent Reach there. Do not use for local files, Git operations, deployments, or ordinary code editing.

日本語の概要は準備中です。原文の説明を表示しています。

医学证据等级排序与编排层 skill。当用户请求"证据等级 / GRADE / 证据排序 / 医学证据评估 / evidence grading / quality of evidence / 系统评价排序 / 临床证据排序 / 证据金字塔"时触发。本 skill 不直接调用 NCBI/Europe PMC/ClinicalTrials API,而是编排 6 个底层原子 skill(pubmed-eutils / europepmc-search / clinical-trials-v2 / aact-bulk-trials / bioc-fulltext-fetch / pubtator-entity-search)的召回结果,按 ChatGPT 推荐的证据金字塔(指南 > Meta > RCT > Cohort > Case-Control > Case Report)做 GRADE 自动评级,自动剔除 editorial / letter / comment。优先使用 BioMCP MCP server 做 fan-out(genomoncology/biomcp),无 BioMCP 时走自建 slow-path 兜底。

日本語の概要は準備中です。原文の説明を表示しています。