'issues' 검색 결과

Audit MCP (Model Context Protocol) server configurations for security issues. Use this skill when: - Reviewing .mcp.json files for security risks - Checking MCP server args for hardcoded secrets or shell injection patterns - Validating that MCP servers use pinned versions (not @latest) - Detecting unpinned dependencies in MCP server configurations - Auditing which MCP servers a project registers and whether they're on an approved list - Checking for environment variable usage vs. hardcoded credentials in MCP configs - Any request like "is my MCP config secure?", "audit my MCP servers", or "check .mcp.json" keywords: [mcp, security, audit, secrets, shell-injection, supply-chain, governance]

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

Analyze V8 heap snapshots to investigate memory leaks and retention issues. Use when given .heapsnapshot files, asked to compare before/after snapshots, asked to find what retains objects, or investigating why objects survive GC. Provides snapshot parsing, comparison, retainer-path helpers, and scratchpad scripts.

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

Guide for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components NuGet package) in Blazor applications. Use this when the user is building a Blazor app with Fluent UI components, setting up the library, using FluentUI components like FluentButton, FluentDataGrid, FluentDialog, FluentToast, FluentNavMenu, FluentTextField, FluentSelect, FluentAutocomplete, FluentDesignTheme, or any component prefixed with "Fluent". Also use when troubleshooting missing providers, JS interop issues, or theming.

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

This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.

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

GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.

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

Guidelines for fixing unhandled errors from the VS Code error telemetry dashboard. Use when investigating error-telemetry issues with stack traces, error messages, and hit/user counts. Covers tracing data flow through call stacks, identifying producers of invalid data vs. consumers that crash, enriching error messages for telemetry diagnosis, and avoiding common anti-patterns like silently swallowing errors.

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

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

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

Triage and resolve Fedora issues with dnf, systemd, and SELinux-aware guidance.

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

Prepare for tomorrow's meetings and tasks. Pulls calendar from Outlook via WorkIQ, cross-references open tasks and workspace context, classifies meetings, detects conflicts and day-fit issues, finds learning and deep-work slots, and generates a structured HTML prep file with productivity recommendations.

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

Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance.

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

Provides expert guidance on Development Containers (devcontainers) — creating, configuring, and optimising containerised development environments using the Dev Container Specification. This skill should be used when users ask about devcontainer.json, .devcontainer setup, Dev Container Features or Templates, pre-building images, multi-container workflows, Docker-in-Docker, cloud development environments (Codespaces, DevPod), or troubleshooting container performance and permission issues.

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

Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks. Use this skill before any deployment to Azure to preview changes, identify potential issues, and ensure the deployment will succeed. Activate when users mention deploying to Azure, validating Bicep files, checking deployment permissions, previewing infrastructure changes, running what-if, or preparing for azd provision.

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

Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld.

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

Analyze Azure resource health, diagnose issues from logs and telemetry, and create a remediation plan for identified problems.

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

Agents workbench layout — covers the fixed layout structure, grid configuration, part visibility, editor modal, titlebar, sidebar footer, and implementation requirements. Use when implementing features or fixing issues in the Agents workbench layout.

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

Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations.

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

Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

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

INVOKE THIS SKILL when downloading or exporting Arize traces and spans. Covers exporting traces by ID, sessions by ID, and debugging LLM application issues using the ax CLI.

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

Scan websites for common vulnerabilities including SQL injection, open ports, and DevTools-related issues. This skill is designed for testing user-owned websites and is compatible with OpenClaw.

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

Optimizes transformer attention with Flash Attention for 2-4x speedup and 10-20x memory reduction. Use when training/running transformers with long sequences (>512 tokens), encountering GPU memory issues with attention, or need faster inference. Supports PyTorch native SDPA, flash-attn library, H100 FP8, and sliding window attention.

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

Roleplay the most difficult, tech-resistant user for your product. Browse the app as that persona, find every UX pain point, then filter complaints through a pragmatism layer to separate real problems from noise. Creates actionable tickets from genuine issues only.

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

Phase 4 of the Forge pipeline. Summarize the whole workload — what was built, which Beads issues closed, a before/after, and a step-by-step walkthrough the user can run to verify it themselves — then run quality gates, push, and open the PR. Use when starting /forge-ship or the ship step of /forgemaster.

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

Triage GitHub issues through gh and a label-based state machine. Use when the user intentionally wants GitHub issue triage, incoming bug or feature review, issue workflow labels, needs-info follow-up, or ready-for-agent briefs.

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

Phase 2 of the Forge pipeline. Turn a research document into an implementation plan that is built around Beads issues and TDD. Reads plans/research/<slug>.md, designs the build, sets up red-green-refactor test strategy using the tdd skill, materializes a Beads epic/feature/tasks with dependencies and priorities, and defines demo/test checkpoints. Use when starting /forge-plan or the plan step of /forgemaster.

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