35건 · 관련도순
Discover and exploit mass assignment vulnerabilities in REST APIs to escalate privileges, modify restricted fields, and bypass authorization controls by injecting unexpected parameters in API requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide Zoom Virtual Agent integration into websites and mobile apps, covering embedded chat, conversation startup and cleanup, and handoff to live support. It also directs developers to platform references and knowledge-base synchronization workflows.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build server-side Zoom integrations for meeting scheduling, user management, and recording downloads. This reference guides API endpoint selection, OAuth authentication, request limits, and error diagnosis, with examples for automated workflows and event notifications.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan how an AI agent should interact with Zoom through MCP, a protocol for calling tools. Assess task suitability, divide responsibilities between MCP and REST APIs, and identify connection, authentication, and client requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide Zoom Contact Center integrations across Zoom client apps, websites, and native mobile apps. Use platform references to implement chat, video, scheduled callbacks, and handling of customer interaction states, context changes, and resource cleanup.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guides HTTP integration with the agentmemory server for saving and searching knowledge. It explains authentication, request conventions, and endpoint references, including how to connect systems that do not support MCP, the agent tool connection protocol.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Call the Obsidian Local REST API directly (over HTTP) for vault operations the mcp__obsidian__* tools do NOT expose — move/rename a note, overwrite a whole file atomically (PUT), act on the currently-open active file, run an Obsidian command, open a note in the UI, list all tags, or do date-specific periodic-note CRUD. Prefer the mcp__obsidian__* tools for plain read/append/patch/delete/search; fall back to this skill only when the required method is missing from MCP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
cuOpt REST server — start server, endpoints, Python/curl client examples. Use when the user is deploying or calling the REST API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run end-to-end calibration on the shipped sample dataset (sdg_08_2_sample_data_010926.zip) against a running AMC microservice. Use when user says 'test sample dataset', 'run sample calibration', 'verify AMC install', or 'launch and test'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Calibrates pre-recorded `cam_*.mp4` datasets through the AutoMagicCalib REST API. Use for user-supplied local MP4s; route live RTSP streams to `amc-run-rtsp-calibration`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras; VIOS records clips, AMC ingests them, then runs calibration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploys a Regional REST API with a custom domain name, a Lambda backend function, and a request-based Lambda authorizer using AWS CLI. Covers ACM certificate provisioning, API Gateway REST API creation, Lambda function deployment, request authorizer setup, custom domain configuration, base path mapping, and Route 53 DNS record creation. Trigger keywords: custom domain, REST API, Lambda, Route 53, API Gateway, regional endpoint, request authorizer, base path mapping.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnoses and root-causes Amazon MWAA workflow failures across Provisioned (Python DAG) and Serverless (YAML workflow) environments. Provisioned uses aws mwaa invoke-rest-api, CloudWatch log groups, and get-environment; Serverless uses aws mwaa-serverless API (GetWorkflowRun, ListWorkflowRuns, GetTaskInstance) and CloudWatch logs. Covers failed runs and tasks, DAGs not appearing, import errors, worker OOM, IAM denials, and dependency drift. Triggers on: DAG failed, task failed, workflow run failed, MWAA error, debug my DAG, why did my workflow fail, DAG not showing up, MWAA import error, requirements failing, worker crashed, serverless run failed. Not applicable to authoring workflows (handled by authoring-mwaa-workflow), running or smoke-testing a workflow (handled by testing-mwaa-workflow), or CI-CD deploy failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
cuOpt REST server — start server, endpoints, Python/curl client examples. Use when the user is deploying or calling the REST API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build, manage, and operate APIs with Amazon API Gateway (REST, HTTP, and WebSocket). Triggers on phrases like: API Gateway, REST API, HTTP API, WebSocket API, custom domain, Lambda authorizer, usage plan, throttling, CORS, VPC link, private API. Also covers troubleshooting API Gateway errors (4xx, 5xx, timeout, CORS failures) and IaC templates containing API Gateway resources. For general REST API design unrelated to AWS, do not trigger.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides patterns for unit testing external REST APIs using WireMock. Stubs API responses, verifies request details, simulates failures (timeouts, 4xx/5xx errors), and validates HTTP client behavior without real network calls. Use when testing service integrations with external APIs or mocking HTTP endpoints.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when generating REST controllers, DTOs, success response contracts, pagination, HTTP status mapping, or API versioning. For RFC 9457 exception and error response formatting, use problem-details-rfc9457 unless the project explicitly requires a legacy error envelope.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix features broken by REST API responses that flatten Nostr events, losing tag data. Use when: (1) A feature works for WebSocket-loaded events but not REST API-loaded ones, (2) A model field (like sha256, textTrackRef) is null for REST API data but set for WebSocket data, (3) REST API returns denormalized fields (d_tag, video_url) but omits raw tags array, (4) hasSubtitles/hasFeature returns false for REST-loaded videos. Common in Nostr clients that use both REST APIs (for analytics/bulk queries) and WebSocket (for real-time events).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix "content disappears after publishing" bugs caused by REST API indexing lag. Use when: (1) User publishes content but it doesn't appear in their feed/profile, (2) REST API returns stale data immediately after write operations, (3) Async indexing backends (ClickHouse, Elasticsearch, etc.) haven't processed new events, (4) Content shows briefly then vanishes on refresh. Applies to any system with separate write path (WebSocket/direct DB) and read path (REST API with async indexing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs RESTful APIs with proper resource naming, HTTP methods, status codes, and response formats. Use when building new APIs, establishing API conventions, or designing developer-friendly interfaces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when adding or changing a Go HTTP endpoint — Fiber v2 or v3 (detect which), thin handlers, central error mapping, boundary validation; the same rules apply to net/http, chi, echo or gin
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.