「eal」の検索結果

Build, configure, and ship production voice agents on the ElevenLabs Agents platform (branded "ElevenAgents," formerly "Conversational AI"). Use when an agent must design a spoken-conversation system prompt, pick an LLM and TTS voice/model for a real-time voice bot, wire client/server/system tools and knowledge-base RAG, connect a channel (WebRTC/WebSocket SDK, embeddable widget, or telephony via Twilio/SIP), tune turn-taking and latency, set up simulation testing and evaluation, or reason about pricing, concurrency, and the consent/disclosure obligations of a synthetic voice talking to real people. Not for plain non-conversational text-to-speech, dubbing, or music generation.

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

Use when an agent must make TwelveLabs do real video-understanding work: indexing footage, semantic/visual search across an archive, generating descriptions, summaries, chapters, highlights, and tags from video, producing multimodal embeddings, or wiring TwelveLabs into a media-production pipeline (NLE panels, logging, compliance review, metadata). Covers the current model families (Marengo for search/embeddings, Pegasus for video-to-text analysis), the v1.3 Video Understanding API (indexes, assets, tasks, search, analyze, embed), prompt construction for analysis, capability and format limits, pricing/quota math, output quality review (hallucination and timestamp accuracy), and privacy/rights obligations when footage shows real people. Not for generating or editing video pixels — this is analysis and retrieval.

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

Produce text-to-speech with Alibaba/Qwen Qwen3-TTS through DashScope/Model Studio or open-weight Qwen3-TTS checkpoints. Use when an agent must choose Qwen3-TTS models, voices, realtime versus non-realtime synthesis, voice cloning, voice design, instruction/prosody controls, multilingual or dialect speech, audio artifact handling, regional routing, pricing/privacy/licensing constraints, or production QA for narration, characters, assistants, audiobooks, ads, localization, or voice-enabled media.

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

Produce short-form video with Pika (pika.art) — its effect-driven tools (Pikaffects, Pikadditions, Pikaswaps, Pikaframes, Pikascenes, Pikatwists) and audio-driven lip sync (Pikaformance), plus text-to-video and image-to-video. Use when a task calls for playful, stylized, meme-able social clips, or for applying generative effects and object swaps to real uploaded footage, and when deciding whether Pika is the right engine versus a higher-fidelity model. Covers model versions, credit/plan economics, the fal.ai API route, prompt construction, iteration/repair, capability limits, and consent/rights rules for uploaded real-person media. Not a general "best video model" chooser.

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

Produce and understand audio with OpenAI request-based audio APIs and audio-capable chat models, including text-to-speech, transcription, translation, multimodal audio input/output, model routing, prompt and performance direction, artifact custody, approval gates, and safety/rights review. Use for non-realtime OpenAI audio production; route continuous live voice agents to the separate realtime voice skill.

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

Audit a website's content, structure, SEO health, and technical setup through SandBase. Use when asked for website audit, content audit, SEO health check, site structure analysis, or technical assessment.

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

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, use an available competitor-analysis capability. For marketing website copy, cold outreach, or offer design, use the corresponding capability when available.

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

Goal-oriented binder design campaign planning and health assessment. Use this skill when: (1) Planning a complete binder design campaign, (2) Converting high-level goals into runnable pipelines, (3) Assessing campaign health and pass rates, (4) Diagnosing why designs are failing QC, (5) Estimating time, cost, and expected yields, (6) Selecting between design tools for a specific target. This skill orchestrates the other protein design tools. For individual tool parameters, use the specific tool skills.

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

Use this skill when authoring reusable, idempotent MATLAB scripts that build System Composer architecture models via the architecture-modeling API — `systemcomposer.createModel`, `addComponent`, `addPort`, `setInterface`, `connect(srcPort, dstPort)`, interface dictionaries (.sldd) with `addInterface`/`addElement`, profiles/stereotypes with `Profile.createProfile` and `addStereotype`, or `systemcomposer.allocation.createAllocationSet`. Also trigger when debugging these APIs (connections that don't appear, interfaces that don't resolve, profile save errors, `createAllocationSet` signature-mismatch errors). Do NOT trigger for ad-hoc structural edits to an already-built model (adding one SubSystem, rewiring a port) — use `building-simulink-models` with `model_edit` for that.

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

Use this skill for any work involving a MATLAB Project (.prj file) — creating a new project, tracking files, managing the project path, configuring Simulink cache and code-generation folders, running project health checks, or writing build scripts that keep the project in sync with the file system. Trigger phrases include "set up a MATLAB project", "create a .prj", "track this file in the project", "project health check", "build script conventions". This skill is the generic foundation; domain-specific skills (e.g. `mbse-workflow`) build on it.

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

Trim large MetaX model directories for dummy smoke tests or real-checkpoint loading on limited GPUs. Preserve target execution paths while reducing depth; use the real-weight workflow when a loadable checkpoint is requested. Not for accuracy evaluation or model compatibility upgrades.

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

Neighborhood Analysis — schools, crime, walkability, demographics, amenities, growth trajectory, and natural disaster risk with Neighborhood Score (0-100)

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

Mortgage Calculator & Affordability Analysis — monthly payments, amortization, loan comparison, affordability limits, rent vs buy, and refinance break-even with rate comparison tables

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

Launches 5 parallel AI agents to produce a comprehensive property analysis with composite Property Score (0-100), investment grade, and actionable recommendations

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

Local Market Analysis — median prices, inventory, days on market, price trends, rental conditions, economic drivers, and market classification with Market Score (0-100)

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

Estimates rental income from comparable rentals, builds a full expense model, calculates cash flow and key investment metrics across conservative, moderate, and optimistic scenarios

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

Finds and analyzes 5-10 comparable recent sales to estimate fair market value, calculate price adjustments, and score the property's value proposition

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

Generates MLS-ready property listing descriptions with attention-grabbing headlines, feature highlights, neighborhood context, and SEO keywords across multiple buyer-persona styles

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

Commercial Property Analysis — NOI, cap rate, expense ratio, tenant mix, vacancy, debt coverage, replacement cost, and lease analysis with Commercial Score (0-100)

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

Fix-and-Flip Analysis — purchase price, ARV, rehab budget breakdown, holding costs, selling costs, profit margin, ROI, timeline, and risk assessment with Flip Score (0-100)

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

Evaluates a property across three investment strategies — Buy & Hold, BRRRR, and Fix & Flip — with feasibility scores, multi-year projections, tax benefits, and break-even analysis

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

Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites. Includes metric formulas, realistic targets by company stage, and the action to take when each metric goes red. Use when: "QA metrics," "test metrics," "quality KPIs," "test health," "flakiness rate," "defect escape rate." Not for: building the dashboard UI (Allure/Grafana) — use qa-dashboard; measuring coverage gaps and mutation score — use coverage-analysis. Related: qa-dashboard, coverage-analysis, ci-cd-integration, release-readiness, quality-postmortem.

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

Analyze escaped defects and test suite health through blameless postmortems. Covers bug pattern analysis, test suite health reviews, 5 Whys root cause analysis, process improvement cycles, and postmortem/retro meeting templates with action item tracking. Use when: "QA retro," "escaped bugs," "postmortem," "quality incident," "defect analysis," "improvement cycle." Not for: live release go/no-go decisions — use release-readiness. Not for ongoing metric dashboards — use qa-metrics. Not for reviewing existing test code quality — use ai-qa-review. Related: qa-metrics, test-reliability, test-strategy.

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

Decision framework for isolating every external dependency in a test suite: when to use in-process mocks, HTTP stubs (MSW, WireMock), record-replay, fault injection (Toxiproxy), or ephemeral real services (Testcontainers), and how to enforce that no real calls escape in CI. Use when: "mock service," "stub API," "fake service," "WireMock," "MSW," "Toxiproxy," "test isolation," "dependency management," "stub an external API in CI." Not for: consumer-driven contract verification (Pact, broker) — use contract-testing; standing up a full Docker Compose env or seed data — use test-environments; broad resilience/game-day fault campaigns — use chaos-engineering. Related: contract-testing, test-environments, api-testing, test-data-management, chaos-engineering.

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