5,250 件 ・ 関連度順
概要と使いどころ
Debug and troubleshoot ElevenLabs conversational AI agents and Twilio calls. Use when diagnosing agent issues, analyzing failed calls, troubleshooting audio problems, investigating conversation breakdowns, reviewing error logs, or optimizing underperforming agents. Includes transcript analysis, error diagnosis, and performance troubleshooting.
日本語の概要は準備中です。原文の説明を表示しています。
白板火柴人拆书短视频工作流。用于把一本书或一段长内容做成 60-90 秒竖屏(9:16)白板手绘信息图风格的拆书口播短视频，并用 HyperFrames 在本地渲染无平台水印的最终成片。覆盖：拆书脚本与分镜表生成、白板火柴人信息图分镜图生成、口播配音生成(可选男声/女声)、背景音乐生成(可选活泼/沉稳/其他风格)、每个阶段与用户确认、HyperFrames 动效渲染+字幕卡点+音乐混音装配、成片交付。当用户提到"拆书视频""拆解一本书""白板风/火柴人信息图短视频""口播短视频""书评视频""把这本书做成视频"等需求时使用。
日本語の概要は準備中です。原文の説明を表示しています。
System bottleneck identification, resource optimization, and performance analysis
日本語の概要は準備中です。原文の説明を表示しています。
Pull performance data for published content across every surface — LinkedIn, Dev.to, Google Search Console, GA4, and AI citation tracking (Perplexity, Anthropic, OpenAI). Grades each piece as winner, average, or underperformer and surfaces whether an AI search engine has cited it.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo 20 development knowledge base covering actions, controllers, data files, API decorators, SQL constraints, indexes, modules, fields, manifests, mixins, ORM methods, migrations, OWL components, performance, QWeb reports, security, testing, transactions, translations, and XML views. Use when writing, reviewing, or debugging Odoo 20 Python, XML, or JavaScript code, creating or modifying modules, fixing performance issues, or looking up Odoo 20 API patterns and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Odoo 19 development knowledge base covering actions, controllers, data files, API decorators, SQL constraints, indexes, modules, fields, manifests, mixins, ORM methods, migrations, OWL components, performance, QWeb reports, security, testing, transactions, translations, and XML views. Use when writing, reviewing, or debugging Odoo 19 Python, XML, or JavaScript code, creating or modifying modules, fixing performance issues, or looking up Odoo 19 API patterns and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
日本語の概要は準備中です。原文の説明を表示しています。
Biome is a high-performance Rust-based toolchain for JavaScript, TypeScript, JSX, JSON, CSS, and GraphQL that unifies formatting and linting in a single tool. With 97% Prettier compatibility and over 450 lint rules, Biome replaces ESLint and Prettier with dramatically faster execution.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze LinkedIn performance and manage engagement through Publora. Use when the user asks how a LinkedIn post or account performed (impressions, reach, reactions, comments, reshares, follower growth) or wants to react, comment, reshare or resolve an @mention. Statistics run over the REST API, engagement over MCP tools. Not for creating posts (use linkedin-post).
日本語の概要は準備中です。原文の説明を表示しています。
Expert performance marketing guidance for paid acquisition, CRO, and growth optimization. Use when creating ad campaigns, writing ad copy, optimizing landing pages, setting up A/B tests, analyzing CAC/LTV, building attribution models, or planning retargeting strategies. Use for Google Ads, Meta Ads, LinkedIn Ads, conversion tracking, budget allocation, and funnel optimization.
日本語の概要は準備中です。原文の説明を表示しています。
Expert sales enablement strategist for building high-performing sales teams. Use when designing sales training programs, onboarding and ramp plans, sales playbooks, coaching frameworks, certification programs, or competitive intelligence distribution. Covers content strategy, tool adoption, performance measurement, and continuous learning systems. Use for building sales academies, creating enablement content, and optimizing sales productivity.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a rigorous Carmack Council code review. Use when explicitly asked to review code, do a "council review", "carmack review", or invoke /council-review. Carmack's philosophy chairs a council of domain experts — Troy Hunt (security), Martin Fowler (refactoring), Kent C. Dodds (frontend), Matteo Collina (Node.js), Brandur Leach (Postgres), Vercel Performance, Simon Willison (LLM pipelines), Karri Saarinen (UI quality), Vitaly Friedman (UX quality), Kent Beck (test quality). Uses parallel subagents for deep, independent review. Produces prioritised P1/P2/P3 findings. Stack: Next.js App Router / React / TypeScript / tRPC / Prisma / Neon / Clerk.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when keeping imp's docs and config examples coherent after a change - updating docs/internals/ARCHITECTURE.md / README / docs/GOAL.md / docs/MODELS.md / docs/roadmap.md / imp.conf.example / CHANGELOG / MISSION_JOURNAL, or "is this doc stale", "document this change", "the example config is out of date", "the README says X but the code does Y", "add a roadmap ledger row". Do NOT use for layer/frontmatter/lint questions (docs-layers), structural code audits (codebase-audit), measuring perf or refreshing the perf baseline (benchmark-cuda), or the agent's private memory (MEMORY.md).
日本語の概要は準備中です。原文の説明を表示しています。
Structures co-investment reporting with deal-level performance, fee/carry calculations, and co-invest program aggregate analysis. Use when reporting co-invest performance, tracking deal-level returns, or preparing co-invest summaries.
日本語の概要は準備中です。原文の説明を表示しています。
Monitors structured product performance with collateral deterioration triggers, coverage test tracking, and credit migration analysis. Use when conducting ABS surveillance, monitoring CLO performance, or tracking structured product credit.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates fund performance against peer universes with vintage year comparison, quartile ranking, and strategy-specific benchmarking. Use when benchmarking fund performance, analyzing vintage comparisons, or assessing relative positioning.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates master and special servicer performance with delinquency management, modification outcomes, and loss mitigation effectiveness. Use when assessing servicer quality, monitoring servicing metrics, or evaluating servicer transfers.
日本語の概要は準備中です。原文の説明を表示しています。
Sentry error tracking and performance monitoring for real-time visibility into application errors, performance issues, and release health
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose and fix UI performance across loading speed, rendering, animations, images, and bundle size. Use when the user mentions slow, laggy, janky, performance, bundle size, load time, or wants a faster, smoother experience.
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants measurable accessibility, performance, responsive, theming, or anti-pattern findings—not when they mainly want an overall UX critique or final visual/detail polish.
日本語の概要は準備中です。原文の説明を表示しています。
Run technical quality checks across accessibility, performance, responsive design, theming, and anti-patterns. Generate a scored report with P0-P3 severity ratings. Report-only — documents issues for other skills to fix. Triggers on audit the design, check accessibility, technical review, performance audit, a11y check.
日本語の概要は準備中です。原文の説明を表示しています。
Apply React and Next.js performance optimization guidelines from Vercel Engineering — 40+ rules covering components, data fetching, bundle optimization, and rendering. Triggers on React components, Next.js pages, bundle optimization, performance improvements, refactoring React code.
日本語の概要は準備中です。原文の説明を表示しています。
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
日本語の概要は準備中です。原文の説明を表示しています。