'sca' 검색 결과

Set up Muse’s built-in Tailscale connector, join a private Tailscale or Headscale network, and check connection status. Use a TCP tunnel proxy to reach private machines and consult documentation about routing capabilities and supported limits.

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

• Set up the built-in Tailscale connector in Muse
• Join a Tailscale or Headscale network
• Check status and access private machines

ScalarDB Cluster および ScalarDB Analytics のアーキテクチャ、サイジング、構成を見積もるスキル。 性能要件、可用性要件、クラウド環境からScalarDB Cluster Pod数、Kubernetes構成、 バックエンドDB、API Gateway、監視システム等の全体構成を見積もる。 ScalarDB Analyticsを使用する場合はEMR/Databricksのサイジングも含む。 使用タイミング: - 「ScalarDBのサイジングを見積もりたい」「ScalarDB環境を構築したい」 - 「ScalarDB Clusterの構成を決めたい」「ScalarDBの費用を算出したい」 - 「開発/テスト/ステージング/本番環境のScalarDB構成」 - CI/CD、Blue/Green、Canary Deploymentを含む本番環境設計 - 「ScalarDB Analyticsを使いたい」「分析クエリ環境を構築したい」 - 「EMR/Databricksのサイジングを見積もりたい」 出力: Markdown形式の見積もり結果 + HTML形式のレポート 費用: USD/JPY両建て（為替レート明記）

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

Set up encrypted connections between devices with Tailscale and control access by user or device. The skill covers network routing, device name resolution, and self-hosting the coordination server with Headscale.

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

• Replacing a traditional VPN with Tailscale
• Restricting server access by team or device
• Connecting remotely to internal networks

Apache Pekko + Scala 3によるCQRS/Event Sourcing実装ガイド。 PersistenceEffectorを用いた集約アクター、ドメインモデルとアクターの分離、 状態遷移の型安全な表現、イベント設計、Protocol Buffersシリアライズ、 ZIOベースのユースケース層、リードモデルアップデータの実装パターンを提供する。 対象言語: Scala 3限定。CQRS/Event Sourcingアーキテクチャが前提の場合のみ使用。 トリガー条件: 「Scala」かつ「CQRS」または「Event Sourcing」または「Pekko」が リクエストに含まれる場合のみ起動。Scala以外の言語やCQRS/ES以外のアーキテクチャでは このスキルを使用してはならない。 トリガー：「PekkoでCQRS/ESを実装したい」「Scalaで集約アクターを書きたい」 「PersistenceEffectorの使い方」「Pekkoのイベントソーシング」 「ScalaでCQRSのコマンド側を実装」「Pekkoで状態遷移を管理」 といったPekko + Scala + CQRS/ES実装リクエストで起動。 非トリガー：「CQRSのトレードオフ」「イベントソーシングとは」「JavaでCQRS」 「GoでEvent Sourcing」「CQRSの概念を教えて」など、Scala/Pekko以外や概念的な質問では 起動してはならない。

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

Create and edit rooms or buildings in Pascal through MCP, a connection that lets agents use its tools. Inspect existing projects, validate changes, and hand over saved, editable 3D scenes with verified editor links.

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

• Creating a 3D model of a room or building
• Editing walls, windows, stairs, and surface finishes
• Inspecting an existing Pascal project

Create rules for Suricata and Snort, systems that detect suspicious network traffic, to flag port scans and reconnaissance. Combine packet patterns with connection counts, tune alert volume, and summarize scanning sources, targets, and activity.

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

• Create rules to detect Nmap and Masscan activity
• Monitor scanning within an internal network
• Tune alerts for authorized vulnerability scanners

Diagnose failures in GKE HorizontalPodAutoscaler (HPA), which adjusts Pod counts automatically. Investigate missing metrics, unexpected scaling behavior, and slow reactions, then receive proposed configuration fixes or commands for review before deployment.

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

• Investigating unknown metrics and HPA errors
• Diagnosing workloads that will not scale up or down
• Troubleshooting scaling to and from zero

Configure and troubleshoot Salesforce Case Escalation Rules: time-based escalation entries, business hours configuration, escalation actions (email alerts and reassignment), and diagnosing why cases are not escalating. Covers the EscalationRules metadata shape, businessHoursSource and escalationStartTime semantics, staged escalationAction thresholds, deploy-inactive parallel-run cutover, and monitoring escalated cases. Trigger keywords: escalation rule, case not escalating, SLA breach notification, escalate after X hours, reassign case automatically, IsEscalated. NOT for SLA milestone timers — use admin/entitlements-and-milestones. NOT for case routing on creation — use admin/assignment-rules. NOT for the calendar itself — use admin/business-hours-and-holidays.

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

Submit security scans for AI services, tools, skills, and agents through AI-Infra-Guard, then retrieve progress and results. It also supports jailbreak evaluation, testing whether prompts can bypass a model’s safety restrictions.

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

• Scanning AI services for known vulnerabilities
• Auditing MCP tools and skill source packages
• Checking agents from saved settings or YAML files

Guides agents through creating and safely sizing a Replay Vision scanner: choosing the scanner type (monitor/classifier/scorer/summarizer), shaping the RecordingsQuery that selects sessions, and — crucially — estimating observation volume and checking the org's monthly quota before creating, so a broad scanner doesn't exhaust the budget on its first scheduled sweep. TRIGGER when: user asks to create, set up, or configure a Replay Vision scanner, OR when you are about to call vision-scanners-create, OR when widening an existing scanner's query or sampling_rate via vision-scanners-update. DO NOT TRIGGER when: only reading scanners or observations, deleting a scanner, or running an existing scanner against a single session on demand (vision-scanners-scan-session).

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

Identify runtime signs of attackers breaking out of Docker or Kubernetes containers. Review namespace changes, privilege abuse, sensitive host access, and unusual system calls to guide incident investigations and compare monitoring coverage across security tools.

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

• Investigating a suspected Docker or Kubernetes container escape
• Choosing runtime behaviors to monitor for escape attempts
• Comparing escape detection coverage across security sensors

Review Pascal pull requests or branches against documented architecture rules. Check package responsibilities, node extension patterns, state management, and rendering subscriptions to identify misplaced code, compatibility breaks, and changes that could cause excessive redraws.

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

• Reviewing a Pascal pull request for architecture violations
• Auditing package responsibilities in a branch
• Checking new node definitions and scene compatibility

Configure and troubleshoot automatic node scaling in GKE. Examine logs and workload constraints to explain why nodes fail to grow or shrink, and guide tuning for capacity shortages, zone placement, and sudden traffic increases.

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

• Enable automatic scaling for GKE node pools
• Find why nodes do not scale up
• Identify constraints that prevent nodes from scaling down

Security-Scanner Agent fuer fabrikIQ und andere Projekte. Fuehrt umfassende Sicherheitspruefungen durch. Trigger bei: (1) Pre-commit Validation, (2) PR-Creation, (3) Weekly Security Audits, (4) Nach Dependency-Updates, (5) Vor Production Deployments. <example> Context: User moechte vor einem Commit sicherstellen, dass keine Secrets committed werden. user: "Ich will gleich committen. Pruefe mal auf Secrets." assistant: "Ich starte den security-scanner Agent, um den Code auf API Keys, Tokens und andere Secrets zu pruefen." <Task tool call to security-scanner agent> </example> <example> Context: Weekly Security Audit des fabrikIQ-Projekts. user: "Fuehre den woechentlichen Security-Scan durch." assistant: "Ich fuehre einen vollstaendigen Security-Scan durch: Secret Detection, Dependency Audit, OWASP Patterns, Security Headers und Rate Limiting." <Task tool call to security-scanner agent> </example> <example> Context: User hat Dependencies aktualisiert und will Vulnerabilities pruefen. user: "Ich habe npm update und pip install -U gemacht. Gibt es Sicherheitsprobleme?" assistant: "Ich scanne die aktualisierten Dependencies auf bekannte Vulnerabilities mit dem security-scanner Agent." <Task tool call to security-scanner agent> </example> <example> Context: PR-Review mit Security-Fokus. user: "Review den PR #42 auf Security-Probleme." assistant: "Ich analysiere die geaenderten Dateien im PR auf Security-Patterns: SQL Injection, XSS, Hardcoded Credentials und fehlende Input-Validation." <Task tool call to security-scanner agent> </example>

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

Investigate suspicious URLs with URLScan.io by reviewing screenshots, redirects, page content, and network requests. Extract domains, IP addresses, and file hashes as indicators of compromise, then compare findings with threat intelligence sources.

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

• Investigating suspicious links in emails
• Checking pages for brand impersonation and credential forms
• Tracing redirects and extracting domains, IPs, and hashes

Scan source code for security weaknesses with Semgrep after approving the target and rulesets. Choose full results or focus on important findings, then receive merged results and a record of failed or skipped scans.

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

• Audit source code for security weaknesses
• Check for vulnerabilities before code review
• Focus on findings with medium-to-high confidence and impact

Two pipelines ending at a scanner-look PDF. (1) Phone photos of paper documents (contracts, stamped certificates, receipts, forms, handwritten notes) → clean scanner-quality PDF: perspective rectification + noteshrink whitening + A4 assembly + mandatory whole-document check. Trigger: "把照片 做成扫描件", "photos to scanned PDF", "make this look scanned", "手机拍的 文档转 PDF", "盖章文件扫描", replacing pages in an existing scanned PDF, any CamScanner-like request. (2) A digital document with no signature yet (rendered docx/PDF, confirmation form, contract draft) → make it look hand-signed and scanned: synthesize a handwriting-style signature, composite it onto the signature line, apply the same scan-look post-processing. Trigger: "帮我做个手写签名", "生成签名盖到这份文件上", "做成签过字的扫描件", "synthesize a signature", any request for a document that needs to look signed without a real photographed signature. Do NOT hand-roll levels/contrast enhancement for scan-look — tried and rejected twice; this skill's pipeline is the proven one.

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

OpenClaw의 GitHub Secret Scanning 경고를 조사하고 비밀 정보를 가립니다. 댓글 삭제와 재작성, 작성자 알림, 경고 처리를 진행합니다.

• 인증 정보가 유출된 위치를 조사합니다
• Issue와 PR 본문의 비밀 정보를 가립니다
• 비밀 정보가 있는 댓글을 삭제하고 재작성합니다

Investigate excessive privileges inside Kubernetes pods by reviewing security settings, runtime events, and audit logs. Use admission policies to restrict risky configurations and Falco monitoring to detect suspicious privilege changes and container activity.

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

• Finding pods running as root or in privileged mode
• Reviewing host filesystem access and dangerous Linux permissions
• Detecting privilege changes while containers are running

Assess whether a container can escape its isolation and reach the host during an authorized security test. Review privileges, shared mounts, Docker socket exposure, and runC vulnerabilities, then document demonstrated impact and remediation.

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

• Testing container escape within an approved scope
• Assessing the impact of privileged or hostPath workloads
• Validating controls that block container escape

Create and tune Falco rules to detect possible container escapes, where a container gains access to its host. Define detection conditions, alert priorities, and output fields, then refine exceptions to reduce false positives.

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

• Writing rules for suspicious host filesystem access
• Investigating noisy container escape alerts
• Reusing detection conditions through macros and lists

Develop attack detection for SCADA systems that monitor and control industrial equipment. Compare network traffic and process measurements with normal behavior to identify unauthorized commands, altered sensor data, communication disruption, and indicators of known industrial malware.

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

• Introducing intrusion detection in a SCADA environment
• Investigating suspected attacks on industrial control systems
• Creating detection rules for industrial protocol abuse

Unwrap layers of obfuscated PowerShell malware to recover hidden commands, additional malicious code, and server addresses. Combines script structure analysis with execution tracing and decoding tools to support incident investigation and detection work.

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

• Investigating an obfuscated PowerShell script
• Recovering hidden commands and additional malicious code
• Extracting suspicious URLs, IP addresses, and file paths

Build a GitLab CI/CD pipeline with automated checks for vulnerable code, dependencies, container images, running applications, and exposed secrets. Covers scanner configuration, consolidated findings, and approval policies for serious vulnerabilities before production deployment.

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

• Add automated security scans to .gitlab-ci.yml
• Check dependencies and container images for known vulnerabilities
• Detect credentials and API keys committed to source control