1.2천건 · 관련도순
Draft compliance policies required by a framework (access control, incident response, data retention). Use when asked to "write an access control policy", "draft our incident response policy", or "we need a data retention policy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure Salesforce Industries Insurance (Financial Services Cloud Insurance): permission set licenses, irreversible org settings, core insurance objects, coverage types, claim configuration, and OmniScript-based quoting via the Insurance Product Administration API. Trigger keywords: insurance setup, FSC Insurance, InsurancePolicy object, InsurancePolicyCoverage, policy quoting OmniScript, claim type configuration, InsProductService, Digital Insurance Platform, many-to-many policy, multiple producers. NOT for which FSC Insurance modules to license or how to architect claims and underwriting — use architect/insurance-cloud-architecture. NOT for generic OmniStudio setup, CPQ/Pricebook quoting or Health Cloud.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts an Adverse Event Reporting Policy compliant with 21 CFR 312.32 (IND safety reporting), 21 CFR 314.80 (postmarketing), and ICH E2A, with multi-jurisdictional overlays (EMA, PMDA, Health Canada). Covers seriousness/causality frameworks, expedited reporting timelines, roles, documentation standards, training mandates, and QA mechanisms. Use when drafting or updating an adverse event reporting policy, pharmacovigilance policy, AE/SAE reporting SOP, or safety reporting framework for a pharmaceutical company, CRO, biotech, or clinical research institution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a company needs rules for how staff use company systems, data, devices and AI tools, or asks "write our acceptable use policy", "AUP for employees", "can staff use ChatGPT at work", "AI usage policy", "BYOD rules", "remote work security rules" or "a policy people will actually read". Finds how people really work (devices, apps, AI tools, travel), puts the choices to the reader as decisions, drafts a short plain-language policy with concrete do and do not examples, and adds a comprehension check and an acknowledgement text for onboarding.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Azure Policy Deep — azure Policy deep compliance and governance management. Covers policy definitions, initiatives, assignments, compliance evaluation, exemptions, remediation tasks, custom policies, and regulatory compliance. Use when managing Azure governance at scale, reviewing compliance states, creating custom policies, or troubleshooting policy evaluation results.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement Adobe-specific lint rules, CI policy checks, and runtime guardrails covering credential scanning (p8_ patterns), Firefly content policy pre-screening, PDF Services quota enforcement, and OAuth scope validation. Trigger with phrases like "adobe policy", "adobe lint", "adobe guardrails", "adobe eslint", "adobe content policy".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Privacy Policy Generator - 隐私政策生成器. Use when you need privacy policy capabilities. Triggers on: privacy policy. 隐私政策生成器。GDPR/CCPA合规、App/网站隐私政策、合规审计。Privacy policy generator with GDPR, CCPA compliance. 隐私政策、合规。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
제조 현장의 산업 안전 지적 사항, 근거와 시정 요구를 규제 기관과 공장 경영진용 HTML 슬라이드로 정리합니다. 종이 질감과 어스 톤으로 자료를 구성합니다.
시의회 등에 제출할 대중교통 재원 제안을 수요, 계획, 위험 대책, 승인 요청이 드러나는 HTML 슬라이드로 구성하고 포스터풍 색상과 글꼴로 표현합니다.
병원의 환자 데이터 위험, 관리 체계, 책임 분담, 승인 사항을 정리합니다. 이사회나 규제 기관에 설명할 발표자 노트가 포함된 HTML 슬라이드를 만듭니다.
Interpret economic indicators and central bank policy across China, the United States, and Europe. Identify the economic cycle stage and produce a structured assessment of whether to increase, maintain, or reduce allocations to major asset classes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Investigate Google Cloud access denials and choose a resolution path based on the caller’s permissions. Supports temporary access activation, structured escalation tickets, policy analysis, and administrator selection of roles that grant only the permissions needed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check AWS S3 buckets and IAM roles against documented compliance rules. Identify public exposure, missing tags, and overly broad permissions, trace changes through audit logs, and prepare remediation requests for human review without applying fixes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Manage isolated working environments in OpenShell using its command-line tool. Register gateways, create and connect to sandboxes, configure credential providers, and reuse workload templates with shared images, environment settings, and computing resources.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build reproducible empirical analyses in R, from data cleaning to statistical modeling and publication tables and figures. Covers economics, epidemiology, and machine learning approaches to causal inference, which estimates effects of interventions.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
[omh] Bot replies via Discord, Slack, or Telegram: normalize Discord, Slack, Telegram, and other gateway sessions into origin, thread, delivery, silent, attachment, and status-update policy. Use when the user says: gateway-intent-card, gateway intent, discord thread, slack thread, telegram delivery, discord delivery policy, slack delivery policy, telegram delivery policy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Provides verified corrections for IAM behaviors that AI agents frequently get wrong — policy evaluation edge cases, trust policy gotchas, STS session limits, Organizations quirks, and SAML/MFA specifics. Also provides structured workflows for IAM role management and baseline policy generation from application source code or a Terraform plan JSON. Covers condition operator safety (ForAnyValue/ForAllValues with Null checks), bucket policy deny patterns (VPC endpoint restrictions, org paths), confused deputy protection, and service role creation for AWS services (Glue, CloudTrail, Lambda, ECS, etc.) with aws:SourceAccount/aws:SourceArn trust conditions. Applies when creating IAM roles, writing IAM or bucket policies, generating policies from application source code or a Terraform plan JSON, working with STS, Organizations, or condition operators, or any task needing a service or execution role. Does not cover non-IAM authorization like Cognito user-pool policies or app-level RBAC.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and enforce repository, runtime, data, spend, endpoint, and approval guardrails without guessing secret formats or content-policy rules. Use when the task requires adobe policy and execution guardrails. Trigger with "Adobe guardrails", "block unsafe Adobe calls", or "Adobe policy checks".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decide when and how your product and communications must (or should) label AI-generated content, and write the disclosure policy — surface-by-surface rules, exact label wording, and the review trigger for regulations like the EU AI Act's transparency obligations. Use when asked 'do we have to label AI content', 'write our AI disclosure policy', 'are we covered for the AI Act', or when marketing/support/product start shipping AI-generated output. Produces a disclosure policy with a per-surface matrix and ready-to-use label copy. Not legal advice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when deciding whether a project fits AEJ: Economic Policy rather than J. Public Economics, AEJ: Applied, or AER, and when sharpening the policy question and its welfare stake for an AEJ: Economic Policy manuscript. Frames fit and the policy-question-first contribution; it does not design the identification or run estimation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the credibility of the causal evaluation of a policy is the bottleneck for an AEJ: Economic Policy manuscript — DID/event study, IV, RDD/bunching, or RCT of a program. Stress-tests the quasi-experimental policy-evaluation design to the AEJ: Policy bar before exhibits are finalized; it does not build the welfare mapping or write exhibits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when placing the contribution against the policy-evaluation literature and sharpening it as a policy answer for an AEJ: Economic Policy manuscript. Stakes the contribution and the policy-relevant "so what"; it does not write the full introduction or design the identification.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge for Azure Policy development including troubleshooting, best practices, decision making, architecture & design patterns, security, configuration, integrations & coding patterns, and deployment. Use when authoring JSON policies, deploying via ARM/Bicep/Terraform, enforcing security baselines, automating with Gatekeeper, or running policy-as-code in CI/CD, and other Azure Policy related development tasks. Not for Azure Blueprints (use azure-blueprints), Azure Role-based access control (use azure-rbac), Azure Resource Manager (use azure-resource-manager), Azure Security (use azure-security).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Imperative guidance for the System.Text.Json APIs added in .NET 11: the built-in `JsonNamingPolicy.PascalCase` naming policy, and the strongly-typed generic `JsonSerializerOptions.GetTypeInfo` and `JsonSerializerOptions.TryGetTypeInfo` metadata accessors (generic overloads that return a typed `JsonTypeInfo`). USE ONLY when the user is targeting net11.0 or later and needs PascalCase JSON property or dictionary-key names without writing a custom naming policy, a strongly-typed generic `JsonTypeInfo` instead of the non-generic `JsonTypeInfo`, or a no-throw way to probe whether a type's serialization metadata is resolved. DO NOT USE when the target is earlier than net11.0, the requested behavior uses an established pre-net11 naming policy, or the user explicitly selected another JSON library.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.