654 件 ・ 関連度順
概要と使いどころ
Create, filter, refresh, and activate audience segments in Salesforce Data Cloud: segment types (Standard, Real-Time, Waterfall, Dynamic, Data Kit), segment refresh schedules, activation field mapping, audience publishing. NOT for the SQL metrics a segment filters on - use admin/data-cloud-calculated-insights. NOT for ingestion, DLO to DMO mapping and identity resolution - use data/data-cloud-data-streams.
日本語の概要は準備中です。原文の説明を表示しています。
เขียน SQL วิเคราะห์ insight สรุป finding และออกแบบ dashboard — แปลงตัวเลขเป็น action
日本語の概要は準備中です。原文の説明を表示しています。
Analysis of Competing Hypotheses. Operationalizes Richards Heuer's CIA-tradition technique for systematically narrowing among multiple hypotheses against evidence. Builds an explicit hypothesis-vs-evidence matrix and focuses on disconfirmation rather than confirmation — the central insight: hypotheses cannot be proven, only disconfirmed; the surviving hypothesis is the one with the least disconfirming evidence. Spawns parallel hypothesizers (in isolation, across hypothesis-generation angles) and parallel evidence-gatherers (across evidence classes), then synthesizes into a matrix, diagnosticity analysis, sensitivity analysis, and falsification milestones. Produces feedback only — no code, no tickets, no artifacts.
日本語の概要は準備中です。原文の説明を表示しています。
Manages datasets, tables, and jobs in BigQuery, and integrates with BigQuery ML and Gemini for advanced data analytics and AI-driven insights. Use when you need to interact with BigQuery, run SQL queries, manage BigQuery resources, or leverage BigQuery's built-in ML capabilities. Also use when performing data analysis, ingesting data into BigQuery, or developing AI applications on BigQuery.
日本語の概要は準備中です。原文の説明を表示しています。
AI-powered revenue intelligence: sales call insight extraction, content-to-revenue attribution, and multi-source client reporting. Use when asked to analyze sales calls, build revenue attribution models, or generate client reports.
日本語の概要は準備中です。原文の説明を表示しています。
Dr. Kaia Chen - AI Architect, mentor, and strategic advisor for Marcus. Use when the user says "Kaia", "Dr. Chen", "ask Kaia", "/kaia", or wants architectural advice, trade-off analysis, production readiness guidance, mentorship, a voice of reason, or a second opinion on design decisions. Kaia grounds her advice in the actual codebase (via Chen MCP tools) and research literature, and logs important decisions and insights via Simon.
日本語の概要は準備中です。原文の説明を表示しています。
Use Notion to track meeting patterns, identify communication insights, and improve team coordination. Record decisions, attendees, and outcomes for trend analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Systematically document research findings, competitive analysis, market trends, and user insights in Notion. Build searchable research repository for data-driven decisions.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Use when facing SEO algorithm questions, content strategy decisions, Threads growth planning, GEO optimization, AI tool selection for SEO, or evaluating SEO vendors. Triggers on any algorithm or content marketing decision — even without mentioning darkseoking. Every insight is backed by patent numbers or tested data.
日本語の概要は準備中です。原文の説明を表示しています。
Stores a persistent memory or learning with `bd remember` so it survives across sessions. Use when the user invokes `/bdr` or `$bdr`, or asks to remember, note, or persist an insight in a Beads workspace.
日本語の概要は準備中です。原文の説明を表示しています。
Applies insights from MetaGPT paper on how structured communication, role specialization, and SOPs prevent coordination failures in multi-agent LLM systems
日本語の概要は準備中です。原文の説明を表示しています。
Professional network graph analyst identifying Gladwellian superconnectors, mavens, and influence brokers using betweenness centrality, structural holes theory, and multi-source network reconstruction. Activate on 'superconnectors', 'network analysis', 'who knows who', 'professional network', 'influence mapping', 'betweenness centrality'. NOT for surveillance, discrimination, stalking, privacy violation, or speculation without data.
日本語の概要は準備中です。原文の説明を表示しています。
Search Reddit posts by meaning via the reddapi.dev index.
日本語の概要は準備中です。原文の説明を表示しています。
Intelligently analyze git status and provide insights about current project state
日本語の概要は準備中です。原文の説明を表示しています。
Use when setting up Laravel Pulse — real-time dashboard, built-in cards, custom recorders, performance insights — even when the user just says 'I need app monitoring' without naming Pulse.
日本語の概要は準備中です。原文の説明を表示しています。
Deep analysis of articles/long-form via thinking frameworks (SCQA, mental models, inversion) — 'analyze article', 'deep dive', 'extract insights', URL/text wanting depth not summary.
日本語の概要は準備中です。原文の説明を表示しています。
Agentes de voz representam a fronteira da interação com IA - humanos falando naturalmente com sistemas de IA. O desafio não é apenas reconhecimento e síntese de fala, mas alcançar fluxo de conversa natural com latência inferior a 800ms enquanto se lidam com interrupções, ruído de fundo e nuances emocionais. Esta habilidade cobre duas arquiteturas: fala-para-fala (OpenAI Realtime API, menor latência, mais natural) e pipeline (STT→LLM→TTS, mais controle, mais fácil de depurar). Insight-chave: latência é a restrição. Hu
日本語の概要は準備中です。原文の説明を表示しています。
Plataforma de observabilidade de IA de código aberto para rastreamento de LLM, avaliação e monitoramento. Use ao debugar aplicações de LLM com rastreamentos detalhados, executar avaliações em datasets ou monitorar sistemas de IA em produção com insights em tempo real.
日本語の概要は準備中です。原文の説明を表示しています。
Ferramentas são como agentes de IA interagem com o mundo. Uma ferramenta bem projetada é a diferença entre um agente que funciona e um que alucina, falha silenciosamente ou custa 10x mais tokens do que o necessário. Esta skill cobre design de ferramentas desde schema até tratamento de erros. Melhores práticas em JSON Schema, escrita de descrições que realmente ajudam o LLM, validação e o emerging padrão MCP que está se tornando a língua franca para ferramentas de IA. Insight-chave: Descrições de ferramentas são mais importantes que implementação
日本語の概要は準備中です。原文の説明を表示しています。
Memória é a base de agentes inteligentes. Sem ela, cada interação começa do zero. Esta skill cobre a arquitetura de memória de agentes: curto prazo (janela de contexto), longo prazo (vector stores), e as arquiteturas cognitivas que as organizam. Insight-chave: Memória não é apenas armazenamento - é recuperação. Um milhão de fatos armazenados não significam nada se você não conseguir encontrar o certo. Estratégias de chunking, embedding e recuperação determinam se seu agente se lembra ou esquece. O campo é fragm
日本語の概要は準備中です。原文の説明を表示しています。
Agentes autônomos são sistemas de IA que conseguem decompor objetivos, planejar ações, executar ferramentas e se auto-corrigir sem orientação humana constante. O desafio não é torná-los capazes - é torná-los confiáveis. Cada decisão extra multiplica a probabilidade de falha. Esta habilidade cobre loops de agentes (ReAct, Plan-Execute), decomposição de objetivos, padrões de reflexão e confiabilidade em produção. Insight-chave: taxas de erro compostas matam agentes autônomos. Uma taxa de sucesso de 95% por passo cai para 60% b
日本語の概要は準備中です。原文の説明を表示しています。
Run evidence-disciplined Xiaohongshu social listening for foreign pharma employee pain points. Use when the user asks to collect and analyze notes/comments about pharma companies, aliases, roles, compliance, medical affairs, or AI topics, then produce a cited and scored sampled-insight report. Includes independent-evidence counting, MediaCrawler batch collection, and CAPTCHA/461 fallback to Agent Reach/OpenCLI.
日本語の概要は準備中です。原文の説明を表示しています。
Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.
日本語の概要は準備中です。原文の説明を表示しています。