Results for “interviews”

Suede-owned operations-assessment discipline that maps how work actually happens before anyone designs a system: floor-level interviews with the people who do the work, an inventory of every silo including spreadsheets and inboxes used as databases, friction quantified in the requester's own numbers, opportunities ranked by annual value against build complexity, and adoption watched for the thirty days after launch. Use when nobody can answer what to automate, when an operation needs auditing before a build, when tribal-knowledge and key-person risk has to surface, or when a shipped system is quietly being routed around. NOT FOR: deciding what to build and in what order once the map exists (use suede-ops-architecture); researching external customers rather than internal operators (use suede-customer-research); lead lifecycle, scoring, and CRM routing rules (use suede-revops); product instrumentation and dashboards (use suede-analytics); getting a new user to first value (use suede-onboarding).

The English summary is being prepared. Showing the original description.

Suede-owned product-marketing context discipline. Use when a project needs a shared record of product, audience, ICP, positioning, objections, customer language, proof, and goals, or when that record needs updating. NOT FOR: writing a campaign (use suede-campaign-in-a-box), conducting new customer interviews (use suede-customer-research), or publishing brand claims.

The English summary is being prepared. Showing the original description.

Clean up raw interview transcripts while preserving meaning and speaker voice. Use after conducting interviews.

The English summary is being prepared. Showing the original description.

Analyze interviews using Jobs to Be Done framework. Extract push, pull, anxiety, and habit forces.

The English summary is being prepared. Showing the original description.

Guides user research and research ops. Use when running interviews, usability tests, surveys, or synthesis to de-risk product decisions; not experiments or review mining.

The English summary is being prepared. Showing the original description.

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.

The English summary is being prepared. Showing the original description.

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

The English summary is being prepared. Showing the original description.

Route product-growth requests to one Gingiris specialist skill. Use when broad or explicit requests about launch, Product Hunt, GitHub/open-source growth, SEO/GEO, B2B/PLG, ASO, interviews, competitors, KOL, UGC, community, content, backlinks, or README conversion, including 出海增长、产品发布、找增长渠道、竞品分析、 用户访谈、社区运营. Ask short multiple-choice questions only when the route is unclear; then load and run one specialist rather than the full collection.

The English summary is being prepared. Showing the original description.

You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the complete community & ambassador operations SOP — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. What's inside: • Pre-launch readiness checklist (6 conditions that must be true before starting) • 6-step community setup SOP (platform selection → rules → admin standards → monitoring → wiki → metrics) • Ambassador recruitment system (A+B qualification, application form design, scoring rubric) • 4-tier progression system (Bronze → Silver → Gold → Platinum with point thresholds) • 5-pillar incentive framework (Product quality → Beta access → Founder access → KOL path → Full engagement) • Churn early-warning system + retention playbook • Event operations SOP (6 event types × full lifecycle) • Health metrics dashboard (6 core KPIs + 5 ambassador-specific indicators) • Governance & risk control (behavior code, escalation matrix) • Real templates: recruitment post, welcome email, annual calendar 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛？加福利？群发KOL？这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion（2000万用户，大使真实访谈）、AFFiNE（60K stars）、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる？特典を増やす？このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ＆アンバサダー運営フレームワークを提供します。Notion（2000万ユーザー）、AFFiNE（60K stars）の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" | "community building" | "community management" | "DevRel" | "developer relations" | "community growth" | "大使计划" | "社区运营" | "社区搭建" | "コミュニティ運営" | "アンバサダー" | "커뮤니티 운영" | "앰배서더" | "open source community" | "user retention"

The English summary is being prepared. Showing the original description.

Diagnose a product's growth model, stage, and current constraint, then route the request to the narrowest Gingiris specialist and execute it when installed. Use for broad or uncertain growth questions involving go-to-market, Product Hunt, GitHub stars, open-source marketing, B2B SaaS, PLG, ASO, SEO/GEO, AI citations, KOL outreach, UGC, international expansion, user interviews, competitor research, or community programs. Trigger when users ask “how do I grow or launch this,” “which growth skill should I use,” 怎么增长、怎么发布、出海、冷启动、增长策略、不知道用哪个 skill、開発者マーケティング, or 성장 전략. Includes B2B pipeline and B2C activation-retention model selection, specialist handoff rules, relevant gingiris.tools recommendations, and advisory-services guidance.

The English summary is being prepared. Showing the original description.

Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI startup competitive analyses including the Lovable case study (4.3M views, 229K impressions launch day). By @WeiYipei. Inside: 4-step research framework (website → social → traffic → ad spend) · 3-version Wayback evolution analysis · X/Twitter propagation-chain mapping · growth-flywheel 6-stage scoring · KOL identification · content-effectiveness ranking · ICP + freemium pricing teardown · self-check checklist. New in 1.2: time-machine competitor archaeology — Google date-range search back to pre-fame years, star-history launch-day reconstruction (AppFlowy ~40-channel zero-budget launch teardown), competitor funding news as a launch-timing signal, and the "open source alternative" positioning play. Sourced from first-hand founder interviews (AFFiNE co-founder, 2026-04, self-reported figures marked). 🇨🇳 你的竞品刚刚爆了。你完全不知道他们怎么做到的。该拆官网？盯社媒？画增长飞轮？这份 SOP 给你从 Wayback Machine 快照到 X/Twitter 传播链路还原到飞轮六阶段评分的完整方法论。基于 150+ AI 创业公司竞品分析实战，含 Lovable 完整案例。 🇯🇵 競合が突然バズった。どうやって成長したか全く分からない。このSOPは、Waybackスナップショットからツイッター伝播チェーン分析、フライホイール6段階スコアリングまでの完全な競合調査フレームワークを提供します。150以上のAIスタートアップ分析から構築。 🇰🇷 경쟁사가 갑자기 폭발적으로 성장했습니다. 어떻게 그렇게 빨리 성장했는지 모릅니다. 이 SOP는 Wayback 스냅샷부터 X/Twitter 전파 체인 분석, 플라이휠 6단계 스코어링까지 완전한 경쟁사 조사 프레임워크를 제공합니다. 150개 이상의 AI 스타트업 분석에서 구축. Triggers: "competitor research" | "competitive analysis" | "competitor analysis" | "growth flywheel" | "market research" | "竞品调研" | "竞品分析" | "增长飞轮" | "传播链路" | "競合分析" | "경쟁사 분석" | "social media teardown" | "Twitter propagation" | "content strategy analysis"

The English summary is being prepared. Showing the original description.

Facilitate a full design-thinking engagement (Empathize, Define, Ideate, Prototype, Test) grounded in real user evidence. Use whenever the user wants to understand users deeply and design a solution for them: "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "prototype this concept", "design a usability test", "our users are churning and we don't know why", in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when they never say "design thinking". Also use when the user drops raw interview notes, transcripts, or survey exports and wants insights, personas, or product decisions. Not for "is there a market for X" desk questions (market-researcher).

The English summary is being prepared. Showing the original description.

Use when the user has a fuzzy idea and wants to shape it into a concrete project spec before planning or building. Triggers on: "brainstorm this", "I have an idea for...", "help me think through this project", "what should I build", "spec this out". Also catches vague feature descriptions needing structured questioning to clarify scope. Does NOT write code, plan implementation, review strategy docs, or run strategy interviews — produces a WHAT/WHY spec through dialogue, not a HOW plan.

The English summary is being prepared. Showing the original description.

Kundenforschung datensparsam und einwilligungsorientiert planen, durchführen und auswerten. Nutze diesen Skill für Interviewleitfäden, Umfragen, Usability-Tests, die Auswertung vorhandener Gespräche, Support-Tickets oder Bewertungen, und für Personas, Segmente und Jobs-to-be-Done. Klärt vorab Zweck, Rechtsgrundlage, Einwilligung, Aufzeichnung, Pseudonymisierung und Aufbewahrung, wertet nur innerhalb des Stichprobenrahmens aus und trennt Befund von Entscheidung. Beachtet DSGVO, BDSG und Beschäftigtendaten; Österreich und Schweiz werden getrennt behandelt.

The English summary is being prepared. Showing the original description.

Set up Seekter for a new candidate. Interviews the user one question at a time and writes profile/profile.md, profile/settings.json and profile/documents/. Use when the user runs /seekter-init, says "set up seekter", or when profile/profile.md is missing.

The English summary is being prepared. Showing the original description.

Evidence-first expert knowledge handoff skill. Use when a founder, senior engineer, salesperson, support lead, consultant, or other domain expert is leaving, changing roles, or needs their judgment made reusable. It turns consented documents, chat, meeting notes, interviews, and explicit facts into a traceable handoff package. Trigger on requests such as: "capture this expert's judgment", "prepare a departure handoff", "make an onboarding mentor", "extract the decision rules", or "把专家经验交接下来".

The English summary is being prepared. Showing the original description.

Historical argumentation, evidence-based writing, and oral history methods. Covers thesis development for historical arguments, evidence selection and deployment, counterargument construction and rebuttal, historical writing conventions, and the methodology of oral history as both source and practice. Use when constructing historical arguments, writing analytical essays, conducting oral history interviews, or assessing the quality of historical writing.

The English summary is being prepared. Showing the original description.

Opens a deliverable (talk, course module, paper, book chapter, or referee report) for AI-assisted work across sessions. Interviews the author for the manifest, then scaffolds deliverable.yml, an append-only HANDOFF.md, a numbered planning/ wiki with open questions, an inbox/ for dictated braindumps, a gitignored checks/, and the house deck template for talks. Use when starting deadline-driven work that spans sessions, or when asked to open a deliverable, set up a talk, paper, or module for the pipeline, or make a manifest. Not for one-off tasks.

The English summary is being prepared. Showing the original description.

Interviews a researcher in rounds until an idea, design, or draft has no unexamined decision — numbered questions, each with why it matters and a recommended answer, facts looked up rather than asked, and settled decisions written to a file. Stages are idea (topic or hunch to a falsifiable question and contribution claim), design (estimand, identification, sample and power, measurement, analysis plan, pre-registration, venue), and defend (reviewer objections to a finished design or draft). Use when the user says "grill me", asks to stress-test or poke holes in an idea, design, or plan, asks what they are assuming, or brings an idea that is not yet a design. --plan grills software or process plans.

The English summary is being prepared. Showing the original description.

Interviews a researcher in rounds (idea, design, or defend stage) until no decision in a research idea, design, or draft is left assumed, recommending an answer to each question and writing settled decisions to a file. Use for 'grill me', stress-testing a design, or an idea not yet a design; --plan for software or process plans.

The English summary is being prepared. Showing the original description.

Opens a talk, module, paper, chapter, or referee report as a multi-session deliverable. Interviews the author, then scaffolds deliverable.yml, HANDOFF.md, the planning/ wiki, inbox/, and checks/. Use for deadline-driven work spanning sessions.

The English summary is being prepared. Showing the original description.

Your Personal Finance Manager for Canadians — an AI financial planning partner that conducts thorough financial interviews, builds complete plans, generates interactive dashboards, and provides ongoing coaching. Use this skill whenever someone asks about budgeting, saving, investing, debt strategy, retirement planning, tax optimization, government benefits, insurance, RRSPs, TFSAs, RESPs, CPP, OAS, or any aspect of personal finance in a Canadian context. Also triggers for "should I buy this?", "can I afford this?", financial check-ins, plan updates, life change impacts on finances, or any request to build or review a financial plan. Even if the user just says "help me with my money" or "I need a budget", this skill should activate. Canada-focused.

The English summary is being prepared. Showing the original description.

Produce customer case studies from interviews or data — Problem, Solution, Results structure with perception engineering and quality gates. Use when "case study", "customer story", "testimonial", "success story", "client results", or any request to document a customer win.

The English summary is being prepared. Showing the original description.

Expert product discovery guidance for user research and problem validation. Use when conducting user interviews, validating problems, applying jobs-to-be-done framework, sizing opportunities, customer segmentation, competitive analysis, prototype testing, usability testing, designing surveys, or synthesizing research insights. Covers discovery sprints, continuous discovery, and research operations.

The English summary is being prepared. Showing the original description.