'recommend rule' 검색 결과

Use this skill when the user is invoking doca_flow_dpa_perf on DPA-capable hardware (ConnectX-7 minimum supported, ConnectX-8 recommended, or BlueField-3) to measure rule update / disable rates on the DPA-offloaded DOCA Flow path — picking the active / passive device split, choosing workload-shape axes (burst, queue, completion threshold, workers, hash pipe algo, PSL tables), or reading Kops/sec iteration stats and the optional self-test. Trigger even when the user does not explicitly mention "doca_flow_dpa_perf" or "DPA Provider" — typical implicit phrasings include "how fast can the DPA program path-selector entries", "baseline rule-update rate on ConnectX-8", "tool reports zero ops on my BlueField", "self-test sentinel never shows on tcpdump", or "is my BlueField-2 DPA-capable". Refuse and route elsewhere for the host / DPU-CPU Flow path (doca-flow-perf), Flow pipeline tuning (doca-flow-tune), writing doca-flow / doca-dpa applications, or DOCA install — those belong to other skills.

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

Read-only audit of a GitHub repository's security posture. Gathers ref protection (rulesets AND classic branch protection), Actions token permissions, code and supply-chain features (Dependabot, secret scanning, push protection, CodeQL), and repo hygiene toggles via `gh api`, then classifies findings against essential / recommended / advanced tiers into a PASS/GAP report. Makes NO changes. Use when reviewing a repo before open-sourcing or a release, auditing a public user-owned repo whose CI auto-commits to the default branch, verifying a hardening change actually took effect, or producing a baseline security posture report for a repository.

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

기계 학습이 없는 기존 앱에 추천, 분류, 예측 기능을 추가하는 절차를 정리합니다. 문제와 데이터 확인부터 초기 모델의 학습, 평가, 통합까지 돕습니다.

• 기존 앱에 추천 기능 추가
• 학습 데이터 준비 상태 확인
• 대체 규칙을 갖춘 예측 기능 통합

Claude Code가 읽는 에이전트, 스킬, 규칙, MCP 설정의 정보량을 점검합니다. 길거나 중복된 정의를 찾고 예상 절감량에 따라 개선안의 우선순위를 제시합니다.

• 컨텍스트가 빨리 차는 원인을 조사합니다
• 스킬이나 MCP 추가 후 설정을 점검합니다
• 긴 파일과 중복 지시를 확인합니다

새 제품의 목적과 경쟁 제품 조사를 바탕으로 색상, 글꼴, 여백, 동작 규칙을 제안합니다. 미리보기로 확인하고 DESIGN.md에 설계 방향을 정리합니다.

• 새 제품의 시각적 방향을 정할 때
• 브랜드와 화면의 공통 규칙 문서화
• 글꼴과 색상 조합 확인

Audit slow page loads by measuring how static files, such as images and scripts, are delivered. Check CDN usage, a network of distributed servers, and identify caching or delivery settings that need improvement.

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

• Investigating slow page loads
• Checking CDN delivery of images and scripts
• Reviewing caching settings for global audiences

Review Monte Carlo alerts, score their likelihood of indicating an incident and their potential impact, and investigate likely causes. Use the same stages to design and test a repeatable triage workflow, starting with recommendations before enabling actions.

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

• Reviewing recent Monte Carlo alerts
• Prioritizing alerts by incident likelihood and impact
• Designing and testing a recurring triage workflow

Assess serverless functions, primarily AWS Lambda, for unsafe execution of external input and unauthorized changes to code or added libraries. Combine source inspection, activity logs, and permission reviews to identify injection risks and recommend detection and prevention measures.

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

• Reviewing Lambda event handlers for injection vulnerabilities
• Investigating unauthorized function or layer changes
• Checking privilege escalation through Lambda execution roles

Investigate lateral movement, where attackers expand access across Azure identities and tenants. Correlate audit logs and unusual sign-ins, build Microsoft Sentinel detection queries, and report affected identities with recommended containment actions.

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

• Investigating suspicious Azure sign-ins
• Building Microsoft Sentinel detection rules
• Reviewing suspicious OAuth app consent

Assess authorized networks through host discovery, service checks, vulnerability identification, and controlled exploitation. Follow a structured testing process to document attack paths, demonstrate business impact, clean up test artifacts, and prioritize remediation.

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

• Assessing internal or external network security
• Validating firewall rules and network segmentation
• Verifying whether service vulnerabilities are exploitable

Audit Kubernetes RBAC, the rules that assign access through roles, to identify excessive permissions, risky role assignments, and paths to gaining higher privileges. Review service accounts and produce findings with recommended permission changes.

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

• Reviewing access permissions in shared Kubernetes clusters
• Finding accounts that can read secrets or gain higher privileges
• Checking service account token mounts

Audit Kubernetes access rules to find excessive permissions and service account token abuse paths. Trace which users or workloads could gain cluster administrator access, then produce prioritized findings and recommendations for reducing permissions.

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

• Reviewing Kubernetes privilege escalation paths
• Checking permissions after an RBAC change
• Tracing workloads with overprivileged service accounts

Adapt a knowledge collection's schema, the rules defining page types and relationships. Review untyped pages, propose new types, update classification settings, and apply those types to existing pages after previewing the changes and checking consistency.

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

• Adding page types for researchers and papers
• Classifying existing pages that have no type
• Proposing new types from stored content

Recommend where new gbrain pages belong using the active schema pack, a configuration defining page types and storage paths. It also checks existing pages for missing or undeclared types and highlights cases requiring a classification decision.

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

• Choose a storage path before creating a brain page
• Check filing rules before a bulk import
• Apply classification settings for a specific source

Turn brand documents, sales call transcripts, discovery reports, and direct input into writing guidelines. Define a consistent brand personality, adapt tone by context, and attach source evidence, confidence ratings, and recommendations for unresolved questions.

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

• Consolidating scattered brand materials into writing guidelines
• Extracting brand language from sales call transcripts
• Defining tone for social posts and business proposals

Check mesh files for 3D printing by measuring geometry and comparing it with process-specific design limits. Get findings on wall thickness, overhangs, and supports, plus build orientation options and concrete redesign guidance.

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

• Check whether a mesh meets printing design limits
• Find thin walls and unsupported overhangs
• Compare build orientations to reduce supports

Plan authorized security tests involving phone calls, text messages, physical access, and USB devices. Helps develop scenarios from public information, document interactions, and assess how staff verification procedures and physical controls respond.

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

• Planning authorized phone and SMS security tests
• Reviewing visitor and badge verification procedures
• Designing USB device security exercises

Choose a prioritization method that fits your product stage, team, stakeholder needs, and available data. Get a recommended framework, practical setup steps, a scoring example, and an alternative approach with its tradeoffs.

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

• Choosing a method for recurring roadmap prioritization
• Selecting a lightweight approach when data is scarce
• Agreeing on prioritization rules with stakeholders

Create UTM links, which identify traffic sources, and GA4 event specifications for marketing campaigns. Standardize names across advertising and email channels, with platform-specific parameter templates, implementation notes, and recommendations for checking tracking before launch.

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

• Create tracking links for campaigns across multiple channels
• Standardize campaign naming rules across a team
• Define GA4 events for purchases and form submissions

Design reusable SEO page templates from a niche and data source. Get title patterns, page sections, internal linking rules, structured data for search engines, and requirements that keep each page useful and distinct.

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

• Planning location pages for a service
• Designing product comparison page templates
• Building industry-specific software recommendation pages

Use when the user asks to "personalize the email", "add merge tags / dynamic content", "set up conditional blocks per segment", or "make first-name and product-recommendation fields fall back safely"; produces a merge-tag map with per-tag fallbacks, conditional-block rules with per-segment variations, a fallback-safety audit, and a PII guard on what may render, informing the SEND E (Engagement/personalization) dimension. Not for building the segments — use list-segment-builder; not for writing the base copy — use email-creative-builder; not for scoring EQS or running vetoes — use email-quality-auditor. 邮件个性化/合并标签/条件内容块/兜底默认值

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

AWS security service suitability, coverage and cost recommendations: WAF/origin overlap, AWS Network Firewall inspection coverage and policy review, VPC endpoint, Transit Gateway/Cloud WAN segmentation and DNS Firewall security-control suitability, certificate renewal ownership and monitoring, incident response triage ownership, centralized security log store (CloudWatch or Security Lake). Also factual configuration, findings, data sources and severity scoring for GuardDuty, Inspector, Security Hub V2/OCSF (Exposure, connectors, automation), Security Hub CSPM/ASFF (standards, controls), Macie, Detective, Security Lake, AWS Security Incident Response membership and case coverage, and Organizations security policies. Applies to advisory security-service choices even when one service is named. Implementation, rule or code authoring, deployment, scans and troubleshooting outside these factual procedures belong to specialist skills. Supports local AWS CLI and AWS MCP.

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

Converts an audited medical research gap into a complete, structured, gap-traceable study design. Always use this skill whenever a user already has one or more candidate research gaps and wants to transform them into an executable biomedical research plan rather than re-run broad topic ideation. Covers six gap-to-design patterns (evidence-completion, mechanism-resolution, cell-state/context-mapping, translation-bridge, causality-upgrade, population/stage-specific) and always outputs one recommended primary protocol, a gap-to-design dependency map, step-by-step workflow, figure plan, validation strategy, minimal executable version, publication upgrade path, and verified design-support literature rules. Never fabricate references. Preserve claim-evidence discipline and do not replace a topic-specific gap with a generic workflow.

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

Analyze weekly marketing campaign performance data across channels. Use when analyzing multi-channel digital marketing data to calculate funnel metrics (CTR, CVR) and compare to benchmarks, compute cost and revenue efficiency metrics (ROAS, CPA, Net Profit), or get budget reallocation recommendations based on performance rules.

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