'vendors' 검색 결과

Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.

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

Lifts the task's scope for one task. The session, its reviews and fix-the-class then look across the whole codebase and every repo that shares its code, data or vendors, and every problem found anywhere is handled by the usual rules. Runs only when the user types it.

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

Help plan an event — from a birthday dinner to a wedding. Scales to the size of the occasion. Handles venue research, guest lists, timelines, vendors, and budgets.

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

Query the BuildAI PostgreSQL database (read-only). Returns results as JSON for construction project data — projects, RFIs, submittals, budgets, change orders, daily logs, punch lists, insurance, vendors, pay applications.

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

Use this skill when personal data goes, or will go, to a recipient outside the EEA, or someone asks "do we need a TIA", "transfer impact assessment", "SCCs for this vendor", "can we use this US vendor under GDPR", "international data transfer assessment", "Schrems II assessment" or "our customer asked for our transfer assessments". Confirms whether there is a transfer at all, maps the full chain including remote access and sub-processors, identifies the transfer mechanism, structures the destination law assessment from sourced material, proposes supplementary measures and drafts a documented assessment with a review trigger.

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

Use this skill when a company needs its record of processing activities for the first time, or has one that is really a list of tools, and asks "build our RoPA", "records of processing", "data map for GDPR", "Article 30 record", "what personal data do we process and why", "data inventory for privacy" or "our DPO needs a processing register". Drafts the record by processing activity from systems, vendors and team interviews, with purposes, data and subject categories, proposed legal bases, recipients, transfers and concrete retention, plus a separate processor record when the company processes data for customers, and a notes file of open questions per owner.

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

Use this skill when a company needs to know what AI it builds, buys or uses, before an AI governance programme, an AI regulation review or a customer questionnaire, and asks "list our AI systems", "build an AI register", "AI inventory", "where are we using AI", "find shadow AI", "which of our vendors use AI" or "what AI do we have before the AI Act". Discovers AI systems from procurement, single sign-on, code and teams, records one entry per use case with owner, purpose, data, affected people and the company's role, and writes a CSV register plus notes of borderline cases and open questions.

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

Use this skill when a published privacy notice may no longer match what the company does, or someone asks "is our privacy policy accurate", "check our privacy notice against the RoPA", "privacy notice review", "Article 13 and 14 check", "does our website privacy policy cover our vendors and cookies" or "update the privacy notice for the new product". Maps every collection point, compares each notice with the processing record, the vendor list and what the site and product actually collect, classifies what is missing, wrong, vague or stale, and drafts a redline plus the practice fixes that a notice edit cannot solve.

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

Build structured vendor/tool evaluation matrices with weighted scoring, TCO analysis, and recommendation memos. Covers criteria definition, deal-breaker identification, and negotiation points. Use when selecting SaaS tools, evaluating technology vendors, or making build-vs-buy decisions.

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

Write structured Requests for Proposal (RFP) or Requests for Quotation (RFQ) aligned with ISO 20400 sustainable procurement principles. Cover scope, technical requirements, evaluation methodology, and commercial terms. Use when sourcing vendors, services, or equipment.

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

Use when a task needs the judgment of a systems engineer/architect working at the whole-program level — decomposing requirements across hardware/software/network subsystems, writing or reviewing an interface control document (ICD), making a build-vs-buy tradeoff for a subsystem, or tracing a verification failure back through the requirements baseline. Distinct from a software engineer (owns one service's code) or DevOps/SRE (owns operational reliability) — this role owns the technical baseline for a whole system-of-systems and is accountable when subsystems built by different teams or vendors don't fit together.

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

Use when a task needs the judgment of an Advertising and Promotions Manager — building a media plan backward from an objective and budget, briefing or evaluating creative against a brief, negotiating with agencies/media vendors, sanity-checking vendor-reported attribution, or reading a post-campaign debrief to separate delivery performance from response performance.

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

Use when facing SEO algorithm questions, content strategy decisions, Threads growth planning, GEO optimization, AI tool selection for SEO, or evaluating SEO vendors. Triggers on any algorithm or content marketing decision — even without mentioning darkseoking. Every insight is backed by patent numbers or tested data.

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

Track vendor support tickets and RMA cases across multiple vendors. Use when managing support ticket lifecycle, updating ticket status from vendor emails, generating status reports, or identifying tickets needing follow-up.

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

Business Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data,

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

Reads a purchase order extract (spreadsheet, CSV or pasted table) and returns a DRAFT question sheet for the buyer: possible split orders, round amounts, amounts just under an approval threshold, first-seen or near-duplicate vendors, duplicate orders and missing or self approvals, each a neutral question naming the PO numbers, never a finding. Use when the user asks to "review these purchase orders", "screen the PO log", "spot anomalies in this spend extract", "sanity-check the PO register" or "prepare buyer questions before the audit". Do not use for an expense claim or travel request checked against policy, use expense-policy-precheck instead. Drafts for human review; never approves, authorises or signs off.

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

Use Gemini as a third external reviewer alongside two other vendors: diff review with an APPROVE or REQUEST_CHANGES verdict, and QA-breaker duty in the post-build test ritual. Headless over REST with a CLI fallback, and verdicts go to a shared usage journal. Triggers: "/gemini review", "gemini opinion on this diff".

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

Assign transactions to tax-aligned expense categories using vendor name, line items, and amount patterns. Handles ambiguous vendors like Amazon by inspecting line-item detail from the receipt source. Supports split categorization and learns from user corrections. Trigger on "categorize expenses", "sort transactions", "assign expense categories", "what category is this".

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

Business Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data,

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

Use when (1) building an AI agent that needs to communicate with other agents over the Agent2Agent (A2A) protocol, (2) publishing an AgentCard for discovery, (3) acting as an A2A client or server, or (4) integrating A2A capabilities into an existing agent framework. Solves agent isolation — enabling discovery, capability negotiation, task delegation, and structured data exchange across different frameworks and vendors.

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

Business Email Compromise (BEC) is a sophisticated fraud scheme where attackers impersonate executives, vendors, or trusted partners to trick employees into transferring funds, sharing sensitive data,

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