スキルを探す

Review marketing KPIs and produce an executive summary with insights, anomalies, and recommended actions using the Storytelling with Data framework (Cole Nussbaumer Knaflic). Every review starts with a Big Idea - one sentence capturing the insight, its implication, and why it matters. Use when the user asks for a KPI review, monthly metrics review, marketing dashboard review, "review last month's numbers", quarterly review, performance review, or wants to analyze marketing data. Reads kpis.md and any uploaded data files. For planning a campaign against these numbers, see campaign-brief. For the post-campaign learning loop, see retro. For setting the baseline itself, see brand-context.

日本語の概要は準備中です。原文の説明を表示しています。

Write landing page copy for product pages, campaign pages, lead-gen pages, pricing pages, and feature pages. Use when the user asks for landing page copy, product page, lead magnet page, "write the page for X", pricing page copy, feature page, hero section, or web copy that converts. Uses the StoryBrand SB7 framework (Donald Miller) to structure every page. Reads brand voice, positioning, and ICP from knowledge/. For improving an existing page's copy, see copy-review. For diagnosing why a page does not convert, see page-cro. For the ads driving traffic to it, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

Write a high-performing LinkedIn post in the user's brand voice using Hook-Story-Offer (Russell Brunson) and the Curiosity Gap hook method (George Loewenstein). Every post starts by selecting a named hook formula - specific number + surprising result, contrarian statement, personal confession, direct challenge, or before/after. Use when the user asks for a LinkedIn post, LinkedIn update, LinkedIn content, "post for LinkedIn", thought-leadership post, founder post, or short professional social content. Reads brand voice and ICP from knowledge/ so output sounds like the company, not generic AI. For long-form opinion pieces, see thought-leadership-writer. For the monthly posting plan, see social-calendar. For turning one asset into many posts, see content-repurposer.

日本語の概要は準備中です。原文の説明を表示しています。

Write recurring newsletter issues with a consistent format and POV using the Curiosity Gap (George Loewenstein) and David Perell's Online Writing framework. Different from one-off emails (use /content-writer or /email-nurture). Use when the user asks for a newsletter, weekly/monthly newsletter, "write this week's issue", recurring email, Substack issue, internal newsletter, or any periodic publication with subscribers. Reads brand voice and content library from knowledge/. For a nurture or lifecycle sequence, see email-nurture. For long-form thought leadership, see thought-leadership-writer. For the monthly plan, see social-calendar.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose why a landing page, homepage, pricing page, or signup form is not converting, and produce a ranked fix list with a test plan. Runs a structured audit across motivation, value clarity, friction, anxiety, and CTA hierarchy rather than giving generic design opinions. Use when the user says "why isn't this page converting", "improve our conversion rate", "CRO", "conversion audit", "this page isn't working", "high traffic low signups", "people bounce", "review our landing page", or shares a URL and asks what is wrong with it. For rewriting the words only, see copy-review. For writing a new page from scratch, see landing-page-writer. For the statistics of running the test afterwards, see growth-experiment.

日本語の概要は準備中です。原文の説明を表示しています。

Write a product positioning document. Use when the user says "write a positioning doc", "positioning statement", "how should we position this product", "positioning for [product]", "we need to differentiate from competitors", "product positioning and messaging", "positioning workshop", "help me define our position in the market", or wants to establish how a product should be perceived relative to competitors. For customer-facing message wording, see messaging-framework. For the competitive research behind it, see competitor-analyst. For storing it in the knowledge base, see brand-context.

日本語の概要は準備中です。原文の説明を表示しています。

Build branded PowerPoint decks (.pptx) for pitches, internal updates, sales decks, customer QBRs, board updates, conference talks using the Pyramid Principle and SCQA framework (Barbara Minto, The Minto Pyramid Principle). Every deck starts with the answer - conclusion on slide 2, evidence after. Slide titles are conclusions, not topics. Use when the user asks for a deck, presentation, slides, pitch deck, sales deck, board deck, QBR, "make slides for X", or "build a presentation". Uses templates/ for brand assets. Generates structured slide content with speaker notes. For the narrative content of the deck, see thought-leadership-writer or campaign-brief. For a case study slide, see case-study-writer.

日本語の概要は準備中です。原文の説明を表示しています。

Critique a design for usability, hierarchy, and accessibility. Use when the user says "critique this design", "review this screen", "what's wrong with this UI", "design feedback", "UX review", "how can I improve this", "review my mockup", "is this good UX", or shares a design and wants structured feedback - even if they don't explicitly say "design critique".

日本語の概要は準備中です。原文の説明を表示しています。

Document a design system component. Use when the user says "design system docs", "document this for the design system", "add this to the design system", "design token", "component library docs", "style guide", "design system entry", or wants to formally document a pattern, component, or token for team-wide use - even if they don't explicitly say "design system".

日本語の概要は準備中です。原文の説明を表示しています。

Write a blameless postmortem after an incident. Use when the user says "postmortem", "post-incident review", "PIR", "what happened in that incident", "incident review", "blameless postmortem", "5 whys", "how do we prevent this again", or needs to document learnings from a production incident - even if they don't explicitly say "postmortem".

日本語の概要は準備中です。原文の説明を表示しています。

Build psychological safety in your team using Simon Sinek's Leaders Eat Last Circle of Safety model and Amy Edmondson's research. Use when a leader says "my team doesn't speak up", "people are afraid to fail", "nobody challenges bad ideas", "people only tell me what I want to hear", "I want my team to take more risks", "there's a blame culture", "people hide mistakes", or "I want to create a safe environment". Also trigger when someone describes a team where postmortems turn into blame sessions, where people stay quiet in meetings and then vent privately, where mistakes are hidden until they become crises, or where the same person speaks 80% of the time in every meeting. Psychological safety is not about comfort - it is the condition that makes high performance possible.

日本語の概要は準備中です。原文の説明を表示しています。

Turn raw customer material into evidence-backed personas and verbatim voice-of-customer language. Two modes - analyse sources the user already has (call transcripts, support tickets, survey responses, sales notes, reviews), or source new material from public places customers actually talk. Produces quoted pains, objections, and switch triggers that other skills consume, never invented ones. Use when the user says "customer research", "voice of customer", "what do our customers actually say", "we need real quotes", "analyse these call transcripts", "read our support tickets", "build a persona from data", "find what customers complain about", or when a persona is marked provisional. For structuring the finished persona into the knowledge base, see brand-context. For the JTBD persona template itself, see customer-persona.

日本語の概要は準備中です。原文の説明を表示しています。

Build a brand messaging framework or messaging hierarchy. Use when the user says "messaging framework", "brand messaging", "what should our tagline be", "clarify our messaging", "StoryBrand", "brand script", "our website copy is confusing", "we need a messaging hierarchy", "homepage messaging", "value prop copy", or wants to create consistent, clear messaging that converts visitors into customers. For the underlying positioning, see positioning-doc. For applying the message to a page, see landing-page-writer. For checking live copy against it, see copy-review.

日本語の概要は準備中です。原文の説明を表示しています。

Rewrite UI copy directly on Figma files to be simpler, jargon-free, and terminologically consistent. Trigger when: user says "rewrite copy", "simplify copy", "fix the text", "copy audit", "UX copy review", "clean up the wording", shares a Figma URL and mentions copy/text/wording, or asks to make text simpler/clearer/more consistent on a Figma file.

日本語の概要は準備中です。原文の説明を表示しています。

Audit a user flow for friction and drop-off points. Use when the user says "UX audit", "audit this flow", "where are users dropping off", "why isn't this converting", "review the onboarding", "usability audit", "what's causing friction", "user journey review", or wants to identify why users struggle with a flow - even if they don't explicitly say "UX audit".

日本語の概要は準備中です。原文の説明を表示しています。

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

Behavioral guardrails against the six most common LLM coding failure modes. Apply on every coding task: writing, editing, reviewing, or refactoring.

日本語の概要は準備中です。原文の説明を表示しています。

Write a clear pull request description. Use when the user says "write a PR description", "PR template", "pull request description", "how do I describe this change", "commit message for this", "document this change", "open a PR for", or is about to merge code and needs to communicate what changed and why - even if they don't explicitly say "PR description".

日本語の概要は準備中です。原文の説明を表示しています。

Analyze competitors using Blue Ocean Strategy's ERRC Grid and Strategy Canvas (W. Chan Kim and Renee Mauborgne) to identify uncontested market space, not just who is better on the same axes. Produces an ERRC Grid, Strategy Canvas, positioning matrix, messaging comparison, and differentiation map. Use when the user asks for competitive analysis, competitor research, "how do we compare to X", positioning vs competitors, market landscape, "analyze our competition", "where is the blue ocean", or wants to update competitor docs. Writes to knowledge/markets/competitors.md. For a lightweight competitor summary in the knowledge base, see brand-context. For positioning against them, see positioning-doc.

日本語の概要は準備中です。原文の説明を表示しています。

Build or refine the Ideal Customer Profile (ICP) and personas using the Jobs-to-be-Done framework (Clayton Christensen / Bob Moesta). Use when the user asks for ICP research, persona development, "who are our customers", buyer personas, audience research, "build our ICP", target customer definition, or wants to update persona docs. JTBD interview questions, three job dimensions (functional/emotional/social), and the Four Forces of Progress are wired into every persona. Writes to knowledge/icp/personas.md so all other skills get smarter. For the individual buyer persona rather than the segment, see customer-persona. For sourcing real customer language, see customer-research.

日本語の概要は準備中です。原文の説明を表示しています。

Write a Functional Requirements Document. Use when the user says "write an FRD", "functional requirements", "system requirements", "SRS", "what should the system do", "document the functional specs", "software requirements specification", "detailed requirements for engineering", "functional spec" - even if they don't explicitly say "FRD".

日本語の概要は準備中です。原文の説明を表示しています。

Write an executive summary using the Pyramid Principle SCQA structure. Use when a consultant says "write an executive summary", "I need a one-pager for the exec", "how do I open this report", "write me the intro for this deck", "draft the cover memo", "I need to frame the findings", "executive doesn't have time to read the full report", "help me write the storyline", or "write the situation-complication-answer". Also trigger when someone has findings or recommendations and needs to communicate them top-down to a time-constrained audience.

日本語の概要は準備中です。原文の説明を表示しています。

Define the scope, success criteria, roles, and boundaries for a consulting engagement. Use when a consultant says "help me scope this engagement", "I need to define what's in and out", "the client keeps adding things", "scope is getting fuzzy", "we need a contracting conversation", "I'm not sure what we actually agreed to", "help me set boundaries with a client", or "what should be in a kickoff". Also trigger when describing an engagement that feels like it is expanding without agreement, or when starting a new client relationship and preparing the initial contract or SOW.

日本語の概要は準備中です。原文の説明を表示しています。

Draft professional emails (MoM, status updates, decisions, stakeholder communication) and save as a draft in your email provider. Use this skill after a meeting, decision, spec update, or any event that needs email communication. Trigger phrases: "send MoM email", "draft meeting minutes email", "MoM email for [meeting]", "create MoM draft", "email the meeting notes", "draft MoM", "draft email", "send update email", "draft email for [topic]". Reads context from meetings, specs, tickets, and conversation. Looks up attendee emails from a local team directory, formats as HTML email, and pushes to the email provider as a draft (never sends).

日本語の概要は準備中です。原文の説明を表示しています。