5,811 件 ・ 関連度順
概要と使いどころ
Create polished audio content and save to Spotify. Produces episodes with TTS narration, a rich timeline (chapters plus in-player images, external links, and Spotify entity cards), and a cover image. Also use for raw media saves, show/episode management, and timeline navigation.
日本語の概要は準備中です。原文の説明を表示しています。
Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).
日本語の概要は準備中です。原文の説明を表示しています。
Migrate workloads from Google Cloud Platform to AWS — including AI and agentic workloads regardless of cloud provider. Triggers on: migrate from GCP, GCP to AWS, move off Google Cloud, migrate Terraform to AWS, migrate Cloud SQL to RDS, migrate GKE to EKS, migrate Cloud Run to Fargate, Google Cloud migration, migrate from OpenAI to Bedrock, move off OpenAI, switch from ChatGPT API to AWS, migrate from Gemini to Bedrock, migrate LangChain to Bedrock, migrate LangGraph to AWS, migrate agentic workloads to AWS, move AI workloads to AWS, migrate my AI app to AWS. Runs a 6-phase process: discover GCP resources from Terraform files, app code, or billing exports, clarify migration requirements, design AWS architecture, estimate costs, generate migration artifacts, and collect optional feedback. Clarify must finish before Design, Estimate, or Generate. Includes AI provider migration guidance (for example, OpenAI to Amazon Bedrock) by selecting closest-fit Bedrock model families for required modality, latency/quality targets, context windows, and cost constraints. Model mapping is compatibility-guided, not 1:1 parity; validate prompts, tool-calling behavior, and eval metrics before cutover. Do not use for: Azure or on-premises migrations to AWS, AWS-to-GCP reverse migration, general AWS architecture advice without migration intent, GCP-to-GCP refactoring, or multi-cloud deployments that do not involve migrating off GCP.
日本語の概要は準備中です。原文の説明を表示しています。
Query Windsor.ai business data across marketing, sales, CRM, ecommerce, finance, and analytics connectors. Use when users need dashboards, reports, data visualization, schema exploration, or connector-backed test data from Windsor.ai.
日本語の概要は準備中です。原文の説明を表示しています。
Code quality guidelines and best practices for writing clean, maintainable code. Covers naming, structure, error handling, testing, and code review standards. Use when writing code, reviewing, refactoring, or asking "how should I name this", "best practice for", "clean code".
日本語の概要は準備中です。原文の説明を表示しています。
Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "/aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
日本語の概要は準備中です。原文の説明を表示しています。
Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met. Use after "$aif-implement" completes, or when user says "verify", "check work", "did we miss anything".
日本語の概要は準備中です。原文の説明を表示しています。
Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives
日本語の概要は準備中です。原文の説明を表示しています。
Write well-structured Verification Guards. Use when: (1) Creating a new guard, (2) Editing guard check commands or patterns, (3) User mentions guard, verification, or check
日本語の概要は準備中です。原文の説明を表示しています。
Act as an interactive data analyst for ClickHouse-backed analytics. Use when the user asks questions about internal data, metrics, dashboards, telemetry, active users, revenue, funnels, trends, distributions, or wants an analyst-style conversation, ad hoc SQL, charts, or a data export against ClickHouse (local or ClickHouse Cloud).
日本語の概要は準備中です。原文の説明を表示しています。
知識型 IG 輪播圖卡的獨立審核員（Joker）——預設有罪推定、禁止 LGTM。對一套輪播圖卡＋文案，按「封面/結構/擴散/CTA/品牌」五類硬規則逐條 PASS/FAIL，指到卡給可照做的改法，並算社群擴散體質分。是 Social Post Producer 迴圈裡的「審」（寫審分離）。觸發詞：驗收這套輪播、這組圖卡會不會擴散、red team 這個 carousel、carousel joker、圖卡審核、這套 IG 圖文夠不夠好。立場是找碴不是稱讚。
日本語の概要は準備中です。原文の説明を表示しています。
迷因知識輪播的獨立審核員——用「幽默感」的可二元判定要素（不協調-解消/良性冒犯/切身共鳴/誇張反差/自嘲/三的法則/秒懂）＋迷因 Hook＋版權安全，對一套迷因圖卡逐條 PASS/FAIL、指到卡給改法。預設有罪推定、禁 LGTM。是迷因輪播 loop 的「審」。觸發：這張夠不夠好笑、驗收迷因圖、meme joker、這個梗會不會冷、迷因輪播審核。
日本語の概要は準備中です。原文の説明を表示しています。
最强经理之争——把四位风格迥异的中国权益基金经理（易方达郑希、易方达张坤、易方达武阳、财通金梓才）放进同一个擂台， 用他们各自的全部公开观点原文 + 全部在管基金真实数据（季度持仓/净值/回撤/规模），做可溯源的对比与应用。能做： (1) 经理之争擂台——同口径比收益/最大回撤/回撤恢复/波动/Calmar/换手/规模，给"分场景谁更强、各自长短板"； (2) 行业/个股透视——给一个行业或股票，看四人谁持有/谁加减/谁更早布局，再用各自框架给"四个镜头"的综合看法； (3) 持仓/调仓追踪——逐季还原谁加仓、减仓、新进、清仓（季度颗粒度，公开数据能到的最细）； (4) 多视角参考——用四人的方法和真实操作，多角度帮你理解一只基金/一个行业、校准自己的判断（只呈现不同视角，不替你做决定、不构成建议）； (5) 溯源问答/方法讲解/风格化点评——引用某位经理本人原话答其观点，讲其投资框架，或用其口吻点评； (6) 言行对照——用真实持仓核对某位经理"说的"和"买的"。 (7) 进阶玩法——风格雷达+人设卡、本季调仓快报(共识/分歧)、言行一致性打分、观点时间机器(谁最早看到)、四人会诊(四种视角点评)、自定义擂台(把任意基金/经理拉进来比)。 When the user mentions 最强经理之争 / 经理对比 / 谁更强 / 回撤谁控得好 / 张坤/郑希/武阳/金梓才 / 景气轮动 vs 买入持有 / 风格雷达 / 人设 / 谁最早布局 / 言行一致 / 四人会诊 / 把某基金加进来比， asks who holds a sector or stock, wants 调仓追踪/调仓快报, a 风格化点评, words-vs-holdings, a style radar/persona, an opinion timeline, or to apply their methods to a fund/sector ——use this skill, even without the word "skill", even if the topic isn't in a corpus (fall back to that manager's method). 引用忠于原文、不杜撰；原话/推演/需核实分清；季度颗粒度非逐笔；研究学习辅助，非投资建议。
日本語の概要は準備中です。原文の説明を表示しています。
Build type-safe validated forms using React Hook Form v7 and Zod v4. Single schema works on client and server with full TypeScript inference via z.infer. Use when building forms, multi-step wizards, or fixing uncontrolled warnings, resolver errors, useFieldArray issues, performance problems with large forms.
日本語の概要は準備中です。原文の説明を表示しています。
This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
日本語の概要は準備中です。原文の説明を表示しています。
Append a DiT-tuning round to history.yaml. DiT-side counterpart of the LLM-path accuracy_append.py; records practice.md5, inference_outputs, fp_baseline_outputs, and the scoring fields (scores / overall_score / loss_vs_baseline / is_satisfied) populated by quant-tuning-score-dit. Idempotent on practice_id.
日本語の概要は準備中です。原文の説明を表示しています。
ACTIVATE THIS SKILL FOR ANY SHELL COMMAND OR FILE READ. Check curl, wget, rm, sudo, apt, dpkg, chmod, dd, format, powershell, bash, sh. Check pipe patterns like | sh or | bash. Check shell wrappers like bash -c, xargs, find -exec. Check cloud CLI (aws, gcloud, kubectl, terraform). Check when user says sysadmin told me, Stack Overflow says, is this safe, can I run. Block reading of .env, .ssh, .aws, and credential files. This skill blocks dangerous commands and warns on risky ones. ALWAYS apply the safety protocol from this document before responding about any command.
日本語の概要は準備中です。原文の説明を表示しています。
Refresh the NowStack Mobile public landing page style. Use for `/ns web landing-page`, landing redesigns, CapWords/Screen Studio inspired references, and web-app/app/components/landing edits.
日本語の概要は準備中です。原文の説明を表示しています。
Operate and review a JLCPCB PCB/PCBA quote, optional physical-stencil request, or order using a frozen Gerber/drill, BOM, CPL, sourcing lock, constraints, and release manifest. Use for browser upload, board or stencil options, cost anomalies, coupons, component matching, substitutions, imported placement calibration, top/bottom preview inspection, cart preparation, or order records without silently accepting placement errors or payment.
日本語の概要は準備中です。原文の説明を表示しています。
Use when scoring finished content against quality dimensions, evaluating whether a piece meets publishable standards, or determining which workflow phase needs rework based on quality gaps.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing content targeting search visibility, optimizing articles for keywords and featured snippets, planning SEO-aware heading architecture, or validating on-page SEO elements.
日本語の概要は準備中です。原文の説明を表示しています。
Summarize any block of text using the `summarize` CLI (chained-in from steipete/summarize — npm package `@steipete/summarize`). Use whenever the user pastes a long piece of content and asks for a TL;DR, a summary, a digest, a gist, a condensed version, or key points — even if they don't explicitly say "use summarize". Also chains into `mktg-transcribe --summarize` for audio/video TL;DRs and source-digestion workflows to condense long articles. Requires the `summarize` CLI to be installed (`mktg doctor` will tell you if it's missing). Do NOT trigger for structured data (JSON/CSV/code), for text already shorter than ~500 words, or when the user wants the full content preserved.
日本語の概要は準備中です。原文の説明を表示しています。
Discover keyword opportunities with MEASURED volume, keyword difficulty, CPC, and intent from OpenSEO, then write them into brand/keyword-plan.md. Use this skill whenever someone asks for keyword difficulty, KD, search volume, keyword ideas with metrics, striking-distance opportunities from Search Console, or SERP-validated keyword priorities. For qualitative research without an OpenSEO connection, use mktg's keyword-research instead (metrics will be unknown). Triggers: "keyword difficulty", "search volume", "keyword opportunities", "striking distance keywords", "measured keyword research".
日本語の概要は準備中です。原文の説明を表示しています。