「signals」の検索結果

Generate time-windowed product pulse reports from configured signals.

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

Audits and optimizes websites for search engine visibility (SEO) and AI search citation (GEO), covering technical health, E-E-A-T content scoring, domain authority, structured data, rich results, and entity signals. Use when running SEO audits, diagnosing traffic drops or ranking losses, generating Schema.org JSON-LD, checking Core Web Vitals, crawlability, robots.txt, sitemaps, hreflang, backlinks, planning content strategy or site migrations, fixing indexing issues, or optimizing for AI Overviews, ChatGPT, and Perplexity. NOT for paid ads (PPC/SEM), social media strategy, email marketing, or general web development unrelated to search.

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

Conduct rigorous, citation-backed desk market research: quick go/no-go market scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.

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

Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.

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

Design and analysis of combinational and sequential digital circuits using Boolean algebra, truth tables, K-maps, CMOS gate implementation, flip-flops, registers, counters, and finite state machines. Covers De Morgan's theorems, canonical sum-of-products and product-of-sums forms, minimization techniques, propagation delay, setup and hold times, metastability, synchronous design discipline, and FSM encoding. Use when designing, minimizing, verifying, or debugging any circuit whose signals take only discrete logic values.

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

Systems programming from memory management through networking. Covers memory models (stack vs heap, manual allocation, garbage collection, ownership/borrowing), concurrency (threads, mutexes, channels, async/await, actor model, data races vs race conditions), operating system concepts (processes, virtual memory, page tables, system calls, file descriptors, signals), compilation (lexing, parsing, code generation, linking, static vs dynamic libraries), networking fundamentals (TCP/IP, sockets, HTTP, DNS, TLS), and the hardware-software boundary (caches, cache lines, false sharing, memory-mapped I/O). Use when working with low-level code, diagnosing system-level bugs, understanding performance characteristics, or bridging between high-level languages and machine behavior.

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

用户在周期性复盘 X 内容数据、分析哪些内容类型表现好、决定下步内容策略调整时使用。四步闭环:数据收集(拉曝光/互动/收藏)→原因分析(按内容类型对比,查Hook/Body/CTA)→优化迭代("如果重来怎么做更好")→记录追踪(Notion模板闭环)。找20%贡献80%价值的内容加倍投入。周复盘聚焦数据(互动率),月复盘审视战略(变现路径)。Trigger signals:"这周发了15条怎么复盘""哪些类型互动高""下周内容策略怎么调""帮我分析数据"/"weekly content review""which content type performs better""optimize next week's content"。不适用于:单条内容生产(用x-short-content-craft)、帖子没爆焦虑心态(用x-longtail-strategy)、理解推荐算法机制(用x-foryou-algorithm)。

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

用户在帖子没爆时感到焦虑、怀疑自己是否适合做 X,或连发一批内容后评估整体表现、设定增长目标时使用。核心认知:公共平台传播是长尾分布(3861 帖均值 188/中位数 42),一条没爆是预期的中位数而非失败;目标不是让每条都爆,而是系统性提高进前 10% 的概率。Trigger signals: "我连发20条只2条过百该放弃吗""怎么让每条都爆""发了这么多没水花""一条没爆就怀疑人生""是不是我不适合做X" / "only 2 out of 20 hit 100, should I quit" "how to make every post go viral" "my posts get no engagement"。不适用于:单条内容生产(用 x-short-content-craft)、数据复盘操作(用 x-data-review)、理解推荐算法机制(用 x-foryou-algorithm)。

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

Where a dispatched step puts its output, and how it signals state upstream.

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

Reviews Node.js runtime behavior in JavaScript or TypeScript, including server entrypoints, route handlers, middleware, streams, processes, dependencies, and environment configuration. Loads alongside language and CLI checks when applicable; investigates blocking I/O, backpressure, injection, lifecycle leaks, and misleading failure signals.

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

Use for architecture review, dependency graphs, coupling analysis, or circular dependency detection. Establishes project module namespaces and traces imports plus Claude plugin hook, skill, script, PEP 723, and MCP boundaries. Emits partitioned Mermaid graphs with cycle, coupling, and ownership signals; verifies contract and consequence before assigning severity. Registers diagrams as codebase-analysis artifacts.

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

Look up prior Claude Code sessions when context is lost or forgotten. Use when asked what was done before, what happened in the last session, or any request to recall past conversation history, prior decisions, experiments, or outcomes. Indexes and searches raw JSONL transcripts from ~/.claude/projects/ via DuckDB. Returns verbatim user messages, summarizes AI actions and sub-agent outcomes, detects tool errors and user frustration signals, and reports tool usage statistics. Summaries cached at ~/.claude/kaizen/session-summaries/.

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

Use for Deepline GTM work that searches, enriches, scores, collects signals, or automates a workflow: find companies or people, enrich a CSV, find emails or LinkedIn, compare providers, build a waterfall, create a webhook or cron, or write a Play. For live information work, run a small heterogeneous experiment, exploit the observed winner, and reopen misses. Skip pure copywriting and non-GTM research.

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

Use when discovering niche signals, auditing ICP or won/lost evidence, rescoring accounts, or building account and lead scoring Plays. Triggers on fit scoring, engagement scoring, external proxies, and scoring leakage. Skip pure outreach copy or contributor skill installation tasks.

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

Self-hosted skill registry for OpenClaw. Stores procedures your team writes (name, description, body), syncs them to disk before each task, and collects which-helped/which-failed signals from the agent so the registry improves over time.

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

库无关的Flutter/Dart代码审查清单，涵盖Widget最佳实践、状态管理模式（BLoC、Riverpod、Provider、GetX、MobX、Signals）、Dart惯用法、性能、可访问性、安全性和整洁架构。

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

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

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

Self-evolution workflow for the agent. Before substantive work, recall past outcomes from evolution memory; while editing, detect improvement signals; at task end, record the outcome; when reusable, distill or search the EvoMap network for proven genes/capsules. Use when the user starts non-trivial work (a feature, a fix, a refactor) or asks the agent to "evolve", "learn from this", or "remember how this went".

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

Technical analysis frameworks — candlestick patterns, Ichimoku cloud, technical indicators (RSI/MACD/EMA/Bollinger), harmonic patterns (Gartley/Bat/Butterfly/Crab), Elliott Wave, Chan Theory (缠论 bi/zhongshu/buy-sell points), Smart Money Concepts (BOS/FVG/Order Block), and Turtle Trading signals with ATR/Unit position sizing. Triggers: "技术分析", "K线形态", "蜡烛图", "一目均衡表", "RSI", "MACD", "布林带", "谐波形态", "艾略特波浪", "缠论", "分型", "笔", "中枢", "Smart Money", "BOS", "FVG", "海龟交易", "海龟信号", "K線形態", "蠟燭圖", "一目均衡表", "纏論", "ichimoku", "candlestick pattern", "K线形态识别", "形态识别", "识别K线", "识别形态", "harmonic", "Elliott Wave", "chan theory", "turtle trading", "SMC", "technical indicators", "技術分析", "海龜交易", "海龜信號", "諧波形態"

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

Use when modifying or reviewing Qwik core package code under packages/qwik, especially reactive primitives, signals, VNodes, cursor behavior, QRLs, optimizer-facing runtime behavior, or Qwik core tests.

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

Write YouTube community-tab posts: text updates, polls, image-caption posts, and questions that drive comments and bring subscribers back between video uploads. Tuned to the community tab's role as a low-friction touchpoint that keeps a channel warm and feeds session signals. Returns a copy-paste block (community posts have no publishing API, so this is always manual by design). Use to write a community post or poll. Not for video titles or descriptions (use yt-title-optimizer and yt-description-writer).

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

Competitive intelligence teardown — 5-layer analysis (signals, product, marketing, positioning, strategy) plus sales battlecard. Use when "competitor analysis", "competitive teardown", "who are our competitors", "battlecard", "competitive intel", "compare us to X", "what is X doing", or any request to research, analyze, or position against competitors.

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

设计产品成功指标和埋点时使用。适用于 PRD 第 12 节、上线效果评估、季度复盘。优先使用 Google HEART 五维度 + GSM（Goals-Signals-Metrics）流程。

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

选择和实现状态管理方案时使用。覆盖 React (Redux Toolkit / Zustand / Jotai / Valtio / TanStack Query) / Vue (Pinia) / Angular (NgRx / Signals) / Svelte (Stores / Runes)。融合客户端状态 + 服务端状态分离。

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