'rest' 검색 결과

Build Java REST APIs and microservices with Spring Boot 3.x, including database access, authentication, and reactive endpoints for nonblocking request handling. The skill also guides testing and application health checks.

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

• Building Java REST APIs
• Adding authentication and access controls
• Implementing database access

When the user wants to create Pinterest Pins, optimize Pin descriptions, or grow Pinterest presence. Also use when the user mentions "Pinterest," "Pin," "Pinterest SEO," "Pinterest description," "Pinterest board," or "Pinterest marketing." For asset specs, use visual-content.

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

Remove repeated NuGet restores from multi-step .NET builds safely. USE FOR: build/test/publish steps that each restore, Directory.Build.rsp with -restore, safe restore suppression, NETSDK1004/NETSDK1047 after --no-restore. DO NOT USE FOR: slow first restore, only one restore, version or lock errors, unranked build slowness (use build-perf-baseline).

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

Assess REST, GraphQL, and gRPC APIs for authentication, access control, input validation, and business logic weaknesses. Use OWASP API Security Top 10, a framework of common API risks, to organize testing and document findings with reproduction steps and remediation.

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

• Comparing API access across user roles
• Checking token handling and request rate limits
• Assessing GraphQL access control and data exposure

Expose REST APIs as tools for AI agents through Google Cloud API Gateway using MCP, a protocol for connecting agents to tools. Covers OpenAPI migration, authentication, client connections, validation, and troubleshooting.

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

• Expose existing REST APIs as agent tools
• Migrate OpenAPI 2.0 specifications for MCP
• Protect tool listings with JWTs or API keys

Configure Backup for GKE to protect Kubernetes configurations and persistent data. Set backup schedules, retention periods, and customer-managed encryption keys, then prepare restore plans with explicit policies for handling existing resources.

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

• Setting scheduled backups and retention periods
• Backing up persistent data and Secrets
• Encrypting backups with customer-managed keys

Build custom WordPress themes, plugins, and editor blocks, extend WooCommerce stores, and add REST API endpoints. The skill also guides input protection, permission checks, caching, and database query tuning to improve security and performance.

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

• Build custom WordPress themes and plugins
• Create Gutenberg blocks and block patterns
• Extend WooCommerce stores and REST API endpoints

Test REST, gRPC, and WebSocket APIs for weaknesses in authentication, access controls, input handling, and configuration. Provides protocol-specific checks, tool guidance, and detection indicators to help document reproducible findings and severity during authorized assessments.

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

• Check access controls across users and roles
• Review token lifecycles and request limits
• Assess gRPC and WebSocket security

Review Apache Pinot changes against naming and API conventions, including public names, method signatures, REST endpoints, JSON fields, and documentation. Use it when adding or renaming elements exposed to other code or users.

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

• Reviewing public class, method, or field names
• Checking new enum constants or DataType values
• Reviewing REST endpoints and JSON fields

Investigate GraphQL APIs for unauthorized data access, unsafe updates, and permission inconsistencies with REST APIs. The skill covers schema discovery, checks across users and organizations, and validation steps that turn suspected weaknesses into reproducible findings with concrete impact.

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

• Map GraphQL schemas and sensitive operations
• Check access boundaries between users and organizations
• Compare permission changes across REST and GraphQL

Classical end-to-end empirical analysis workflow in the traditional Stata ecosystem — native Stata + reghdfe + ivreg2 + csdid + did_imputation + eventstudyinteract + sdid + rdrobust + rddensity + synth + synth_runner + psmatch2 + teffects + ebalance + coefplot + esttab + asdoc + binscatter. **Defaults to economics empirical-paper style** (AER / QJE / AEJ) — every run produces a publication-ready output set with a multi-column regression table (M1→M6 progressive controls/FE) as the centerpiece, plus Table 1 (descriptives), mechanism / heterogeneity / robustness tables, and event-study + coefficient + trend figures. Covers the full 8-step Stata pipeline an applied economist runs on every paper — (1) data import & cleaning (use/import, destring, misstable, duplicates, merge assert), (2) variable construction (gen/egen/winsor2/xtile/xtset with L./F./D.), (3) descriptive statistics & Table 1 (tabstat/balancetable/asdoc), (4) classical diagnostic tests (sktest/swilk/hettest/imtest/xtserial/xttest3/vif/dfuller/kpss/hausman/estat overid), (5) baseline modeling (reg/xtreg/reghdfe/ivreg2/ivregress/csdid/did_imputation/eventstudyinteract/sdid/rdrobust/synth/psmatch2/teffects/heckman/qreg/ppmlhdfe), (6) robustness battery (bacondecomp/honestdid/rwolf/ritest/wildbootstrap/oster), (7) further analysis (subgroup/triple-diff/interactions/medsem/marginsplot/binscatter by group), (8) publication-ready tables & figures (esttab/outreg2/estout/coefplot/marginsplot/rdplot/twoway combined). **Also covers two parallel domain modes that share the same 8-step scaffolding** — **Mode A — Epidemiology / public health** (target-trial emulation, IPTW + g-formula + TMLE doubly-robust triplet via `teffects ipw` / `teffects ipwra` / `teffects aipw` / `eltmle`, Mendelian randomization via `mrrobust` (IVW / Egger / weighted median) and `mregger` / `mrpresso`, KM / Cox / AFT / RMST survival via `sts` / `stcox` / `streg` / `strmst2`, E-value sensitivity via `evalue` (Linden-Mathur), principal stratification — STROBE / TRIPOD reporting), and **Mode B — ML causal inference** (DML via `ddml` / `pdslasso`, S/T/X/R/DR meta-learners via `crforest` and `ddml interactive`, causal forest via `crforest` / `cforest`, BART/BCF via `bart` / `bartCause`-style externals, CATE distribution + policy tree via `crforest`, off-policy evaluation, conformal causal externals, fairness audit, DAG learning via `pcalg` / external Python callouts). Use when the user asks for a complete Stata empirical analysis, wants a reproducible .do-file pipeline, needs a Stata counterpart to the Python StatsPAI / Full-empirical-analysis-skill, or names a specific Stata step in isolation ("run reghdfe with two-way clustering", "csdid event study", "winsor2 at 1%", "esttab to LaTeX", "coefplot with CI", "ivreg2 weak-IV test", "synth_runner placebos", "teffects psmatch balance check"). Mode A triggers on "target trial emulation Stata", "teffects ipw aipw", "eltmle", "mrrobust", "mregger weighted median", "stcox AFT survival", "strmst2", "evalue Stata", "STROBE Stata", "公共健康 Stata", "流行病学 Stata". Mode B triggers on "ddml Stata", "pdslasso", "crforest causal forest Stata", "policy tree Stata", "因果机器学习 Stata".

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

GDPR Legitimate Interest Assessment (LIA) — Guided assessment for Art. 6(1)(f) GDPR using the EDPB three-step test. Based on EDPB Guidelines 1/2024, EDPB Opinion 28/2024 (AI models), the OSS Case Digest on Legitimate Interest (McIntyre 2026), CNIL AI guidance (June 2025), ICO guidance, and key CJEU case law. Use when: (1) user needs to assess whether legitimate interest is appropriate, (2) user asks about Art. 6(1)(f), "Interessenabwägung", "berechtigtes Interesse", "balancing test", or "LIA", (3) user wants to document a legitimate interest assessment, (4) user mentions the three-step test, (5) user evaluates necessity or proportionality under Art. 6(1)(f), (6) user discusses direct marketing, fraud prevention, IT security, employee monitoring, AI training, web scraping, or credit checks in context of legal basis, (7) user handles a right to object (Art. 21), (8) user asks about children's data, profiling, or cross-border data sharing under legitimate interest, (9) user compares legitimate interest against other legal bases. Do NOT use for: consent assessments (Art. 6(1)(a)), contract performance (Art. 6(1)(b)), DPIA workflows, or pure ePrivacy/cookie compliance questions — though the skill does address the ePrivacy/GDPR overlap where relevant.

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

Handles GDPR Article 18 right to restriction of processing requests, covering the four grounds for restriction (accuracy contest, unlawful processing, erasure opposition, legitimate interest pending), technical flagging mechanisms, and lifting procedures. Activate for restriction request, Art. 18, processing freeze queries.

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

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).

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

Audit Pinterest Ads measurement, Pinterest Tag and Conversions API, catalog and shopping readiness, visual creative, audiences, Performance+ intent, budgets, brand safety, and reporting. Use for Pinterest Ads, promoted Pins, shopping ads, catalog sales, Pinterest Tag, Pinterest Conversions API, or Pinterest Performance+.

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

Use this skill when a restore test is due, an auditor or customer asks for proof that backups can be recovered, or someone says "plan a restore test", "prove we can recover in time", "our backups succeed but we never restored", "test our RTO and RPO", "write up the disaster recovery test" or "document the backup restore for the audit". Picks what to restore, writes a test plan with success criteria set before the test, records timings against the recovery objectives, and produces a signed-off test record with the issues found and their owners.

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

Audit Pinterest Ads measurement, Pinterest Tag and Conversions API, catalog and shopping readiness, visual creative, audiences, Performance+ intent, budgets, brand safety, and reporting. Use for Pinterest Ads, promoted Pins, shopping ads, catalog sales, Pinterest Tag, Pinterest Conversions API, or Pinterest Performance+.

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

stacked PRの下位PRがマージされた後に上位branchをrestack（rebase/cherry-pick再構成）する際に使用。「restackして」「上位PRを更新して」「restack after merge」「PRのbaseを更新」「スタックを整理」という依頼でトリガーする。対象sliceの特定→rebase→変更ファイル確認と代表テスト実行→force-with-leaseでpush→PR base更新→auto-merge判定の順で進める。

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

Kotlin과 Ktor로 HTTP 서버를 만드는 구현 예시를 제공합니다. API 라우트, 인증, JSON 변환, 구성 요소 조립, 통신과 테스트를 정리합니다.

• Ktor로 REST API 만들기
• JWT 인증으로 라우트 보호
• Koin으로 앱 구성 요소 정리

Rebuild modified packages in the Storybook monorepo and restart its internal UI after code changes. The workflow provides the running URL and can optionally create a UI review of stories related to the changes.

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

• Rebuilding after changes to Storybook internals
• Restarting the internal Storybook UI
• Reviewing stories related to UI changes

Test REST, GraphQL, and gRPC APIs with Strix using schemas, credentials, and example data. Investigate authorization flaws, excessive data exposure, and other API risks, then verify findings with requests that reproduce the issue.

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

• Testing an API from its specification
• Checking data access across tenants
• Verifying restrictions on administrator routes

Choose between REST, GraphQL, and tRPC based on who uses an API and how it is deployed. Define consistent responses, pagination, authentication, and versioning, supported by concrete request examples and failure cases.

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

• Choose an API style for known clients
• Standardize response and error formats
• Design pagination for changing data

Build Node.js APIs and backend services with Express/Fastify. The skill guides authentication, database integration, error handling, and operational practices such as logging and health checks, which report whether a service is working.

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

• Build a REST API with Express/Fastify
• Add authentication and database integration
• Organize middleware and error handling

Organize Confluence team wikis and project documentation with clear page hierarchies, labels, and templates. Use macros, built-in content tools, to assemble indexes and reports, with REST API guidance for creating and updating pages.

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

• Reorganizing a team wiki
• Building an index of decisions and runbooks
• Standardizing recurring meeting notes