スキルを探す

Write or refine a research hypothesis. Use when the user says "write a hypothesis", "frame my hypothesis", "is my hypothesis testable", "null and alternative hypothesis", "research hypothesis", "refine my hypothesis", "hypothesis statement", "H0 and H1", "operationalize my hypothesis", "turn my research question into a hypothesis", or needs to convert a research question or intuition into a falsifiable, testable hypothesis with clear variables and predictions - even if they don't explicitly say "hypothesis".

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

Construct a compelling job offer. Use when the user says "write an offer letter", "help me make an offer", "how should I structure this offer", "what should we include in the offer", "how do I explain the equity", "the candidate is negotiating", or wants to convert a candidate from interested to accepted - even if they don't explicitly say "offer letter". Also use when a recruiter needs to explain comp philosophy or total compensation to a candidate.

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

Structure and prepare for a sales discovery call. Use when the user says "prep for discovery call", "discovery call questions", "how to structure my discovery call", "first call with a prospect", "what to ask on a discovery call", "sales call prep", "plan my discovery call", "initial call framework", or wants to prepare for or debrief a first sales conversation.

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

Handle sales objections using tactical empathy. Use when the user says "how do I handle this objection", "prospect said [X]", "they pushed back on price", "they said they're not ready", "how to respond to 'we already have a solution'", "they said 'send me more information'", "objection response", "they went dark after the proposal", "how to handle 'we don't have budget'", or wants to craft a response to a specific sales objection.

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

Write a vulnerability report. Use when the user says "vulnerability report", "vuln report", "security finding", "write up this finding", "pentest finding", "bug bounty report", "security disclosure", "CVE writeup", "document this vulnerability", "how to report a security issue", or needs to formally document a security vulnerability with evidence, impact, and remediation guidance - even if they don't explicitly say "report".

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

Build a candidate sourcing strategy and outreach pipeline. Use when the user says "where do I find candidates for this role", "build a sourcing plan", "write a cold outreach message", "we're not getting enough applicants", "our pipeline is dry", "help me find passive candidates", "write a LinkedIn message", or wants to increase the volume or quality of candidates in the funnel - even if they don't explicitly say "sourcing strategy". Also use when a recruiter needs to go beyond job postings to find talent.

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

Write a performance-based job description. Use when the user says "write a JD", "draft a job posting", "create a job description", "help me post this role", "write requirements for this position", or wants to define what success looks like in a role - even if they don't explicitly say "job description". Also use when a hiring manager says "I need someone who can do X, Y, Z" and needs that translated into a structured posting.

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

Design a research study. Use when the user says "study design", "design my research", "what research method should I use", "how do I test this hypothesis", "research plan", "methodology section", "experimental design", "survey design", "qualitative study design", "how to structure my study", "sample size", "data collection plan", or needs to plan how to test a research question or hypothesis - even if they don't explicitly say "study design".

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

Write a threat model document. Use when the user says "threat model", "threat modeling", "STRIDE analysis", "attack surface analysis", "security design review", "what are the threats to this system", "adversarial analysis", "identify threats", "security threat assessment", or needs to systematically identify and document threats to a system or feature - even if they don't explicitly say "threat model".

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

Qualify a sales opportunity using the MEDDIC framework. Use when the user says "qualify this deal", "is this deal real", "MEDDIC qualification", "MEDDICC framework", "should I pursue this opportunity", "deal review", "how qualified is this prospect", "pipeline review prep", "forecast this deal", "sanity check on this opportunity", or wants to assess whether a sales opportunity is worth pursuing and at what pipeline stage.

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

Write a literature review. Use when the user says "literature review", "lit review", "review the literature", "summarize prior research", "what does the research say about", "synthesize research on", "background section", "related work section", "what has been studied on this topic", or needs to systematically identify, synthesize, and critically evaluate existing research on a topic - even if they don't explicitly say "literature review".

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

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

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

Write a penetration test scope document. Use when the user says "pentest scope", "pen test scope document", "penetration testing scope", "scope of engagement", "rules of engagement", "what to include in a pentest", "security assessment scope", "red team scope", "bug bounty scope", or needs to define the boundaries, objectives, and rules for a penetration testing engagement - even if they don't explicitly say "scope".

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

Write a compelling sales proposal. Use when the user says "write a sales proposal", "put together a proposal", "draft a proposal for this prospect", "create a business case", "write up our recommendation", "how to structure a proposal", "proposal template", "executive summary for a deal", or wants to create a written document that moves a prospect toward a decision.

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

Run a recruiter-hiring manager intake meeting to kick off a search. Use when the user says "I need to kick off hiring", "run the intake call", "prepare for the intake meeting", "align with the hiring manager on this role", "we're opening a req", or wants to define hiring criteria and process before sourcing begins - even if they don't explicitly say "intake meeting". Also use when a recruiter needs to get a hiring manager aligned on what "great" looks like before anyone talks to a single candidate.

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

Build a structured interview scorecard for a role. Use when the user says "create an interview scorecard", "build an interview guide", "what questions should I ask for this role", "help me evaluate candidates consistently", "design the interview process", or wants to assess candidates against defined criteria - even if they don't explicitly say "scorecard". Also use when a recruiter or hiring manager wants to prevent gut-feel hiring.

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

Write user stories with acceptance criteria. Use when the user says "write user stories", "convert this to stories", "create acceptance criteria", "break this into tickets", "story map", "walking skeleton", "story for this feature", or wants to translate a feature idea into sprint-ready items - even if they don't explicitly say "user stories".

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

Write a Product Requirements Document (PRD). Use when the user says "write a PRD", "document this feature", "product requirements for X", "write requirements", "I need a PRD", "pitch this feature", or wants to formalize a feature or product idea into a structured doc - even if they don't explicitly say "PRD".

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

Identify, score, and mitigate delivery risks for a program or release. Use when the user says "risk review", "what could go wrong", "risk register", "delivery risks for this release", "program risk assessment", "identify blockers before they hit", or wants to pressure-test a plan before committing - even if they don't say "risk review". Based on "The Phoenix Project" by Kim, Behr & Spafford (unplanned work, fragile systems, single points of failure) and "The Art of Project Management" by Scott Berkun (scoping risk, milestone pressure, hidden assumptions).

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

Generate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report

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

Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags. For improving an existing article, see copy-review. For deciding what to write about, see social-calendar pillars and icp-research. For repurposing it, see content-repurposer.

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

Quality gate for product specifications before stakeholder review. Use this skill when: - A spec draft is ready and you want to validate it before sending to Engineering, Design, and QA - You want to check a spec against your template's completeness rules - You need to catch vague language, missing sections, or gaps before review - You want a pass/fail scorecard with specific fix suggestions

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

Write an empowered team brief. Use when the user says "team brief", "product brief", "give the team a problem", "empowered team", "how do I brief engineering", "delegate to the team", "product mission", or wants to give a team clear goals without dictating the solution - even if they don't say "team brief".

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

Surface and visualize hidden dependencies blocking delivery. Use when the user says "map our dependencies", "what's blocking what", "dependency audit", "why are teams blocked", "we have a bottleneck", "draw out the dependencies", or asks to identify cross-team blockers - even if they don't explicitly say "dependency mapping". Based on "Making Work Visible" by Dominica DeGrandis (time theft, invisible work, flow blockers).

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