'logging' 검색 결과

Checks structured logging, health check endpoints, metrics collection, request tracing, log levels. Returns findings with severity, location, effort, recommendations.

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

A-share short-term trading decision skill for 1-5 day horizon. Use when you need real-data market sentiment, sector rotation, strong stock scanning, capital flow confirmation, date-based short-term signal scoring, prediction logging, and next-day market comparison for CN A-share momentum trading.

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

Internal utility for the skills library itself — opt-in, local-first, privacy-respecting usage telemetry and update checks. Provides version checking, usage logging, and usage reporting for the skills in this repo. Use only when asked to view skill usage stats, configure telemetry opt-in/out, wire a skill to log its own runs, or check for skill updates.

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

Production-grade error handling for Node.js/TypeScript backends. Error classes, HTTP mapping, logging, retry strategies.

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

Instrument applications with Azure Application Insights and OpenTelemetry for end-to-end observability. Use this skill when users ask about telemetry, tracing, metrics, logging, or monitoring setup. Covers SDK setup, correlation, sampling, dashboards, and alerts per OpenTelemetry standards.

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

Ensure HIPAA compliance when handling PHI (Protected Health Information). Use when writing code that accesses user health data, check-ins, journal entries, or any sensitive information. Activates for audit logging, data access, security events, and compliance questions.

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

Expert in developer tool documentation as a product. Activate on: docs site, getting started guide, API reference, developer documentation, Docusaurus, Mintlify, Nextra, ReadMe, migration guide, troubleshooting page, docs information architecture, documentation testing, llms.txt. NOT for: marketing copy (use seo-content-blogging), API design itself (use api-architect), general technical writing (use technical-writer).

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

Traces complete execution paths through DAG workflows. Records timing, inputs, outputs, and state transitions for all nodes. Activate on 'execution trace', 'trace execution', 'execution path', 'debug execution', 'execution log'. NOT for performance analysis (use dag-performance-profiler) or failure investigation (use dag-failure-analyzer).

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

Build daemon/background processes that start on boot, run continuously, and manage their own lifecycle. Covers macOS launchd (plist files, agents vs daemons), Linux systemd (unit files), Windows services, process supervision, logging, health checks, graceful shutdown, auto-restart, and AI-powered daemons that manage LLM API connections and rate limits. Activate on: "daemon", "background process", "launchd", "systemd", "service file", "plist", "launch agent", "launch daemon", "auto-start", "always running", "process supervisor", "pm2", "background service", "boot service", "AI daemon", "long-running process". NOT for: container orchestration (use devops-automator), cron jobs that run and exit (use task-scheduler), web server deployment (use backend-architect).

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

GEODE CHANGELOG.md management rules. Version releases, change logging, scope determination, format standards. Triggers on "changelog", "release", "version", "릴리스", "변경사항", "버전".

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

JIRA issue CRUD via the jira-as wrapper. Triggers: 'create bug/task/story', 'show me PROJ-123', 'get/view/look up issue', 'update PROJ-123', 'delete PROJ-123'. NOT for transitions (mk:jira-lifecycle); NOT for comments/attachments (mk:jira-collaborate); NOT for bulk ops (mk:jira-bulk); NOT for issue links (mk:jira-relationships); NOT for time logging (mk:jira-time); NOT for sprint/epic (mk:jira-agile).

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

Use when adding logging, metrics, tracing, or alerting to production code, or when a past incident lacks diagnostic data.

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

Use when establishing what observability a project actually has — the four Golden Signals, required signal to detected implementation to evidence, and SLI/SLO provenance.

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

Error handling review — silent failure detection, catch block analysis, error logging.

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

Error handling review — silent failure detection, catch block analysis, error logging.

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

Add useful diagnostics, choose log levels, preserve context, and handle player-facing failures safely.

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

Rastreie experimentos de ML com logging automático, visualize treinamento em tempo real, otimize hiperparâmetros com sweeps e gerencie registro de modelos com W&B - plataforma colaborativa de MLOps

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

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

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

Instruments a web app to send telemetry to Azure Application Insights: SDK setup, configuration, and telemetry patterns. Use when the user wants to enable monitoring, request tracking, or logging to App Insights for a web application.

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

Two-layer memory architecture for board meeting decisions. Manages raw transcripts (Layer 1) and approved decisions (Layer 2). Use when logging decisions after a board meeting, reviewing past decisions with /cs:decisions, or checking overdue action items with /cs:review. Invoked automatically by the board-meeting skill after Phase 5 founder approval.

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

Apply GDPR-compliant engineering practices across your codebase. Use this skill whenever you are designing APIs, writing data models, building authentication flows, implementing logging, handling user data, writing retention/deletion jobs, designing cloud infrastructure, or reviewing pull requests for privacy compliance. Trigger this skill for any task involving personal data, user accounts, cookies, analytics, emails, audit logs, encryption, pseudonymization, anonymization, data exports, breach response, CI/CD pipelines that process real data, or any question framed as "is this GDPR-compliant?". Inspired by CNIL developer guidance and GDPR Articles 5, 25, 32, 33, 35.

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

Use when logging, scoring, and triaging a learner's persistent weak areas to drive intervention selection.

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

Control and interact with a live browser session on any scraped page — click buttons, fill forms, navigate flows, and extract data using natural language prompts or code. Use when the user needs to interact with a webpage beyond simple scraping: logging into a site, submitting forms, clicking through pagination, handling infinite scroll, navigating multi-step checkout or wizard flows, or when a regular scrape failed because content is behind JavaScript interaction. Also useful for authenticated scraping via profiles. Triggers on "interact", "click", "fill out the form", "log in to", "sign in", "submit", "paginated", "next page", "infinite scroll", "interact with the page", "navigate to", "open a session", or "scrape failed".

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

Detecting misconfigured Azure Storage accounts including publicly accessible blob containers, missing encryption settings, overly permissive SAS tokens, disabled logging, and network access violations using Azure CLI, PowerShell, and Microsoft Defender for Storage.

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