「ai」の検索結果

fal.aiのAIモデルを使って画像や動画を生成するためのスキル。Flux、SDXL、ideogramなどを対象に、エージェントから生成を依頼する入口になります。

• fal.aiで画像を生成したいとき
• fal.aiで動画を生成したいとき
• 画像生成モデルを指定したいとき

Emaillistverifyの操作を自動化するため、使えるツールと入力項目を検索し、接続確認から実行、一括処理までをRube MCP経由で進めるスキル。

• Emaillistverifyのツール検索
• Emaillistverifyの接続確認
• Emaillistverifyの操作自動化

Dailybotの操作をAIエージェントに任せるスキル。Rube MCP経由で利用可能なツールと入力条件を調べ、接続状態を確認して作業を実行します。

• Dailybotの対応操作を調べたいとき
• 実行前に接続状態を確認したいとき
• 最新の入力条件で操作を実行したいとき

Detects AI-generated writing four ways — a heuristic audit against a catalog of known AI patterns, deterministic statistical signals (n-gram entropy, burstiness, repetition, stylometry — features never verdicts), an empirical Pangram score calibrated against known-human baselines, and a keyless scan for watermark and steganography signatures (invisible characters, homoglyphs, bidi, odd whitespace) in the bytes. USE WHEN detect AI writing, is this AI, AI detection, AI detector, did an AI write this, does this sound like AI, AI writing score, pangram, scan for AI tells, flag AI patterns, AI-isms, statistical AI signals, burstiness, text entropy, is this watermarked, detect watermark, steganography, zero-width chars, hidden characters, invisible unicode, compare drafts for AI-ness. NOT FOR rewriting prose to strip AI patterns (use a voice/authoring skill), plagiarism detection, detecting AI-generated images/video/code, or judging whether writing is any good.

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

Rigorous, defensible email-spoofability verdict and SPF supply-chain risk analysis computed from published DNS alone. Deepens the record-level SPF/DMARC/DKIM/BIMI/MTA-STS/DNSSEC fetch recipes in the offensive-osint arsenal (§16.14) with the reasoning that section doesn't do: a priority-ordered composite verdict for whether an attacker can actually land header-From-spoofed mail in an inbox, and by which vector (exact-domain vs subdomain) — grounded in the single most-misunderstood distinction in email security: the envelope MAIL FROM that SPF authenticates vs the visible header From: that only DMARC governs. Explains precisely why SPF -all/~all alone is NOT spoof-proof without DMARC enforcement, and why SPF +all bypasses DMARC even under p=reject pct=100. Covers RFC 7208 §4.6.4's 10-DNS-lookup / 2-void-lookup PermError fail-open condition with a runnable stdlib-only lookup-counter script, plus the SPF-include-takeover supply-chain vector (an attacker re-registering a dead include inherits SPF-pass authority over the victim domain) with strict transient-vs-NXDOMAIN discrimination discipline so a temporary SERVFAIL is never mistaken for a takeover lead. Fully passive: DNS TXT reads only, no mail sent, no RCPT TO probe, no API keys. Use when auditing a domain's real spoofing resistance (not just its published records), explaining to a client why 'we have SPF -all' does not mean they're covered, investigating an SPF PermError or an unusually long include chain, evaluating a dead SPF include as a takeover lead, or writing a defensible spoofability finding for a deliverable.

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

End-to-end testing of email-dependent flows — signup confirmation, password reset, magic-link login, OTP/MFA codes, and notification emails. Covers the capture-inbox decision tree (Mailpit, Mailosaur, MailSlurp, Ethereal), Playwright polling without fixed sleeps, regex extraction of links/OTPs from the email body, deterministic per-test addresses (plus-addressing, per-inbox), subject/from/header/link assertions, and SPF/DKIM/DMARC deliverability checks as a separate suite. Use when: "test the signup confirmation email," "password reset email test," "magic-link login test," "capture OTP from email," "Mailpit," "Mailosaur," "MailSlurp," "email arrives flaky in CI," "assert email subject/from/links." Not for: Sending transactional email from your app code, or API-only contract tests of an email provider — those are api-testing / app concerns. Email HTML rendering across clients (Outlook/Gmail dark mode) is out of scope (note it as a gap; use visual-testing or Litmus). Related: playwright-automation, api-testing, test-data-management, qa-project-context.

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

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

Retrieves patent claims data from Nexscope (Nexscope). Trigger when the user mentions patent claims, claim text, independent claims, dependent claims, claim count, claims tree, claims analysis, claim scope, claim language, viewing the claims section of a specific patent, patent claims, independent claims, dependent claims, claims text, Nexscope. Also trigger when the user requests patent claims information by patent ID or publication number, even without explicitly mentioning Nexscope or Nexscope.

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

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

Win #1 Product of the Day on Product Hunt. Completely reverse-engineered from 30x daily winner and 3x weekly winner campaigns — ranking algorithm decoded, launch timing optimized, hunter selection guide, community engagement approach, and post-launch momentum playbook. Use this if you're: (1) already read PH launch guides but still can't break into Top 5 and need algorithm-level deep optimization, (2) targeting Daily #1 and 5,000+ sign-ups with a proven 30+ case validated approach, or (3) an investor/accelerator coaching portfolio companies on PH launches. What's inside: PH ranking algorithm decoded: weighted factors for first 3 hours, 24 hours, and weekly ranking · Pre-launch preparation: gallery optimization, product URL selection, tagline refinement (≤60 chars) · Launch timing optimization: exact PST launch windows + scheduling guide · Community engagement KPIs: upvote targets, comment response time, maker comment strategy · Platform compliance guide: understanding PH's quality signals and organic growth · Post-launch 72-hour plan: maintaining momentum, conditions for Weekly #1 · Case studies: 3 different categories (AI Tool, App, SaaS) dissected Expected outcomes: Product Hunt Daily #1 ranking · strong community engagement on launch day · 3,000–10,000+ sign-ups (depending on product-market fit) 🇨🇳 Product Hunt 打榜完整攻略 | 🇯🇵 Product Hunt ローンチガイド | 🇰🇷 Product Hunt 런칭 가이드 Keywords: Product Hunt #1, Product Hunt launch strategy, PH ranking algorithm, PH #1 daily winner, Product Hunt tips, product launch, startup launch, ranking optimization, PH gallery optimization, Community engagement strategy, maker community engagement, product strategy, launch tactics, how to win Product Hunt, product hunt best practices

Use whenever the user wants to find, rank, or shortlist directories and listing sites where they can submit an AI product — an AI tool, AI app, AI agent, or agent skill / plugin — to get backlinks, referral traffic, and discovery. Triggers on "where can I list my AI tool", "directories to submit my AI agent", "agent-skills directories", "best AI tool directories for backlinks", "where do I get my GPT/Claude app discovered", or "pull submission details for these AI-directory domains", even when described indirectly (we built an AI agent, where do we get it in front of people). Drives the ServiceGraph API (api.servicegraph.co) — a catalog of 1,000+ product directories enriched with Domain Rating, backlinks, and organic traffic. Defer to find-mcp-directories for MCP-server listings specifically, and to find-product-directories for general SaaS/software/app launches with no AI angle. Skip finding an AI consultancy/agency to hire (use find-ai-consultancy), comparing AI products ("ChatGPT vs Claude"), building an AI tool (do-the-work), and AI link-building *services*.

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

Use when configuring the outbound Send Email quick action in Lightning Case Feed — creating the action in Setup on Case (Action Type = Send Email), attaching a default Custom email template, setting predefined To/CC/BCC values, wiring QuickAction.QuickActionDefaultsHandler Apex defaults, respecting the Lightning Experience 10-file / 25 MB attachment limits, and letting agents move an email to a different case. Trigger keywords: Send Email quick action, case email composer, Email action missing from Case Feed, Don't Apply Template Subject, QuickActionDefaultsHandler, SendEmailQuickActionDefaults, move email to another case. NOT for Email-to-Case inbound routing, routing addresses, or thread-ID matching (use admin/email-to-case-configuration), NOT for authoring or migrating the templates themselves (use admin/email-templates-and-alerts and admin/classic-email-template-migration), and NOT for Apex Messaging.SingleEmailMessage sends outside Case Feed.

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

欧盟 AI 法案知识引擎——以 70 份官方欧盟来源文件为基础的权威监管问答（包括 2026 年委员会关于 Art. 6 高风险分类的指南草稿——一般原则、附件 I、附件 III）。基于完整条例文本、委员会指南、EDPB/EDPS 意见、《实践守则》、协调标准、FRIA 指南、事件模板和行业特定指引，以条款级引用回答关于 AI 法案的任何问题。当用户询问"EU AI Act"、"AI Act regulation"、"Regulation 2024/1689"、"KI-Verordnung"、要求"explain an AI Act article"、"what does Article X say"、"AI Act requirements"、"AI Act penalties"、"AI Act timeline"、"GPAI obligations"、"high-risk AI"、"prohibited AI practices"、"AI Act and GDPR"、"fundamental rights impact assessment"、"AI Act standards"、"AI Act national implementation"、"AI literacy"、"serious incident reporting"、"Digital Omnibus"、"AI regulatory sandbox"，或任何关于欧盟人工智能监管的问题时，应使用本技能。德语术语同样触发："KI-Gesetz"、"KI-Verordnung"、"Hochrisiko-KI"、"KI-Kompetenz"、"Grundrechte-Folgenabschaetzung"、"GPAI-Verhaltenskodex"。对于产出分类决定而非知识答案的评估工作流，提议在会话内运行结构化风险等级分类。

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

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

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

AIエージェント専用のメール受信箱を用意し、送受信や返信、添付ファイルの処理を行います。メールで届く認証コードの確認や、受信をきっかけにした継続的な処理にも使えます。

• AIエージェント専用アドレスの作成
• メール送信と返信・添付ファイルの処理
• メールで届く認証コードの確認

ReactとTailwindを使い、claude.ai向けの複雑なHTMLアーティファクトを作成するスキルです。埋め込み可能なWebコンテンツの制作に使えます。

• claude.ai向けHTML成果物の制作
• ReactとTailwindでの制作
• 埋め込み用Webコンテンツの作成

新しいサービスや製品に合うドメイン名の案を出し、.com・.io・.dev・.aiなど複数の末尾で取得できるかを確認するスキル。

• 新サービスのドメイン名を考えたいとき
• 複数の末尾で空き状況を確認したいとき
• 製品名に合うドメインを比較したいとき

対話を通じて仕事や好み、AIに任せたい範囲を整理し、AIパートナーの行動方針を定めるSOUL.mdを作成・更新します。話し方や反対意見の伝え方まで具体化します。

• AIの性格や役割を初めて決めたいとき
• 口調や反対意見の伝え方の調整
• AIに任せる判断範囲の整理

Emailableの操作をRube MCP経由で自動化するスキルです。利用可能なツールと入力形式を検索し、接続状態を確認してから処理を進めます。

• Emailableの操作ツールを探したいとき
• 実行前のEmailable接続確認
• Emailableの一括処理

Convolo AIの操作をAIエージェントから自動化するスキル。Rube MCPを通じて利用可能なツールと入力形式を調べ、接続状態を確認して処理を実行します。

• Convolo AIの操作を調べたいとき
• 処理前に接続状態を確認したいとき
• Convolo AIの反復操作の自動化

Apipie AIの操作をRube MCP経由で自動化するスキルです。利用可能なツールと最新の入力形式を調べ、接続状態を確認してから処理を実行します。

• Apipie AI用のツールを探したいとき
• 実行前のApipie AI接続確認
• 対応する操作を一括実行したいとき

React Email renderer for json-render that turns JSON specs into HTML or plain-text emails using @react-email/components and @react-email/render. Use when working with @json-render/react-email, building transactional or marketing emails from JSON, creating email catalogs, rendering AI-generated email specs, or when the user mentions react-email, HTML email, or transactional email.

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

Write an email drip sequence for affiliate marketing. Triggers on: "write me an email sequence", "create a drip campaign", "email nurture sequence", "affiliate email funnel", "welcome email series", "email onboarding sequence", "write emails for my list", "set up a drip sequence", "email campaign for [product]", "nurture my subscribers", "email follow-up sequence", "build my email funnel", "write 5 emails promoting [product]", "email automation sequence".

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

コミュニケーション診断ツール（commu-checker）の各タイプ向け、90日トレーニングコンテンツを生成するスキル。 ユーザーが「D1型のトレーニングを作って」「〇〇型の90日プランを作りたい」「training-data.jsに追加したい」 「コミュ診断のトレーニングページ」などと言ったときに必ず使う。 タイプ定義・観察メモを受け取り、既存サイト（M PLUS Rounded 1c・グリーン基調・Material Icons）に合わせた インタラクティブなチェックリスト用HTMLコンテンツを training-data.js の TRAINING_PAGES オブジェクトに追加する形で出力する。 トレーニングは trainings/index.html + trainings/training-app.js + trainings/training-data.js の3ファイル構成。 個別の <type>.html は存在せず、URL の ?type=d1 などのパラメータで表示タイプを切り替える。