1,732 件 ・ 関連度順
概要と使いどころ
Amazon Bedrock Automated Reasoning for mathematical verification of AI responses against formal policy rules with up to 99% accuracy. Use when validating healthcare protocols, financial compliance, legal regulations, insurance policies, or any domain requiring deterministic verification of AI-generated content.
日本語の概要は準備中です。原文の説明を表示しています。
Apollo.io benefits packages by country — health insurance, equity, perks, and stipends
日本語の概要は準備中です。原文の説明を表示しています。
Customer segmentation model builder — tiers customers by ARR, health, and expansion potential; defines CS motion per tier; maps resource allocation. Use when asked to "segment our customers", "define our CS tiers", "how should we allocate CS resources", "build a customer segmentation model", or "who gets high-touch vs. digital".
日本語の概要は準備中です。原文の説明を表示しています。
Customer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.
日本語の概要は準備中です。原文の説明を表示しています。
Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".
日本語の概要は準備中です。原文の説明を表示しています。
Operations reconnaissance — audit process documentation, vendor contracts, compliance posture, OKR health, and cross-functional friction points to understand where operations is the bottleneck. Use when asked to "audit our operations", "where are we slow", "what processes are broken", or "before designing a compliance program".
日本語の概要は準備中です。原文の説明を表示しています。
Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".
日本語の概要は準備中です。原文の説明を表示しています。
Content marketing reconnaissance — audit current content, SEO health, competitor content gaps, and content distribution. Use when asked to "audit our content", "what's our SEO state", "where are the content gaps", or before designing a content strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Database reconnaissance — full inventory of schema, migrations, data volume, backups, connection pooling, and query patterns. Use when asked to "assess this database", "understand the schema", or "database health check".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to select a UI style, choose a design direction, pick a visual approach for a product, or match a style to an industry. Examples: "what style fits a fintech app", "choose between neumorphism and glassmorphism", "design direction for healthcare SaaS"
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to generate a color palette, create industry-matched colors, or pick colors for a product type. Examples: "color palette for fintech", "healthcare app colors", "SaaS brand colors"
日本語の概要は準備中です。原文の説明を表示しています。
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
日本語の概要は準備中です。原文の説明を表示しています。
Support operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a support system".
日本語の概要は準備中です。原文の説明を表示しています。
Build and manage open source community — Discord/Slack structure, contributor onboarding, ambassador program, community flywheel design, and GitHub community health. Use when asked to "build a community", "grow our Discord", "improve contributor experience", or "design a developer ambassador program".
日本語の概要は準備中です。原文の説明を表示しています。
PMU observation pattern for agent health monitoring. Runs patrol loops, detects stalled agents, sends nudges, and escalates persistent failures to the mayor. Never modifies agent work or resolves conflicts.
日本語の概要は準備中です。原文の説明を表示しています。
Provides dependency management and supply chain security practices for auditing vulnerabilities, checking licenses, assessing dependency health, and managing upgrades safely. Use when auditing packages, reviewing security, managing dependencies, or when user mentions 'audit', 'vulnerability', 'dependency', 'supply chain', 'npm audit', 'license', 'bundle size'.
日本語の概要は準備中です。原文の説明を表示しています。
Reading a habitat — identifying biome, plant community, food web structure, successional stage, and the keystone species that hold the system together. Covers the elevational and latitudinal gradients that Humboldt first mapped, the structural vocabulary for describing a habitat, the core concepts of food-web and trophic analysis, and the practice of diagnosing habitat health from indicator species. Use when the task is to understand a place rather than a species.
日本語の概要は準備中です。原文の説明を表示しています。
Being a constructive participant in networked communities. Covers digital footprint management, online etiquette and professional communication, collaborative tools, attribution and copyright, cyberbullying recognition and response, and the responsibilities that come with amplification. Use when helping learners think about how to behave online -- not what is technically allowed, but what is actually healthy for themselves and their communities.
日本語の概要は準備中です。原文の説明を表示しています。
Kolla-Ansible day-2 operations skill for post-deployment infrastructure lifecycle management. Covers service reconfiguration (globals.yml changes, config overrides, prechecks, targeted reconfigure with --tags), minor and major OpenStack upgrades (image pull, upgrade procedure, rollback), container management (restart, logs, health inspection), maintenance mode (compute disable, instance drain, host maintenance), password rotation, certificate renewal, and rolling updates. This skill is for operations after initial deployment -- the kolla-ansible deployment skill covers initial bootstrap and deploy.
日本語の概要は準備中です。原文の説明を表示しています。
账号被限流/异常/担心操作触发风控/需要恢复时用：先自检from:@用户名搜不到即限流→区分临时标签(等24h不动账号)与正式标签(写申诉邮件+48h不操作)→复盘触发原因预防复发。Trigger："推文搜不到了""被限流了""账号异常""触发风控""临时标签""怎么申诉""shadowbanned""account suspended""appeal suspension""tweets not showing up"。不适用：正常发内容没出问题(→内容创作skill)、新号开业装修养号(→x-account-setup)、没粉丝怎么起量(→x-cold-start-playbook)。
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain a persistent, LLM-maintained markdown wiki following Andrej Karpathy's LLM Wiki pattern — the agent incrementally compiles raw sources into an interlinked knowledge base instead of re-deriving answers from scratch. Use this whenever the user wants to ingest a source (an article, paper, transcript, chapter, meeting notes), file knowledge or conversation findings into the wiki, query the accumulated knowledge base, lint or health-check the wiki, or mentions "the wiki", "knowledge base", "ingest this", "file this", "what do we know about X", or accumulating notes on a topic over time — even if they don't say "LLM Wiki" explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
Real-time monitoring and automated remediation for proof system health.
日本語の概要は準備中です。原文の説明を表示しています。
Badge design and selection knowledge base for shields.io badges in README files. Use when writing or updating READMEs, choosing badge layouts, selecting badge styles, adding project health indicators, or picking Simple Icons logo slugs. Covers shields.io URL encoding rules, static vs dynamic badge selection, style variants (flat/flat-square/for-the-badge/social/plastic), layout patterns (two-tier/inline/centered), project-type badge sets for Python/JS/Rust/Claude plugins, color reference, non-obvious logo slugs, and common anti-patterns to avoid.
日本語の概要は準備中です。原文の説明を表示しています。
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
日本語の概要は準備中です。原文の説明を表示しています。