309건 · 관련도순
Design interview processes for specific roles and experience levels, with round objectives, timing, suggested questions, and scoring criteria. Help interviewers align their judgments and review potential bias before using the process.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review product roadmaps through six questions about customer needs, retention, priorities, and tradeoffs. Produce a recommendation on what to ship, refine, or stop, with measurable criteria for reassessing the decision after 90 days.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create or update STRATEGY.md through guided questions about a product’s purpose, users, success metrics, and investment areas. Capture a shared basis for product decisions, with draft review and focused updates to existing documents.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize product requirements into a single-page document covering the problem, success metrics, scope, user scenarios, design notes, rollout plans, and open questions. A status label shows whether the specification is a draft, approved, or shipped.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide a team through questions about users, workflows, and priorities to create a user story map. Organize activities and tasks, then define a minimum viable product and later releases that each cover the full workflow.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare for a senior product leadership role or work through challenges after taking one. Adaptive questions identify your transition stage and produce targeted recommendations on organizational leadership, executive relationships, role evaluation, and communicating business outcomes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn product management notes, frameworks, or rough ideas into a complete SKILL.md draft. Guided questions help choose the skill type, narrow its purpose, and organize instructions, examples, and common mistakes into the required structure.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Research product, design, and technical questions using external sources. Check where claims come from, distinguish observed behavior from interpretation, and turn findings into comparisons, recommendations, or concrete next steps for implementation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Get guidance on NotFair's paid advertising skills, installation, supported platforms, account connections, plans, and limits. Use it to understand available capabilities and troubleshoot setup or product questions outside account performance analysis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use when the user mentions Marketing Studio, DTC Ads, ad video, UGC video, the marketing_studio_video MCP model, or wants to generate one of the 9 Marketing Studio ad presets (UGC, Tutorial, Unboxing, Hyper Motion, Product Review, TV Spot, Wild Card, UGC Virtual Try On, Pro Virtual Try On). Also triggers on hook+setting picklist questions, preset-avatar / custom-avatar / text-generated-avatar handling, 4–15s ad video questions, or any reference to Higgsfield's ad-video product surface. Cross-surface workflow handoffs (GPT Image 2.0 / Soul Cinema / Nano Banana Pro / ms_image image gen → Marketing Studio video) covered in the companion cross-surface-workflow.md. Also use for Ad Multiplier (`ad_multiplier` — 'multiply my ad', many independently edited versions of one supplied 4–30s ad) and for Genjutsu one-off edits of a finished ad (swap one object / product / garment → `hf_mult_replace_object`; transfer motion → `hf_mult_motion_control`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Applies the product philosophy and leadership frameworks of Steve Jobs, co-founder and CEO of Apple Inc. Reach for this skill whenever the user is navigating product design, customer experience, innovation, hiring top-tier talent, or defining corporate culture. Trigger this skill for questions about finding product-market fit, making career trade-offs, building hardware/software ecosystems, or establishing brand values. Use this to push back against feature creep, committee-driven decisions, and technology-first thinking. Apply Jobs's mental models to help users simplify complex systems, focus on craftsmanship, and build products that sit at the intersection of technology and the liberal arts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sales enablement, technical presales and deal acceleration for B2B SaaS revenue teams. Use this skill when planning outbound campaigns, running discovery calls, building deal strategy, creating battle cards, writing proposals, responding to RFPs, preparing a product demo, scoping a proof of concept or pilot, answering a security questionnaire or the AI annex buyers now attach to it, executing sales sequences, coaching qualification, or deciding what the website's AI chat agent is allowed to say. Also triggers on: outbound, cold outreach, reply handling, reply classification, out-of-office replies, auto-replies counted as replies, our reply rate is inflated, prospect replied remove me, opt-out by reply, is this list ready to send, launch readiness, CRM segment outbound, we emailed a current customer, outbound hit an open opportunity, ownerless leads, prospects engaging our competitors, competitor connections, displacement list, is this personalization creepy, can we mention they visited our site, signal freshness, deal strategy, pipeline, battle card, objection handling, common objections, why do we keep hearing this objection, mine call transcripts for objections, objection register, proposal, RFP, discovery call, MEDDPICC, sales sequence, qualification, sales engineer, solutions engineer, presales, demo plan, demo script, POC, proof of concept, pilot success criteria, technical evaluation, technical win, security questionnaire, vendor security review, SOC 2 questionnaire, AI security questionnaire, AI annex, AI vendor due diligence, the buyer is asking if we train on their data, do you train on customer data, which model do you use, model provider sub-processor, AI subprocessor disclosure, where does inference run, can the customer turn the AI feature off, AI-CAIQ, CSA AI Controls Matrix, ISO 42001, ISO/IEC 42001, NIST AI RMF, EU AI Act Article 50, are we a provider or a deployer, AI feature disclosure, our model vendor changed and nobody told the buyer, technical objection, mutual action plan, MAP, close plan, mutual close plan, buyer enablement, the deal is stalled, deal stalled after the demo, how do I get this deal to close, close date keeps slipping, JOLT, buyer indecision, no-decision loss, website chatbot, chat widget, AI chat agent, AI SDR, inbound AI SDR, conversational marketing, live chat, what should our chatbot be allowed to say, our chatbot quoted the wrong price, the bot promised a discount, do we have to disclose it is AI, EU AI Act chatbot disclosure, chatbot handoff to sales, chat transcript review, prompt injection on our chatbot, Drift, Qualified, Intercom.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when designing a product catalog taxonomy, planning attribute strategy, or determining search and navigation structure for a B2B or B2C/D2C Commerce store. Triggers on: taxonomy design questions, attribute planning, search index strategy, category navigation structure, or merchandising hierarchy decisions. NOT for wiring the catalog itself — WebStoreCatalog, entitlement policies, product assignment — use admin/commerce-product-catalog. NOT for configuring searchable or facetable attributes, sort rules and index rebuilds — use apex/commerce-search-customization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the company is about to buy, renew or switch on an AI product or an AI feature inside an existing product, and asks "assess this AI vendor", "do they train on our data", "AI supplier questionnaire", "review the AI terms", "can we use this model provider with customer data", "who are the subprocessors behind this AI tool" or "AI vendor risk assessment". Sizes the review to the use, reads the terms, data processing agreement and documentation before asking questions, checks training use, retention, model changes, subprocessors, transfers, security and exit, and writes an assessment with a recommendation plus the follow-up questions for the vendor.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produces a DRAFT product requirements document from the discovery notes, interview summaries, support themes, analytics notes and stakeholder messages the user provides: problem statement, target users, goals with measures as stated, numbered requirements each with a testable acceptance criterion, non-goals, constraints, dependencies and open questions, with every statement tagged evidenced, assumed or UNKNOWN so each assumption is visible for the product owner to confirm. Use when the user asks to "write a PRD", "draft the product requirements", "turn these discovery notes into requirements", "document what this feature needs to do" or "build the requirements doc for this epic". Do not use for supplier-facing requirements in a tender, use rfp-requirements-pack instead; for a technical design decision, use architecture-decision-record; for the change ticket that ships the work, use change-request-pack. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and coordinate Strix security assessments across source code, running applications, APIs, and continuous integration pipelines. Combine findings into one prioritized remediation plan based on demonstrated impact, removing duplicates and documenting gaps in test coverage.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a website's screenshots and brand assets into a HyperFrames site tour or social clip. Develop a storyboard and script, add optional narration and captions, then validate the video and deliver a Studio preview.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explain how dot works and check why a task is blocked, including computer access, login, approvals, and Slack errors. It provides supported next steps and answers questions about changing dot’s avatar and the user’s message color.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design and implement web or iOS interfaces using the product’s existing components and design rules. Define required screen states and responsive behavior, consult optional visual references when useful, and inspect the rendered result when supported.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Design, refine, or review web and iOS interfaces using the product’s existing components and visual style. Consult relevant screen examples when useful, then inspect the result for layout problems, inaccessible controls, and broken interactions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.