543건 · 관련도순
Use when working with Aws S3 — aWS S3 bucket analysis, storage class distribution, lifecycle policies, access patterns, and cost optimization. Covers bucket inventory, object metrics, versioning status, encryption audit, public access analysis, and intelligent tiering evaluation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Transit Gateway — aWS Transit Gateway attachment analysis, route table management, peering configuration, and network topology review. Covers TGW inventory, attachment health, route propagation, VPN connection status, and bandwidth utilization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Secrets Manager — aWS Secrets Manager secret rotation status, access analysis, cost tracking, and lifecycle management. Covers secret inventory, rotation configuration audit, last access tracking, resource policy review, and version management.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Cloudwatch Logs — aWS CloudWatch Logs group management, Logs Insights query execution, metric filter analysis, retention policy review, and subscription filter management. Covers log group inventory, storage cost optimization, query patterns, and cross-account log aggregation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Aws Cloudfront — aWS CloudFront distribution analysis, cache hit ratio monitoring, origin health checks, invalidation management, and performance optimization. Covers distribution inventory, behavior configuration, SSL certificate status, geo-restriction, and real-time metrics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with AWS API Gateway — analyzing REST or HTTP APIs, debugging latency or 5xx errors, auditing throttling and stage configuration, reviewing usage plans, or checking authorization setup. Covers API inventory, CloudWatch metrics, stage audits, and integration health for both REST (v1) and HTTP (v2) APIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Wiz — wiz cloud security posture management. Covers cloud security posture analysis, vulnerability prioritization, attack path analysis, compliance assessment, container security, and resource inventory. Use when assessing cloud security posture, investigating attack paths, prioritizing vulnerabilities, or auditing cloud compliance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Survey one surface of tdmcp (artist controls, library/packaging, CLI/DX, AI/LLM, or TouchDesigner depth) for candidate NEW features — inventory what exists, cross-check the roadmap, apply the gap-finding lenses, vet each idea, and emit a structured, novelty- and confidence-labelled candidate list to _workspace/discovery/. Use when a td-surveyor agent is scouting a surface during the feature-discovery harness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assesses organizational readiness for post-quantum cryptography migration per NIST FIPS 203/204/205 standards. Performs cryptographic inventory scanning to identify quantum-vulnerable algorithms (RSA, ECDH, ECDSA), evaluates hybrid TLS configurations with X25519MLKEM768, and validates CRYSTALS-Kyber (ML-KEM) and CRYSTALS-Dilithium (ML-DSA) readiness. Implements crypto-agility assessment using oqs-provider for OpenSSL. Use planning yaparken or executing the transition from classical to post-quantu...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement API Security Posture Management to continuously discover, classify, and score APIs based on risk while enforcing security policies across the API lifecycle.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lightweight contract lifecycle management App-in-Skill (Busabase App-in-Skill) for contract inventory, lifecycle status, owners, obligations, renewal notices, and simple approval reminders. Use when the user invokes $kelly-clm or /kelly-clm, mentions CLM, contract lifecycle management, 合同管理, 合同台账, contract repository, obligation tracking, renewal reminders, notice deadlines, contract owners, signature readiness, or wants a simple UI to review contract status without doing detailed legal redlines.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Focused Signals scout for finding observability gaps in PostHog itself — significant event volumes the team isn't tracking, custom events with no insight or dashboard coverage, insights pointing at events that have stopped firing, dashboards missing related context, critical events with no alerts. Watches the event-stream-vs-saved- inventory delta as the team's product evolves and emits findings recommending new insights, dashboard additions, or alerts when gaps clear the confidence bar. Self-contained peer in the signals-scout-* fleet — no dependencies on other skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review and revise Japanese job-application documents (entry sheets, rirekisho, shokumu-keirekisho) by checking each answer against the question asked, the stated character limit, and the evidence the applicant can actually support, then propose concrete rewrites the applicant decides on. Use when a user wants an ES or resume answer critiqued, tightened, or drafted from their own experience; to assemble a whole shokumu-keirekisho from an experience inventory, use resume-draft instead; do not use to invent experience, to judge pass or fail probability, or to submit an application.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assemble a Japanese shokumu-keirekisho (career history document) from an experience inventory, choosing between reverse-chronological, chronological, and skills-based layouts, mapping the target posting's requirements to the experiences that can support them, and drafting the summary, work history, skills, and self-PR so that each sentence stays within what its evidence supports and confidential details are abstracted. Use when a user wants to write or rebuild a whole shokumu-keirekisho for a specific posting or as a general version, or wants to decide which experiences to include and in what order; do not use to invent experience, numbers, titles, or qualifications, to predict whether it will pass screening, to fill in a rirekisho form, or to submit it anywhere.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map owned assets, attack surface, and inventory for systems the requester is authorized to assess. Use for asset discovery, service catalogs, and exposure reviews — never unauthorized scanning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inventory staged local EcoSIM data at project startup and validate input readiness for a selected site, simulation period, and preprocessing or analysis workflow. Use before data-dependent work or when relevant inputs change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Independent quality assurance for one SDD Composy task in qa_required: CA coverage, unit/integration/E2E, accessibility, responsiveness, environment, and evidence inventory, producing the QA report and requesting evidence_required. Use when a task finished execution — 'rodar o QA da task', 'testar a TASK-003', 'validar a implementação'. Do NOT use for code review (sdd-review), the final verdict (sdd-verify), or test runs outside an SDD task.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inventory, archive, and summarize PWDEV Flow project history safely. Use when the user asks to find stale artifacts, archive completed work, clean the Flow workspace without deletion, or generate a changelog from verified history.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Crawl an existing website (capped, multi-page) and seed stardust/current/ with PRODUCT.md, DESIGN.md, DESIGN.json, a per-page inventory, and the consolidated brand surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply DESIGN, canon, and modules to every page in the inventory, producing a deployable static HTML site. Three render branches (approved page, template-applied sibling, unique render). Per-page, incremental, idempotent, content-preserving by default.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.