'inventory' 검색 결과

Automate advertising campaigns with AI. Create ads, buy media, manage ad budgets, discover ad inventory, run display ads, video ads, CTV campaigns, and optimize ad performance. Perfect for marketing automation, programmatic advertising, media buying, ad management, campaign optimization, creative management, and performance tracking. Launch Facebook ads, Google ads, display advertising, video marketing, and multi-channel campaigns using natural language. Supports ad targeting, audience segmentation, ROI tracking, and automated bidding.

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

Render Aavegotchi assets by deriving renderer hashes from Goldsky Base core data and calling POST /api/renderer/batch on www.aavegotchi.com. Use when the user gives a tokenId or inventory URL, or when deterministic hash plus image artifacts are required.

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

Render Aavegotchi assets by deriving renderer hashes from Goldsky Base core data and calling POST /api/renderer/batch on www.aavegotchi.com. Use when the user gives a tokenId or inventory URL, or when deterministic hash plus image artifacts are required.

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

Locate and summarize Azure resources quickly across scopes using consistent query patterns. Use this skill when users ask where resources are, what they are configured as, or need inventory by type, region, or tag.

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

Guides the practical path from 'we have no design system' or 'we have a mess' to a real, functional design system. Component inventory, design token extraction, headless UI adoption (Radix, React Aria, Headless UI), migration order of operations, and the assessment-to-rollout pipeline. Activate on 'design system from scratch', 'bootstrap design system', 'no design system', 'design system migration', 'headless UI adoption', 'component audit', 'design token extraction', 'design system strategy'. NOT for building specific components once a system exists (use design-system-creator), not for generating token files/configs (use design-system-generator).

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

PRD 到 UI 线框 / 结构阶段：当需要把 PRD 的界面定义先转成 screen inventory、状态模型、ASCII 布局、低保真 HTML mockup， 并先确认结构/状态而不是视觉 polish 时使用。这个 Skill 只负责 UI mockup 的结构阶段；如果用户要高保真、真实前端项目对齐、 project-native preview、component map、implementation notes 或“开发完全复刻”，必须转用 ui-mockup-desktop-workbench。

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

Use an available Codex MCP integration as a read-only second-opinion verifier for GEODE code reviews, GAP audits, and contract checks. Use only when the user requests Codex cross-checking and the current tool inventory exposes the required MCP tools.

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

Manages Pi packages across their lifecycle: discovers, audits, installs, upgrades, removes, enables, disables, filters, and configures extensions, skills, prompts, and themes from npm, Git, or local sources. Use before any Pi package install or upgrade, when reviewing available updates, changing package activation or configuration, or maintaining the package inventory.

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

Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.

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

Deprecated compatibility shim. Agent routing reads the canonical inventory under .codex/agents/ directly; do not use this skill for agent selection.

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

Deprecated compatibility shim. Agent routing reads the canonical inventory under .claude/agents/ directly; do not use this skill for agent selection.

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

Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never commits, never touches consent paths. Disjoint from the commit skill (Phase 11 executor): the planner proposes a split; the executor lands one consented commit. Use when a working tree has accumulated heterogeneous changes that should not land as one commit.

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

Act as a senior Amazon account growth operator that combines Amazon performance-drop analytics, Amazon growth-opportunity analytics, Amazon Ads data, retail readiness, BSR/rank signals, margin, inventory, and campaign/search-term evidence into a prioritized profitable growth action plan. Use when Codex needs to decide what to protect, fix, scale, reduce, pause, harvest, launch, or monitor for an Amazon brand, agency, marketplace, ASIN set, or account; when building daily, weekly, or monthly Amazon account operating plans; when reallocating ad budget; when deciding which ASINs are safe or risky to push; or when turning performance-drop and growth-opportunity findings into approval-gated actions with success/failure criteria.

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

Frontend design heuristics and the loop applying them: existing-ui-audit, brief, inventory, build, review. Use when building or changing any UI, not only when planning one.

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

When the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. 7 phases: interaction, responsiveness, accessibility. Inventory via existing-ui-audit.

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

Audit how a brand is currently expressed across touchpoints and flag drift from its defined tokens, voice, and strategy. Use to inventory and critique an existing brand before changing it.

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

- End-to-end passive reconnaissance for a domain, website or IP — builds an asset inventory covering registration, DNS, subdomains, infrastructure, tech stack, history and ownership without sending a single packet to the target. Use when asked to research or profile a domain or website, map what an organisation runs, or investigate a suspicious site without alerting its operator

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

Close a work session properly: reconcile it against the wider collaboration, inventory what was actually built from git log and recently-touched files, summarize the arc, classify each artifact as keep, one-off or promote-to-permanent, route the durable ones to memory, canon or a new skill, save the retro as a vault note, and hand back an enriched /compact block so working memory shrinks without losing the thread. Triggers: "/retro", "/rr", "wrap up the session".

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

Operating manual for Telegram over its MCP connector and roughly 115 tools: how to find a chat by title, the tool inventory grouped by job, resolving chat ids, auto-transcribing voice notes, and the connector gotchas (pinned-first ordering, big-page crashes, reload after reconnect, untrusted fields, always passing an explicit account). Load before any non-trivial Telegram work.

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

Move entities through containers, hands, slots, storage, equipment, and inventories without corrupting ownership or transforms.

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

Upgrade or synchronize Agent Skills, or determine a Skill's source and ownership across runtimes and roots. Use only for those lifecycle decisions. Do not use for installation, creation or editing, validation, inventory, usage statistics, general audits, cleanup, packaging, publishing, or ordinary file and package work.

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

Scaffold backend API, data models, ORM setup, and endpoint inventory with OpenAPI output.

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

Pre-breach impact analysis: inventories sensitive data (PII, PHI, PCI-DSS, credentials), traces data flows, scores exposure vectors, and produces a regulatory blast radius report with fine ranges sourced verbatim from GDPR Art. 83, CCPA § 1798.155(a), and HIPAA 45 CFR § 160.404. Cost benchmarks from IBM Cost of a Data Breach Report (annually updated). All citations in references/SOURCES.md for verification. Use when asked: "assess breach impact", "what data could be exposed", "calculate blast radius", "data exposure analysis", "how bad would a breach be", "quantify data risk", "sensitive data inventory", "data flow security audit", "pre-breach assessment", "worst-case breach scenario", "breach readiness", "data risk report", "/data-breach-blast-radius". For any stack handling user data, health records, or financial information. Output labels law-sourced figures (exact) vs heuristic estimates (planning only). Does not replace legal counsel.

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

Use when designing scalable MCP tool routing, dynamic tool retrieval, agent-tool graphs, tool inventory indexing, or routing policies for agents with many available tools.

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