'what' 검색 결과

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still an open loop, and what was just started. Use when someone asks "what happened this week", "what is still open", "what did the team finish", "give me the weekly rollup", or wants a status report over a .specstory/history corpus.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

First-encounter orientation on a repository nobody here has worked in yet. Runs a fixed five-step workflow — venv setup, tarball fetch, tree-sitting structural scan, featuring synthesis, then reasoning over the two — and yields an account of what the repo contains and how it is arranged, optionally written out as _FEATURES.md. Use for "I just cloned this", "what is this repo", "what does this do", "explore this repo", "give me an orientation", "what are the main features", "review what's new in this repo", or before starting work in a codebase you have not seen. This is the divergent what's-here skill. Route elsewhere for: a named symbol, a file's structure or a line range (tree-sitting); all callers of a Python symbol (searching-codebases); teaching a human the codebase through exercises (orienting-codebases); fetching or cloning a repo without analysing it (accessing-github-repos, cloning-project).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

The harnesses a campaign keeps, read outside a run: which there are and where each came from, what each is made of and what moved from its parent, what each was measured to be, trying one on a task, the audit before a promotion and the blind review at a handover, whether a part earns its place, and changing what makes a harness or what a seat is told about one. Use when the operator asks which harness is current, what a Builder changed, whether a harness is ready to promote or hand over, to run a kept harness on a task, or to change the harness contract. Reading one run is whole-run-investigation's, wording a claim attribution-and-proof's.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Post a sitrep (situation report) for a live incident, in its incident channel: a short fixed-layout update for people who haven't read the whole channel — the current picture and what moved since the previous update. Use on "sitrep", "status update", "where are we", "what's the latest", "catch me up", "summarize the incident so far", when asked to keep posting on a schedule ("post a sitrep every hour until resolved"), or when the oncall memory sets an update cadence for this severity and the incident owner asks Claude to keep it. Reads the channel, alert thread and findings posted, re-reads the one key signal, and writes: status line, TL;DR, impact, what changed since the last sitrep, what's in progress and who has it, what's needed, when the next update comes, one chart. Facts come only from what people said or Claude read first-hand; cause and recovery time are never guessed. Fits one phone screen. Not investigation (`incident-investigate`) or the write-up afterwards (`incident-postmortem`).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

App Store / Google Play のメタデータ最適化（ASO）を、4つの専門エージェントチームで実行するスキル。 キーワード調査、宣伝テキスト作成、競合分析、多言語ローカライゼーションの4観点から App Store 向けテキスト一式（タイトル、サブタイトル、キーワード、説明文、宣伝テキスト、What's New）を 生成し、最終レポート(MD)を出力する。多言語対応（日本語・英語+他言語）。 Use when: App Store の説明文を書きたい、ASO対策したい、キーワード選定したい、 宣伝文章を作りたい、App Store テキストを多言語化したい、What's New を書きたい。 Triggers: "ASO", "App Store", "宣伝文", "説明文", "キーワード", "サブタイトル", "What's New", "promotional text", "app description", "keyword optimization", "ストア掲載", "メタデータ", "アプリ紹介文", "Google Play", "多言語ASO"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Discover what Cowork can do for YOUR specific role and tasks, for mapping your daily work to Cowork capabilities. Use when exploring what Cowork offers, for planning your Cowork adoption, during onboarding and role discovery, when figuring out where to start, or when the user says "what can cowork do", "what is cowork", "show me cowork features", "how can cowork help me", "what should I use cowork for", or "cowork capabilities".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Привязать (или ПЕРЕпривязать) WhatsApp к этой машине — единственный шаг, который нельзя сделать за Антона, потому что… Триггеры «/whatsapp-pair», «/wa-pair», «подключи ватсап», «привяжи ватсап», «спарь ватсап», «ватсап отвалился», «ватсап не спарен», «перепривяжи whatsapp», «покажи QR ватсапа», «второй ватсап», «два ватсапа», «ватсап 2 аккаунта», «pair whatsapp», «relink whatsapp»

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Check the working conditions of a Japanese job offer item by item against the conditions an employer states in writing, compare the offer letter or 労働条件通知書 with the job posting and what was said in interviews, and separate what is confirmed in writing from what is still only verbal. Use when a user has received an offer, a working-conditions notice, or an employment contract and wants to know what is missing, what conflicts with earlier statements, and what to confirm before the acceptance deadline; do not use to rule on whether the terms are lawful, to decide whether to accept or decline, or to contact the employer on the user's behalf.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social-content.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review APIs, data structures, and workflows for mistakes that are easy to make silently. Proposes types, database constraints, and enforced checks to prevent misuse, ranks findings by impact, and explains what each fix can and cannot prevent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Design APIs that prevent invalid inputs and call sequences
• Audit existing code for silent misuse hazards
• Address recurring bugs by changing the design that permits them

Help junior developers and AI newcomers understand code through guided questions and progressive hints. Support debugging, concept learning, and critical review of AI-generated code so learners can explain their reasoning and work toward solutions themselves.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Understand errors through guided questions
• Explain AI-generated code in your own words
• Learn with pseudocode and progressive hints

Turn an open-ended business request into a recommendation for the right Small Business plugin skill or command. It considers stored business context, urgency, and connected tools, explains the next step, and requests confirmation before starting.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding where to start with a business concern
• Choosing a workflow for an urgent cash concern
• Exploring available business support features

Summarize the sales week with won and lost deals, stage changes, new opportunities, activity counts, and next week's priorities. Create an individual or team recap and a chat-ready draft using connected tools or uploaded exports.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing a personal sales recap for the week
• Reviewing team results with a breakdown by representative
• Planning Monday's meetings and follow-ups

Find statements, decisions, and commitments in Circleback meeting records. Search by people, company, tags, or dates, then use notes and transcripts to distinguish discussion from agreement and identify the meeting behind each answer.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking what was agreed with a customer
• Finding who promised a deadline
• Looking up exact wording in a meeting

Find what people said, decided, or promised in Granola meetings. The skill narrows meetings by date and participants, checks notes before transcripts, distinguishes decisions from discussion, and supports each finding with its meeting title and date.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking decisions from last week's customer call
• Verifying the exact wording of a commitment
• Reviewing customer feedback across multiple meetings

Plan bug bounty sessions around a clear goal and selected vulnerability types. Guides movement through reconnaissance, mapping, discovery, proof, and reporting, with prompts and routing to help decide what to investigate next.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Set the goal for a hunting session
• Decide what to investigate next
• Map application roles and trust boundaries

Examine what a file claims about itself and what it actually contains — powered by Apache Tika. True content-based type detection (extensions lie), provenance claims (authors, dates, creating application), revision and tamper signals (PDF incremental updates, tracked changes, hidden slides, zip integrity), hidden and embedded content (attachments, macros), risk indicators (PDF JavaScript actions, encryption), and content digests. Evidence gathering, not verdicts: Tika reports what the file asserts and what parsing observed; it does not attribute authorship or validate signatures. Use for triaging suspicious files, provenance questions, e-discovery-style review, or "is this file what it claims to be."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess whether source code is ready to deploy to Azure — the check BEFORE infrastructure work. Evaluates build health, app completeness, dependencies and local services, stack compatibility, and deployment feasibility. Answers questions about what your app needs before it can be deployed — frameworks, dependencies, and configuration. Checks whether dependencies are compatible and identifies deployment blockers and unsupported frameworks. WHEN: "evaluate my repo", "is my app ready to deploy", "what does my app need to deploy", "what do I need before deploying", "does my app need", "can I ship this to Azure", "scan my repo for issues", "is this app deployable", "check if my app is ready for Azure", "do I need a Dockerfile", "what's blocking my deployment", "are there any blockers", "are my dependencies compatible", "does Azure support my framework", "what needs to change before deploying", "check my app configuration".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Reconstruct where you were and what's next after an interruption, so a broken focus doesn't cost you the whole thread. Use when asked where was I, I got interrupted and lost my place, help me pick back up, or I forgot what I was doing. Produces a quick rebuild of the task's state from what you remember (what you'd done, what you were mid-thought on), the single next action to re-enter it, and a 'breadcrumb' habit for next time — cutting the expensive re-immersion cost that interruptions inflict, especially on ADHD brains.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.