6,747 件 ・ 関連度順
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。
Build a polished local launch page in twelve minutes from a frozen app brief and design handoff, including a playable micro-demo, responsive copy, privacy proof, and zero remote dependencies. Use for the parallel marketing lane of a live iOS build, a fallback landing page, or a fast product teaser that must run offline.
日本語の概要は準備中です。原文の説明を表示しています。
Submit iOS app to App Store for review
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning, auditing, or speccing a video's motion and visual craft: shot lists, storyboards, color scripts, transitions, easing, kinetic typography, pacing, retention, or animation principles. Triggers: 'video plan', 'shot list', 'storyboard', 'color script', 'motion spec', 'fix the pacing', 'explainer/demo/brand video'. For the spoken words themselves, use script-writer-skill; for in-code UI motion, use frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a SaaS founder needs to set, audit, or redesign pricing — choosing a value metric, structuring tiers and packaging, setting price points, designing discounts, planning a price increase, or optimizing a pricing page. Also for monetization questions like free-to-paid conversion, expansion revenue, willingness-to-pay research, or per-seat vs usage-based. Not for which acquisition channels to use (use channel-expert) or the wording of the pricing page (use copywriter-skill).
日本語の概要は準備中です。原文の説明を表示しています。
pytest testing patterns for any Python project: test structure, fixtures, parametrize, conftest.py, monkeypatch, tmp_path, markers, unittest.mock (MagicMock, patch), pytest-cov coverage, and best practices. Stack-agnostic — referenced by every Python plugin in the marketplace. Use this skill to: - Organise tests with conftest.py shared fixtures and a clear test/src layout. - Write parametrized tests to cover multiple inputs without duplication. - Mock external dependencies (HTTP, DB, filesystem) with unittest.mock and monkeypatch. - Measure and enforce code coverage with pytest-cov. Do NOT use this skill for: - Framework-specific test types (Django TestCase / WebTestCase, FastAPI TestClient, Flask test client — see framework plugin skills). - Language idioms — see python-foundation:python-conventions.
日本語の概要は準備中です。原文の説明を表示しています。
React Native project structure, Expo vs bare workflow detection, app.json/app.config.js patterns, asset handling, fonts, styling approaches, hot-reload-friendly idioms. Use this skill to: - Detect Expo (managed/dev-client/EAS/ejected) vs bare RN workflow. - Pick correct project layout for each workflow. - Configure app.json / app.config.js with bundle ID, splash, icons, deep link schemes. - Handle assets, fonts, images correctly. - Pick a styling approach (StyleSheet / NativeWind / restyle / styled-components). Do NOT use this skill for: - Platform-specific branching (see rn-platform-specific). - Navigation (see rn-navigation). - Storage (see rn-state-and-storage). - Testing (see rn-testing).
日本語の概要は準備中です。原文の説明を表示しています。
Search the general web or scholarly publications through Exa. Use for current public information, official documentation, source code, release notes, papers, preprints, journals, or literature research.
日本語の概要は準備中です。原文の説明を表示しています。
可选项驱动的互动小说创作完整规范：支持穿越/自创/创世/随机开局，内置视角一致性、字数区间、选项机制、存档系统与角色卡体系。当用户想玩、想写互动小说，或说「加载小说包」「开个互动小说」「选项小说」「互动故事」时使用。
日本語の概要は準備中です。原文の説明を表示しています。
**雨哥（雨哥聊海外销售）出品**的海外销售公司背调与市场调研助手 —— 雨哥海外销售方法论金字塔「第 5 层 · 市场经营」的 AI Skill 化产物。基于「五看六定」经典市场分析框架（华为原版 + 雨哥改造版），输出标准化的市场调研报告，适用于客户拜访前调研、代理商签约前尽调、竞品季度跟踪、新市场进入决策、年度战略规划、面试求职准备等多种海外销售工作场景。 作者：雨哥 · 13 年海外销售实战 · 曾任普渡机器人亚太区负责人（年营收破亿 · 团队 5→50 人）· 海外销售培训头部 IP（累计付费客户 130+）。 触发方式：当用户说"帮我调研 XX 公司""做一下 XX 公司的背调""XX 公司的市场调研""调研 XX 在欧洲/北美/东南亚的市场""XX 公司客户拜访准备""XX 代理商尽调"时使用。 也在用户提到公司名 + 关键词（"调研""背调""尽调""市场分析""客户拜访""代理商谈判""竞品分析""go-to-market""GTM""面试""五看六定"）时主动触发。 This skill should be used proactively when a company research request is detected.
日本語の概要は準備中です。原文の説明を表示しています。
Use when debugging RelWithDebInfo or -O2 release builds, using -Og for debuggable optimization, split-DWARF, GDB scheduler-locking, reading inlined frames, or understanding "value optimized out".
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Cortex-M NVIC ISRs, configuring priorities, handling HardFault, tail-chaining, or measuring interrupt latency. Not for the vector table itself: use baremetal-startup.
日本語の概要は準備中です。原文の説明を表示しています。
Use when collecting sampling profiles with perf record, reading perf report or perf annotate, measuring PMU counters with perf stat -e, or using PAPI instrumentation to interpret IPC, miss rates, MPKI, or memory bandwidth on Linux. Not for SVG rendering: use flamegraphs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when configuring MCU sleep/stop/standby, WFI, STM32 PWR, nRF sleep, clock gating, wake-up EXTI sources, or measuring current draw. Not for the wake ISR: use interrupts-and-exceptions-baremetal.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a non-trivial change lands or is abandoned and its decision, rejected alternatives, and reason must be captured. Not for trivial or corrective changes: those belong in CHANGELOG.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user requests the reasoning behind one matched session by query or handle. Not for peer transfer: use history-sync. Not for store registration: use history-source-registry.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a measured cost surface needs one-change-at-a-time reduction under frozen guardrails. Not for speed-only optimization: use optimize.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for release, version bump, changelog, or branch workflow beyond a single commit. Don't use for single commits or for publishing to a package registry.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a human explicitly asks to reshape or annotate one pull request for review. Don't use for pushing the rewritten branch or mutating any remote.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user needs to measure fuzz corpus coverage, explain a coverage plateau, or turn uncovered regions into campaign work. Not for harness creation: use fuzz-harness-writing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a landed merge, release, or completed change needs its cleanup surface reconciled. Scans for stale TODOs, deprecations, unused flags, and doc gaps. Not for unrelated refactoring.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a user needs to create or improve a deterministic, engine-agnostic fuzz harness for raw or structured target inputs. Not for coverage measurement: use fuzzing-coverage-analysis.
日本語の概要は準備中です。原文の説明を表示しています。