543건 · 관련도순
Assess potential data breach impact by reviewing sensitive data and its movement through a codebase. Produce an inventory, exposure rankings, financial estimates, and prioritized safeguards, distinguishing legal source figures from planning estimates.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review every project in a .NET solution for Oracle dependencies, classify its migration status, and create a saved PostgreSQL migration plan with a project inventory and an order that prioritizes shared libraries.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find undocumented API endpoints, the addresses applications send requests to, by comparing traffic with OpenAPI specifications and examining cloud settings and source code. Build an inventory with activity and risk details to review forgotten or outdated APIs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build an AI system register for EU AI Act reviews. Track owners, deployment status, EU connections, and each system’s role and risk category through a guided discussion, preserving classification reasons and dates for future review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage a project's stored materials through inventory, migration, archiving, and ranking based on verified source reads. Changes follow owner approval, preserve material references, and include validation records and rollback procedures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inventory old and undocumented API versions, then compare their authentication, request limits, input validation, and exposed fields with current versions. Uses API specifications and archived records to identify overlooked endpoints with weaker security controls.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Full inventory and audit of AWS Glue Data Catalog assets across S3 Tables, Redshift-federated, and remote Iceberg catalogs. Triggers on: inventory the catalog, audit databases, list all tables, catalog overview, data landscape, enumerate catalogs, data inventory, search the catalog. Do NOT use for finding specific data (use finding-data-lake-assets), running queries (use querying-data-lake), or creating tables (use creating-data-lake-table).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
KubeKey (kk) Usage Guide. For Kubernetes cluster lifecycle management including creation, scaling and deletion. Use this skill whenever the user mentions kubekey, kk commands, cluster setup, cluster management, adding nodes, deleting nodes, creating inventory files, configuring clusters, installing Kubernetes, or deploying K8s. Also use this skill when the user asks about inventory.yaml, config.yaml formats, CNI configuration, container runtime setup, offline installation, or artifact operations. Provides detailed guidance on kk subcommand usage, config file formats, inventory structure and common workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interview someone about their working life and turn the answers into a master CV inventory: every role, project and achievement with real numbers, before any CV is tailored. Use when asked to build my master CV, get my experience down properly, I don't know what to put on my CV, or as the first step before a tailored CV. Produces a structured inventory of roles, achievements in a fixed shape with evidence and numbers, skills with proof, and a list of gaps to fill. Never invents a number.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
E-commerce warehouse and inventory optimization advisor. Analyzes inventory health, calculates safety stock and reorder points, performs ABC analysis, evaluates fulfillment costs, and provides actionable recommendations for improving efficiency. Supports all major fulfillment models: Self-fulfillment, Amazon FBA/FBM, Walmart WFS, 3PL, Shopify Fulfillment, TikTok Shop, Dropshipping, and Hybrid setups. No API key required. Use when: (1) reducing stockouts or overstock, (2) calculating safety stock levels, (3) optimizing warehouse costs, (4) improving Amazon IPI score, (5) analyzing inventory KPIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert blueprint for inventory systems (Diablo, Resident Evil, Minecraft) covering slot-based containers, stacking logic, weight limits, equipment systems, and drag-drop UI. Use when building RPG inventories, survival item management, or loot systems. Keywords inventory, slot, stack, equipment, crafting, item, Resource, drag-drop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert blueprint for inventory systems (Diablo, Resident Evil, Minecraft) covering slot-based containers, stacking logic, weight limits, equipment systems, and drag-drop UI. Use when building RPG inventories, survival item management, or loot systems. Keywords inventory, slot, stack, equipment, crafting, item, Resource, drag-drop.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
FBA inventory planning — restock timing, safety stock, IPI score optimization, stranded inventory recovery
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides systematic mapping of international personal data flows across an organisation. Covers system-by-system inventory methodology, third-party identification, transfer mechanism assignment, gap analysis, and data flow visualisation. Keywords: data flow mapping, international transfers, data inventory, transfer register, cross-border data flows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Organize, track, and value a trading card game collection. Covers inventory methods, storage best practices, grade-based valuation, want-list management, and collection analytics for Pokemon, MTG, Flesh and Blood, and Kayou cards. Use when starting a new collection and setting up inventory tracking, cataloging an existing collection that has grown beyond casual knowledge, valuing a collection for insurance or sale, or deciding which cards to submit for professional grading based on value potential.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build AI inventory prediction. TRIGGERS - Use when user needs help with ai-inventory-predictor related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build AI inventory optimization systems. TRIGGERS - Use when user needs help with ai-inventory-optimizer related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze an inventory allocation system for demand-driven distribution accuracy, store clustering methodology, safety stock optimization, markdown timing, replenishment logic, and omnichannel inventory visibility..
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a BA or admin needs to document the Salesforce data model: creating field inventories, object relationship maps, ER diagrams, or analyzing field usage across objects. Triggers: 'data dictionary', 'document our data model', 'object relationship map', 'field inventory', 'ER diagram for Salesforce'. NOT for designing the model or choosing lookup vs master-detail — use data/data-model-design-patterns. NOT for generating the Mermaid or PlantUML diagram — use architect/salesforce-erd-and-diagramming. More trigger keywords: field inventory CSV, describe API, getGlobalDescribe, DescribeFieldResult, sObject describe, schema snapshot, schema drift, blank field descriptions, undocumented fields, field ownership, data dictionary review cadence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepares a DRAFT data incident impact brief from the incident notes and data inventory the user provides: the timeline as stated, systems involved matched to the inventory, data categories held and evidenced as involved, people and record counts potentially affected with the source and method behind every figure, third parties, notification questions for legal and the data protection officer, and every UNKNOWN with the evidence that would settle it. No legal determination: it never states whether the incident is a reportable breach, whether notice is due, to whom or by when. Use when the user asks to "prepare the impact brief for this incident", "what data was involved", "how many people are affected", "map the incident to our data inventory" or "pull together what legal needs on the incident". Do not use for the blameless postmortem or root-cause timeline, use incident-postmortem-drafter instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
set_inventory ツールの使い方。チェスト、ホッパー、ドロッパー等にアイテムをセットする前に読む。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CLI版 mc-cli set-inventory コマンドの使い方。チェスト、ホッパー、ドロッパー等にアイテムをセットする前に読む。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform comprehensive cloud asset inventory and relationship mapping using Cartography to build a Neo4j security graph of infrastructure assets, IAM permissions, and attack paths across AWS, GCP, and Azure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.