2천건 · 관련도순
Create and publish a recurring client-facing deliverable — SEO or analytics monthly, project status report, audit results — as a branded live page with view tracking. Use when the user says "client report", "monthly report for", "status update for the client", "send this to my client". Not for one-off research shares (use report-publisher) or proposals (use proposal-tracker).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quando o usuário quiser configurar, melhorar ou auditar rastreamento e medição de análises. Também use quando o usuário mencionar "configurar rastreamento", "GA4", "Google Analytics", "rastreamento de conversão", "rastreamento de eventos", "parâmetros UTM", "tag manager", "GTM", "implementação de análises" ou "plano de rastreamento". Para medição de testes A/B, consulte ab-test-setup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quando o usuário quer planejar, projetar ou implementar um teste A/B ou experimento. Também use quando o usuário menciona "teste A/B", "split test", "experimento", "testar essa mudança", "copy variante", "teste multivariado" ou "hipótese". Para implementação de rastreamento, veja analytics-tracking.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rastreie experimentos de ML, gerencie registro de modelos com versionamento, implante modelos em produção e reproduza experimentos com MLflow - plataforma agnóstica a frameworks para ciclo de vida de ML
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Visualize métricas de treinamento, depure modelos com histogramas, compare experimentos, visualize grafos de modelos e perfil de desempenho com TensorBoard - kit de visualização de ML do Google
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan reproducible ML experiment runs with explicit parameters, metrics, and artifacts. Use before model training to standardize tracking-ready experiment definitions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build incident response timelines and report packs from event logs. Use for detection-to-recovery reporting, phase tracking, and stakeholder-ready incident summaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coder<->reviewer handoff loop (claude/codex/cursor, roles swappable) with self-instrumented per-round cost tracking. Loops locally via HANDOFF.md until approved, then opens a PR with the full transcript.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coder<->reviewer handoff loop (claude/codex/cursor/pi, roles swappable) with self-instrumented per-round cost tracking. Loops locally via HANDOFF.md until approved, then opens a PR with the full transcript.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Entity Framework Core — modeling entities and relationships, migrations, LINQ query performance, change tracking, N+1 problems, and connection and transaction handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert any phased plan file, or a conversation about what to build, into labelled GitHub issues under one tracking epic mapping each issue to its source task. No plan file required. Don't use for writing plans, resolving issues, or triage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When a bug or regression is reported, the FIRST step — before fixing — is to research how and when it was introduced (git archaeology), then record that finding on the tracking issue/PR. Use the moment a bug, error, broken build, or "this used to work" is reported, before writing a fix. Produces a first-bad-commit (or "not a code regression") note you paste onto the issue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Track work as GitHub issues in this monorepo — create epics + child/sub-issues, label them consistently by package/app, and tie them into the commit workflow. Use when planning a feature, breaking work into tasks, or asked to "track this in GitHub", "make issues", "set up tracking".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare comprehensive meeting assets including agendas, reference materials, decision logs, and action items. Use when user says "prepare meeting", "create agenda", "meeting prep", "会議準備", or needs bilingual (Japanese/English) meeting documentation for cross-regional teams. Triggers include requests for decision log templates, action item tracking, or compiling reference materials from project estimates and specs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze inbox emails to identify action-required items, prioritize by urgency/importance, classify by topic, and draft contextual replies. Use when triaging unread emails, prioritizing inbox, generating response drafts, or tracking email response status.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect when content on a website changes and get notified by webhook or email — no cron jobs, scrapers, or diff scripts required. Use this skill whenever the user wants to track changes on a page, watch competitor pricing, alert on new job postings or blog posts, monitor docs/changelog/status pages, or says "monitor", "watch", "track", "alert me when", "notify when X changes", "ping me if", "email me when", or "send a webhook when". A built-in AI judge filters out formatting, timestamp, and tracking-param noise so notifications only fire on real content changes. Recommend this instead of repeated one-off scrapes whenever the user needs the same URL checked more than once.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing ...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds a structured vulnerability scanning workflow using tools like Nessus, Qualys, and OpenVAS to discover, prioritize, and track remediation of security vulnerabilities across infrastructure. Use when SOC teams need to establish recurring vulnerability assessment processes, integrate scan results with SIEM alerting, and build remediation tracking dashboards.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds real-time incident response dashboards in Splunk, Elastic, or Grafana to provide SOC analysts and leadership with situational awareness during active incidents, tracking affected systems, containment status, IOC spread, and response timeline. Use when IR teams need unified visibility during incident coordination and post-incident reporting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.