2,216 件 ・ 関連度順
概要と使いどころ
SEO audit and keyword strategy — investigate a site's real search opportunities, shortlist candidates, and recommend the one to three changes most likely to grow organic traffic that converts. Evidence-first — metrics come from a tool or are written as unknown. Use when asked to "improve our SEO", "do keyword research", "audit our SEO", "why aren't we ranking", or "what should we fix first for search".
日本語の概要は準備中です。原文の説明を表示しています。
Content Marketing engineer — blog strategy, SEO, thought leadership, developer content, case studies, and content calendar. Use when asked to "write a blog post", "plan our SEO", "build a content calendar", or "write a case study".
日本語の概要は準備中です。原文の説明を表示しています。
Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
日本語の概要は準備中です。原文の説明を表示しています。
Build a hiring pipeline - job description, sourcing strategy, interview scorecard, and offer process. Use when asked to "write a job description", "build an interview process", "design our hiring funnel", or "what should we look for in a [role]".
日本語の概要は準備中です。原文の説明を表示しています。
Design a hyperparameter tuning strategy for a model — search space, method, and budget. Use when asked to "tune hyperparameters", "define a search space", or "set a tuning budget".
日本語の概要は準備中です。原文の説明を表示しています。
Design pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".
日本語の概要は準備中です。原文の説明を表示しています。
Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing. Use when asked to "price this deal", "build a sales playbook", "close an enterprise deal", or "manage the B2B pipeline".
日本語の概要は準備中です。原文の説明を表示しています。
Design embedding pipelines — model selection, batching, normalization, index refresh strategy. Use when asked to "design an embedding pipeline", "which embedding model should we use", or "how should we batch embeddings".
日本語の概要は準備中です。原文の説明を表示しています。
Design an edge routing and geo-distribution strategy — latency routing, failover, and edge logic. Use when asked to "geo-route our traffic", "reduce global latency", or "design edge failover".
日本語の概要は準備中です。原文の説明を表示しています。
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
日本語の概要は準備中です。原文の説明を表示しています。
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
日本語の概要は準備中です。原文の説明を表示しています。
Design a cache invalidation and eviction strategy — event-driven invalidation and thundering herd prevention. Use when asked to "design cache invalidation", "fix stale cache data", or "prevent a thundering herd".
日本語の概要は準備中です。原文の説明を表示しています。
Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".
日本語の概要は準備中です。原文の説明を表示しています。
Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a contributor program", "start a developer advocacy program", or "how do we grow our dev community".
日本語の概要は準備中です。原文の説明を表示しています。
Smart agentic web data extraction with multi-strategy scraping (Crawl4AI v4, Firecrawl), LLM extraction loops, anti-bot bypass, and structured export / Ekstraksi data web cerdas dan agentic dengan scraping multi-strategi (Crawl4AI v4, Firecrawl), ekstraksi LLM, bypass anti-bot, dan ekspor terstruktur.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-cognitive and practical strategies for learning any language -- learner autonomy, goal setting, strategy taxonomy (Oxford's SILL framework), memory strategies, cognitive strategies (note-taking, summarizing, analyzing, reasoning), compensation strategies, metacognitive strategies (planning, monitoring, evaluating), affective strategies (managing anxiety, self-encouragement), social strategies (collaboration, questioning, empathy), immersion design, study habit optimization, plateau diagnosis, and motivation maintenance. Use when designing a language learning plan, diagnosing a learner's stuck points, selecting study methods, or building self-directed learning skills.
日本語の概要は準備中です。原文の説明を表示しています。
Distributed storage systems design and operation for cloud platforms. Covers the GFS/HDFS block-and-master pattern, object storage (Swift/S3) with consistent hashing and eventual consistency, block storage semantics, replication vs erasure coding, the CAP theorem in practice, read-repair and anti-entropy, snapshot chains, and the GFS/BigTable/Spanner evolution. Use when designing a storage subsystem, choosing between object/block/file, or reviewing a replication and consistency strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.
日本語の概要は準備中です。原文の説明を表示しています。
OpenStack backup operations skill for protecting cloud infrastructure through systematic backup strategies and disaster recovery procedures. Covers database backups (MariaDB full and incremental with mariabackup), configuration backups (globals.yml, inventory, Fernet keys), volume snapshots (Cinder LVM snapshots), image exports (Glance), instance snapshots (Nova), backup encryption (GPG/OpenSSL), retention policies (daily/weekly/monthly rotation), restore procedures (database point-in-time recovery, service rebuild), RPO/RTO planning, and disaster recovery drills. Use when planning backup strategy, scheduling automated backups, testing restore procedures, or executing disaster recovery.
日本語の概要は準備中です。原文の説明を表示しています。
OpenStack capacity planning operations skill for resource planning, quota management, and scaling decisions. Covers compute capacity (allocation ratios, vCPU/RAM utilization, host aggregates, availability zones), storage capacity (Cinder pool sizing, thin provisioning, Glance storage, Swift rings), network capacity (floating IP pools, port quotas, subnet sizing), project quota management (templates for small/medium/large profiles), flavor sizing strategy, utilization analysis with placement service, growth forecasting from historical metrics, and right-sizing recommendations for underutilized resources.
日本語の概要は準備中です。原文の説明を表示しています。
用户审计自己的内容结构占比、判断单条帖子传播上限、或困惑"发了感叹/观点帖没人理"时调用。 关键 trigger: "内容原型/content archetype""哪种内容容易爆/which content goes viral" "传播上限/viral ceiling""普通表达型/资源入口型/工具教程型/AI工具发现型" "为什么没人互动/why no engagement""内容方向有问题/content direction wrong"。 不适用于: 已确定写某种短内容类型并需要组织结构(用 x-short-content-craft)、 检查帖子五件套完备性(用 x-five-piece-checklist)、做账号定位取舍(用 x-positioning-tradeoff)。
日本語の概要は準備中です。原文の説明を表示しています。
当用户想在大V帖下评论获取曝光、纠结Repost还是Quote、或问"怎么引发互动""怎么在别人帖下获曝光又不被当蹭流量"时调用。六种评论互动法(有价值提问/A-B引战/坎宁汉姆定律/真诚请教/生活日常/找骂)+高质量回复吃原帖流量+Repost vs Quote区分。Trigger:评论互动/蹭流量/Quote还是Repost/评论区抢占/comment engagement/quote vs repost/how to reply for exposure。不适用于:自己发原创帖(用x-short-content-craft)、冷启动整体策略排序(用x-cold-start-playbook)。
日本語の概要は準備中です。原文の説明を表示しています。
账号定位阶段做战略选择时用：用不可能三角（内容深度/传播力/变现力不可兼得）决定放弃哪个角，选IP路线（深度+变现，抗周期/高商业化/复利）或泛流量路线（传播力，但转化差不值钱）。Trigger："追粉丝还是做IP""IP还是泛流量""定位怎么选""深度和传播怎么权衡""泛流量不值钱吗""IP vs generic traffic""build IP or chase followers"。不适用：已有定位后的内容生产/选题（→内容创作类skill）；已有粉丝问怎么变现（→x-monetization-pyramid）；找对标账号（→x-benchmark-research）。
日本語の概要は準備中です。原文の説明を表示しています。
新号没粉丝、推文没人看、怎么度过冷启动时用。涨粉四步漏斗(曝光→展开→Profile门面→关注)诊断丢哪步,按边际回报排序投六策略:大V评论区抢占(最高)/引用转发+深度观点/每日发推/互关社区(≤15/天)/蹭热点/互动率优先;前24h主动加热突破初始池。Trigger:"没粉丝""帖子没人看""冷启动""怎么起量""0 followers""no engagement""cold start"。不适用:开业前装修/蓝V/养号(→x-account-setup)、已有稳定粉丝日常运营、限流封号排查(→x-account-pitfalls)、纯评论技巧(→x-comment-engagement)。
日本語の概要は準備中です。原文の説明を表示しています。