'what' 검색 결과

Make a genuinely good drink from the bottles already on your shelf — no special trip, no 12-ingredient recipe. Use when asked what can I make with [spirits], cocktail from what I have, I've got [bottles] what can I drink, or make me a drink without buying anything. Produces two or three cocktails you can build right now with ratios, a method, sensible substitutions for what you're missing, and a zero-proof version — scaled to how many you're making.

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

RAID log methodology with decision extraction from emails and meeting notes. Use when asked to identify risks, log assumptions, track issues, extract decisions from correspondence, create or update a RAID log, escalate a risk to an issue, assess project risks, validate or challenge assumptions, or capture scope-relevant decisions. Also triggers when the user pastes email chains and asks what decisions were made, or needs to find buried decisions and untested assumptions in correspondence. Trigger on: 'risk report', 'RAID log', 'what are the risks', 'what decisions were made', 'update the risk register', 'what assumptions are we making', 'what could go wrong', 'flag any issues', 'extract decisions from these emails'.

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

Build dependency network and critical path from a matter plan. Produce an interactive Gantt, flag near-critical tasks, and run what-if cascade scenarios when delays occur — showing programme impact and drafting communications. Produces filtered workstream or jurisdiction views for local counsel. Trigger on: 'build a timeline', 'Gantt chart', 'critical path', 'what if X is delayed', 'what moves if', 'schedule impact', 'how does this affect the programme', 'when do we finish', 'can we still close on time', 'if we miss this deadline', 'run a what-if', 'visualise the plan', 'Germany timeline', 'what does the Employment workstream look like', 'timeline for local counsel', 'just show me the [workstream] tasks'.

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

Assesses a legal argument, submission, or piece of structured reasoning from the perspective of a judge reading it cold under time pressure. Produces a structured seven-part assessment: what the case appears to be about, immediate points of confusion, what feels strong, what feels weak, what is assumed but unproved, a provisional confidence level (low/medium/high), and what would be needed to persuade. The skill does not rewrite, improve, or attack the argument — it tells you how it actually lands on a sceptical, experienced reader with no prior context. Works on skeleton arguments, witness statements, letters before action, position statements, academic articles, and non-legal structured reasoning.

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

Capture, structure, and recycle lessons from active and closed legal matters. Three modes: in-flight capture (triggered by scope changes, risk events, status updates — highest value), mid-matter review (phase gates or quarterly), and matter close retrospective (full structured findings). Lessons are formatted for immediate reuse, not filed and forgotten. Use when a risk materialises, a scope change lands, a phase completes, or a matter closes and you want to convert what happened into something useful for the next matter. Trigger on: 'capture a lesson', 'what did we learn', 'matter close', 'retrospective', 'lessons learned', 'what went wrong', 'what worked', 'phase gate review', 'debrief', 'extract the learning', 'close the matter', 'what should we do differently', 'pattern from this matter', 'improve the next one'.

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

Trending products and rising categories discovery for Amazon sellers. Analyzes Best Seller Rank patterns, seasonal trends, new release momentum, and emerging niches. Identifies product opportunities before they peak. Use when the user asks about what's trending on Amazon, hot products, rising categories, seasonal opportunities, viral products, what to sell next, emerging niches, or early-mover opportunities. Also trigger for questions like 'what should I sell now?', 'what products are doing well?', 'find me trending niches', or 'what's hot on Amazon?'.

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

Reverse-engineer successful affiliate strategies from competitors. Use this skill when the user asks about spying on competitors, researching what other affiliates promote, analyzing competitor affiliate sites, understanding how top affiliates in a niche make money, or says "what programs does X promote", "how does [site] make money", "what affiliate strategy does this site use", "spy on competitor affiliates", "reverse engineer affiliate site", "copy what works in my niche", "who are the top affiliates in X niche", "what content gets traffic in my niche", "competitor affiliate analysis".

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

Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live numbers mid-flight, see `03-performance-eval-global`; the next period ads plan, see `57-next-ads-plan-global`.

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

Give the owner one page when they come back from sleep, a meeting or a long run: what got done, what is stuck, what waits for their answer, and what it cost in quota. Use when the owner asks what happened while they were away, wants a status page, or when you finish a long stretch of work and must report it.

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

Query and answer questions about Volcengine API specifications. Trigger this skill whenever a user asks about Volcengine API parameters, error codes, request methods, enum values, required fields, response structures, pagination, parameter dependencies, or API comparisons — even if they don't explicitly say "API". Typical triggers include questions like "What parameters does DescribeInstances have?", "What values does Status support?", "What does InvalidInstanceId.NotFound mean?", "Does Volcengine have a batch tag deletion API?", "Which APIs does ECS support?", "How do I pass parameters to CreateDatabase?", "Is ChargeType required?", "What fields does DescribeInstances return?", "How do I paginate instance lists?", "What's the difference between these two APIs?", "RunInstances returns InvalidParameterValue". When the user needs runnable SDK code, hand off to the volcengine-sdk-generator skill. When the user needs CLI-based operations, hand off to the volcengine-cli skill. Supports both Chinese and English prompts.

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

The telemetry each Active Directory technique generates and what alerts a defender: Kerberoasting produces Event 4769 with RC4 encryption (0x17) and an MDI alert, DCSync produces Event 4662 with the DS-Replication-Get-Changes GUID, AS-REP roasting produces Event 4768 with no pre-auth, LSASS dumping is blocked by EDR, plus a lateral-movement telemetry table by protocol (SMB/WMI/WinRM/RDP/DCOM). Use this whenever you run or plan an offensive AD technique and need to know what noise it makes, when writing the engagement's detection notes, or when a defender wants to know what to monitor. Teaches red teamers what is loud and blue teamers what to watch. Standard-tooling knowledge, no vendor engine.

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

Write correct Python code with the official GREEN-API SDK whatsapp-api-client-python (package whatsapp_api_client_python). Use when sending/receiving WhatsApp messages, files, polls, groups, journals, queues, statuses, contacts, partner instances, polling notifications, or configuring a GREEN-API instance in Python. Triggers: GREEN-API, green-api, whatsapp-api-client-python, GreenAPI, GreenApi, sendMessage, receiveNotification.

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

Symbol-level navigation of a local checkout using tree-sitter ASTs. Answers where a symbol is defined, what lines it spans, which symbols a file exposes, what a directory holds, and where a name is referenced — every answer carries exact line ranges to feed straight into a scoped read. Use for "where is X defined", "who calls X", "find the function/class named", "what's in this file", "give me the line range for", "show me the source of", "list the symbols in", or before editing a file you have not read. Each invocation auto-scans and is self-contained. Not for first-encounter repo orientation (use exploring-codebases), for what a codebase DOES rather than what it contains (featuring), for binding-resolved Python caller sets (searching-codebases), or for literal text and regex matching (plain ripgrep).

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

Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to do

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

Scout the TouchDesigner community for what's HYPED right now — community showcases, recent tutorials, generative-AI bridges, hardware interaction trends, visual-aesthetic trends of 2025-2026 — then propose tdmcp tools that ride those trends AND are easy to build. Use whenever the user wants to brainstorm new feature ideas based on what's trending in TouchDesigner, asks for 'hype' or 'trending' features, asks 'what are people doing in TD right now / what's hot / what's hype', wants tools inspired by community trends, asks to scout TD trends/aesthetics/integrations, or says things like 'ideias hype', 'novas ideias', 'o que está em alta', 'criar ferramentas para o que está bombando', 'tendências do TouchDesigner'. Also for follow-ups: refresh, rescout one surface, re-rank under another profile, deepen a trend, or filter for buildable-easy items. This is an EXTERNAL trend ideation harness — complementary to tdmcp-feature-discovery (which is INTERNAL gap analysis). It produces `_workspace/hype-scout/HYPE_TOOL_BACKLOG.md` ranked by Hype × Build-Ease; it does NOT build. Once a feature is chosen from the backlog, hand it to tdmcp-pipeline.

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

Use when the user asks a question about how things in the codebase or wiki relate — what connects two things, how something works end to end, what depends on what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with source-location citations. Trigger on "/graph-query", "ask the graph", "what connects X to Y", "trace how X works", "explain <concept> from the graph", "shortest path between".

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

Use this skill when the user wants the full existing-registry Trust Magnitude inspector: understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".

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

Use this skill when the user wants to understand why a named Gaia skill has a particular star rank, what its Trust Magnitude (TM) score is, which evidence rows are contributing (or dead), how far it is from the next grade, or what evidence to add to move the needle. Also use when asked for a full leaderboard of all named skills ranked by TM. Triggers: "why does X have 3 stars", "what's the TM for X", "inspect TM", "explain the score for X", "what evidence would rank up X", "show leaderboard", "rank all skills by TM", "what's dragging down X's score", "dead evidence rows", "how close is X to grade A/S".

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

Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now or I'm stuck or I don't know what to do

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

Search an index built for coding agents — GitHub issues, merged pull requests, repository READMEs, and curated documentation sites — and get back the matched passages, not just links. Use this skill whenever the question is about code: how a library, framework, or API behaves, what an error message or stack trace means, whether a bug was reported or fixed, what a function returns, what a default is, or which repos do a given thing. Triggers on "why does <library> do X", "what does this error mean", "is this a known bug", "how do I use <library>", "what's the API for", pasted stack traces, and pasted error strings. Prefer this over a general web search for programming questions — it answers from the primary source instead of a blog post about it.

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

Produce a weekly digest of what Ahmad saved in OpenMark over a given time window, clustered by topic. Use whenever Ahmad asks "what did I save this week", "what's new in OpenMark", "last week's saves", "this week's bookmarks", "what happened in my feed", "weekly recap", or any temporal summary of saved content. Faster than full newsletter — output is a scannable digest, not a published post. Triggers on "this week", "last week", "what's new", "weekly digest", "recent saves", "recap".

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

Prepares a DRAFT vendor risk screening brief from the material the user provides on one vendor (questionnaire answers, certificates, assurance reports, policies, contract extracts): per screening topic, what a document evidences with reference, date and scope, what is only asserted, what is missing or contradicted, certificate and report details as stated, and ready-to-send questions for the vendor and the internal owners. No web research, no risk rating, tier, score or recommendation. Use when the user asks to "screen this vendor", "review the vendor's questionnaire answers", "check what the vendor's certificate covers", "what is missing from this due diligence pack" or "draft the follow-up questions for the vendor". Do not use for answering a customer's questionnaire about your own organisation, use vendor-security-questionnaire-prefill instead. Drafts for human review; never approves, authorises or signs off.

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

Prepares a discovery call brief from what the user has on a prospect (CRM record, inbound form, emails, notes, public material the user supplies): what is known with sources, gaps against the qualification dimensions, hypotheses to test, questions in priority order and what to listen for. Returns a DRAFT Markdown brief in the chat. Use when the user asks to "prep me for the discovery call with <prospect>", "what should I ask on this first call", "intro call brief", "questions for the qualification call" or "what do we know before we speak to them". Do not use for scoring leads against a rubric, use lead-qualification-scorer instead; for an existing customer's account review use account-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Plan the first months at a new Japanese employer after an offer is accepted, listing every expectation and promise made in interviews, the offer, or negotiation with its source, separating what is in writing from what was only said and what has no agreed measure, working out when the probation period ends and whether its criteria and conditions are known, and scheduling who to confirm what with before and after the start date. Use when a user has accepted an offer and wants to prepare for joining, make sure verbal promises such as remote days or a future role are confirmed, or understand what the probation period means for them; do not use to predict whether they will fit in or pass probation, to judge their manager or colleagues, to rule on the legality of probation terms, or to contact the new employer.

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