「search skill」の検索結果

Analyze credential-free public website monitoring evidence from server access logs, HTTP fetches, robots/llms/sitemap checks, and exported summaries while protecting raw IP and private query data. Use this skill when the user asks whether crawlers or AI bots reached a site, whether public SEO/LLM discovery files respond, or how to separate observed facts from unknown Search Console, rank, analytics, or citation claims.

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

Tested reasoning approaches for Claude prompts — 18 variants across 6 categories (Analytical, Strategic, Creative, Technical, Research, Comparative). Use when the user wants a specific reasoning template — retrieving, reviewing, customizing, or combining reasoning instructions for a prompt. Trigger on: "give me the Root Cause Diagnosis approach," "show me the reasoning template for," "I need the Evidence Synthesis method," "show me analytical reasoning options," "combine reasoning approaches for," "show me all reasoning variants." Also use when a prompt produces shallow output and the fix is a reasoning upgrade. Provides 18 tested approaches for analytical, strategic, creative, technical, research, and comparison tasks. If the user is unsure which reasoning method fits, use rootnode-block-selection first if available. Do NOT use for evaluating existing prompts — use rootnode-prompt-validation if available. Do NOT use for project-level audits — use rootnode-project-audit if available.

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

Designs Claude Code prompts and CC environments. Produces CLAUDE.md drafts, agent topologies, scope-authorization frameworks, halt triggers, Skills/hooks/MCP plans, chat-to-CC handoff specs, and EXECUTION_PLAN.md remediation plans. Five modes: DESIGN (new CC deployments), EVOLVE (updates from friction), RESEARCH (evaluate a CC tool/pattern), TEMPLATE (reusable artifacts), REMEDIATE (consume hygiene findings → produce + execute plan). Do NOT use REMEDIATE for direct cleanup (Cat 1–10 — use rootnode-repo-hygiene Phase 2). Do NOT use for hygiene scanning (rootnode-repo-hygiene), chat prompts (rootnode-prompt-validation), or chat Projects (rootnode-project-audit).

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

Use when the user wants to search TR Dizin (trdizin.gov.tr — TÜBİTAK ULAKBİM national academic index) for publications, journals, authors, or institutions; do field-scoped advanced search (title/author/abstract/journal/doi/year/…); apply facet filters (access type, year, language, subject, document type); read a publication's references; or extract a publication PDF as text. Uses the open public JSON API over plain HTTPS — no login, no CAPTCHA, no API key.

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

Django web framework conventions: app layout, settings split (base/local/production), URLconf with app namespacing, CBV and DRF ViewSets, DRF serializers and permissions, form validation, signals, Django admin registration, and middleware. Activated automatically by django-plugin/stack.md. Works alongside python-foundation:python-conventions and django-plugin:django-orm-patterns. Use this skill to: - Structure a Django project with multiple apps and correct URLconf hierarchy. - Write CBVs and DRF ViewSets with appropriate permissions and serializers. - Configure settings correctly for different environments. - Use signals for decoupled event handling between apps. - Register models in Django admin with useful list_display and search_fields. Do NOT use this skill for: - Django ORM model field finalization and migration patterns — see django-plugin:django-orm-patterns. - Python language idioms (type hints, dataclasses, enums) — see python-foundation:python-conventions. - Testing patterns — see python-foundation:pytest-testing.

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

Routing libraries for React SPAs: React Router v6/v7 (most common), TanStack Router (typed, modern), wouter (minimal). Detect what's installed and apply matching patterns. Lazy loading, navigation guards, typed params. Use this skill to: - Configure routes (declarative or file-based). - Use navigation hooks (useNavigate, useParams, useSearchParams). - Lazy-load routes for code splitting. - Implement protected routes / auth guards. - Type-safe params via Zod or framework's built-ins. Do NOT use this skill for: - General React conventions (see react-conventions). - State management (see react-state-management). - Form handling (see react-forms). - Next.js routing (different model — see nextjs-plugin).

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

Use when a SaaS founder needs to set, audit, or redesign pricing — choosing a value metric, structuring tiers and packaging, setting price points, designing discounts, planning a price increase, or optimizing a pricing page. Also for monetization questions like free-to-paid conversion, expansion revenue, willingness-to-pay research, or per-seat vs usage-based. Not for which acquisition channels to use (use channel-expert) or the wording of the pricing page (use copywriter-skill).

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

Create or improve a Senpai target repository's program.md. Use this skill whenever the user wants to point Senpai at a fresh ML or research target repository, define the research objective, primary metric, benchmark contract, allowed edit boundaries, W&B reporting contract, or prepare a repo for autonomous advisor/student experiment loops.

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

Use these skills when you need to discover and explore data assets in the Knowledge Catalog. It allows you to search for entries, lookup specific metadata, and explore aspect types to understand your data platform's assets.

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

Search and browse Cline session history. Use when the user asks to find, list, inspect, or export Cline sessions by time period, prompt content, status, model, provider, source, mode, workspace, or other criteria. Also use when the user wants to read a session transcript or export sessions to a directory. Trigger phrases include "find my session", "search my session history", "show me past sessions", "what was that session where", "find the session that started with", and any mention of past Cline conversations.

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

Expert SurrealDB 3 skill. Use when working with SurrealDB, SurrealQL queries, multi-model data modeling (document, graph, vector, time-series, geospatial), schema design, graph traversal, vector search, security and permissions, deployment and operations, performance tuning, SDK integration, Surrealism WASM extensions, SurrealMCP, Surrealist IDE, Surreal-Sync migrations, SurrealFS, SurrealKit, or ecosystem integrations such as n8n and CodeMirror.

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

Research 3–5 confirmed same-industry or cross-industry websites and translate their brand narrative, page architecture, art direction, and visual-system evidence into one reusable Visual Reference Brief. Use when strong references are scarce, a site needs brand-led or premium positioning, a page lacks a narrative spine, or a key module lacks a credible design precedent. Do not create page content, a Design System, UI directions, HTML, or a permanent brand gallery.

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

Cluster keywords by search intent and map each cluster to an existing or proposed page, with cannibalization detection from Search Console. Use this skill when the user has a keyword list (saved set, brand/keyword-plan.md, GSC export, or seed topic) and needs page targets, content briefs, or a site map for SEO pages — especially before seo-content or seo-machine page generation. Triggers: "cluster keywords", "keyword mapping", "map keywords to pages", "keyword cannibalization", "which page should target".

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

当用户准备写文案/广告/销售材料，需要在动笔前收集和整理信息时调用。 适用于：接到文案委托不知从何开始、写产品文案前做功课、 为新客户准备提案。核心信号：用户说"要写XX的文案"但还没研究产品。 不适用于：已有充分产品知识、纯创意发想（不需要研究支撑）。

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

VictoriaTraces provider for obz. Covers trace search, trace retrieval by ID, and extension commands for service and operation discovery via the Jaeger-compatible HTTP API. This skill should be used when the user mentions "VictoriaTraces", "obz trace -p vt", or needs to search distributed traces from a VT backend.

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

Multi-backend observability CLI for querying metrics, logs, and traces across 12 backends. This skill should be used when the user runs obz commands, constructs metric/log/trace queries, configures providers, parses obz JSON output, or troubleshoots obz errors. Covers all core commands (metric query/list/info/labels/label-values/series, log search, trace search/get), global flags, time formats, output modes, config files, and exit codes.

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

Grafana Tempo provider for obz. Covers trace search, trace retrieval by ID, and extension commands for tag discovery. This skill should be used when the user mentions "Tempo", "Grafana Tempo", "TraceQL", "obz trace -p tempo", or needs to search traces from a Tempo backend.

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

Jaeger provider for obz. Covers trace search, trace retrieval by ID, and extension commands for service and operation discovery. This skill should be used when the user mentions "Jaeger", "obz trace -p jg", or needs to search distributed traces from a Jaeger backend.

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

报告发布员（傅梓铭 Fu）。由 research-chief-editor 主理人在 Phase 5 调度，整合所有部分（标题/日期/目录/引言/章节正文/结论/参考文献/审稿警告）输出最终 Markdown 研究报告。执行终校：格式统一、章节编号连续、分隔线、超链接检查、参考文献去重、术语一致性检查。不修改研究内容本身。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当 Phase 4 完成后，主理人下发 Phase 5 发布任务时激活。

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

草稿审稿人（明鉴秋 Ming）。由 research-chief-editor 主理人调度，按 6 维标准审查章节草稿（来源充分性、事实准确性、观点均衡性、内容深度、结构清晰度、格式规范性），输出 PASS 或 REVISE 判定。尊重 3 轮循环规则：第 3 轮强制 PASS。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人下发 Phase 3.2 审稿任务时激活。

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

报告撰写人（程文成 Cheng）。由 research-chief-editor 主理人在 Phase 4 调度，汇总所有章节通过稿，撰写报告框架部分——深度引言（带引用）、结论（带引用）、目录、APA 格式参考文献列表。输出 JSON。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当所有章节通过审稿后，主理人下发 Phase 4 撰写任务时激活。

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

内容修订员（任润泽 Ren）。由 research-chief-editor 主理人调度，根据 draft-reviewer 的 REVISE 反馈对章节草稿进行修改。逐条回应审稿意见，补充来源、纠正事实、补充反方观点、深化分析，保持未受批评部分不变。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人收到 Phase 3.2 的 REVISE 判定后激活。

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

This skill should be used when the user asks "How do I...", "What is...", "How does X work in Prismatic?", "What's the best practice for...", wants to understand Prismatic concepts, features, or architecture, or needs guidance on marketplace deployment, customer connections, embedded UI, config pages, triggers, or other Prismatic product features. Search and retrieve documentation from prismatic.io/docs and reference examples from github.com/prismatic-io/examples.

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

Entry point for rafter. Invoke when a sub-skill is unclear, or when the task needs `rafter run` (remote SAST+SCA), `rafter secrets` (local secrets-only), `rafter audit`, policy checks, or command-risk evaluation. Scope by security surface, not task label: engage when the diff touches auth, credentials/secrets/tokens, untrusted input, SQL, shell/exec, file paths, deserialization, crypto, network endpoints, data deletion, or dependencies; for research/experimental/local-only code with none of that, a quick surface check is enough. When such surface IS present and no rafter skill or CLI call has been made, invoke this before handing the task off — an un-evaluated "done" on genuine security surface is not done.

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