'status' 검색 결과

Monitor Power Automate flow health, track failure rates, and inventory tenant assets using the FlowStudio MCP cached store. The live API only returns top-level run status. Store tools surface aggregated stats, per-run failure details with remediation hints, maker activity, and Power Apps inventory — all from a fast cache with no rate-limit pressure on the PA API. Load this skill when asked to: check flow health, find failing flows, get failure rates, review error trends, list all flows with monitoring enabled, check who built a flow, find inactive makers, inventory Power Apps, see environment or connection counts, get a flow summary, or any tenant-wide health overview. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app

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

Intelligent Git Flow branch creator that analyzes git status/diff and creates appropriate branches following the nvie Git Flow branching model.

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

Debug failing Power Automate cloud flows using the FlowStudio MCP server. The Graph API only shows top-level status codes. This skill gives your agent action-level inputs and outputs to find the actual root cause. Load this skill when asked to: debug a flow, investigate a failed run, why is this flow failing, inspect action outputs, find the root cause of a flow error, fix a broken Power Automate flow, diagnose a timeout, trace a DynamicOperationRequestFailure, check connector auth errors, read error details from a run, or troubleshoot expression failures. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app

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

Use when validating Azure DevOps pipeline changes for the VS Code build. Covers queueing builds, checking build status, viewing logs, and iterating on pipeline YAML changes without waiting for full CI runs.

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

Debug REST/GraphQL APIs: status codes, auth, schemas, repro.

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

Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.

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

Multi-repo git operations — init, reset, status, branch management, refresh (rebase), stacked rebase. JSON output for agent consumption.

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

Manage parallel workstreams — list, create, switch, status, progress, complete, and resume

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

List active GSD workspaces and their status

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

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.

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

Debug AEM Workflow issues on AEM as a Cloud Service — stuck workflows, failed steps, missing Inbox tasks, launcher failures, stale instances, thread pool exhaustion, queue backlogs, purge failures, and permissions errors. Use when the user reports workflow problems on Cloud Service, asks why a workflow is stuck or failed, needs step-by-step troubleshooting, or provides thread dumps, configuration status output, or Sling Job console output for analysis.

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

Use the AEM 6.5 LTS Replication API for programmatic content activation, deactivation, and replication status management

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

Crawl and validate all internal and external links across an AEM Edge Delivery Services site. Uses the query index or sitemap to discover pages, extracts links from .plain.html renditions, checks HTTP status codes, and produces a prioritized report of broken, redirecting, and insecure links. Use when auditing link health before launch, after a migration, or as a periodic maintenance check.

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

[BETA] Expert assistance for the Adobe I/O CLI plugin `@adobe/aio-cli-plugin-aem-rde` — the `aio aem rde` / `aio aem:rde` command tree used to deploy, inspect, log-tail, snapshot, and troubleshoot AEM Rapid Development Environments (RDEs). Activate ONLY when the user explicitly references RDE concepts: 'AEM RDE', 'Rapid Development Environment', `aio aem rde`, `aio aem:rde`, `aem-rde`, RDE snapshots, RDE deploy/install, `rde install`, `rde inspect`, `rde status`, `rde history`, `rde reset`, the `@adobe/aio-cli-plugin-aem-rde` package, or Cloud Manager program/environment configuration that is specifically for an RDE environment. Do NOT activate on generic AEMaaCS phrases like 'deploy to AEM Cloud', 'push my bundle', 'tail the publish log', 'cloud sandbox', or unqualified 'dispatcher-config / frontend / env-config deployments' — those belong to Cloud Manager pipelines, not RDE. This skill is in beta. Verify all outputs before applying them to production projects.

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

Create, edit, fix, or explain Mermaid diagrams for relationships, decision branches, interactions, lifecycles, and data models; also use when the parent selects a diagram to materially clarify an explanation. Do not trigger for simple status, one fact, short lists, quantitative charts, or marketing slides.

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

Make a web app feel native on a phone — the small CSS and meta-tag fixes that separate "a website in a browser" from something that feels installed. Covers sticky hover states, tap highlight flashes, the 100vh bug, inputs that zoom the page, laggy taps, pull-to-refresh hijacking scroll, content under the notch, long-press selecting button text, carousels that scroll the wrong way, mismatched status bars, and the rule that you test on real hardware. Use when a web app is being built for or reviewed on mobile, when something "works in Chrome but feels wrong on my phone", when building a PWA, a bottom sheet, a carousel, a full-screen layout, or any touch interaction. For motion itself use animate; for React Native use animate-expo.

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

Creates consistent error handling with custom error classes, HTTP status mapping, structured logging, safe client messages, and error taxonomy. Use when standardizing "error handling", "logging", "error responses", or "exception management".

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

Unifies API response patterns across endpoints including pagination format, error structure, status codes, response envelopes, and versioning strategy. Provides contract documentation, shared TypeScript types, middleware utilities, and migration plan. Use when standardizing "API contracts", "response formats", "API conventions", or "API consistency".

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

Use when choosing a journal for a finished or nearly finished manuscript, when index status in Scopus, SSCI, ESCI, or TR Dizin must be confirmed, when a venue looks predatory, or when a cover letter needs drafting from the manuscript's actual claims.

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

1. POST to the forgot-password endpoint with a clearly invalid email (e.g. nonexistent@fakedomain12345.com) — record the response body, status code, and length

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

Hunt Missing/Weak Rate Limiting — login brute force, OTP/2FA brute force (10^6 keyspace), password-reset-token brute, credential stuffing, username/email enumeration via error-string / status-code / timing differences, weak password policy, missing CAPTCHA (CAPTCHA token replay / single-use / concurrency-window bypass specifics → hunt-captcha-bypass), IP-based rate-limit bypass via X-Forwarded-For and friends, ReDoS. Distinguishes hard lockout vs soft IP-throttle vs CAPTCHA-injection vs silent shadow-throttling (avoids false-negative 'no rate limit' conclusions). Medium to Critical depending on what the brute reaches (OTP→ATO = Critical).

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

Microsoft 365 / Entra ID red-team attack chain — current 2026 reality. AADSTS code reference, user enumeration vectors (with hardening status), Smart Lockout math, Conditional Access bypass options, ROPC + SAML SSO browser flow, Burp/Playwright templates. Built from authorized red-team work where ROPC spray surfaced pre-existing lockouts and CA-blocked credentials, plus real-time external attacker activity correlation. Use for any M365/Entra credential attack, password spray, user enumeration, CA-bypass exploration, or active-attacker-detection scenario.

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

Query Google Search Console for SEO data - search queries, top pages, CTR opportunities, URL inspection, and sitemaps. Use when analyzing search performance, finding optimization opportunities, or checking indexing status.

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

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

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