142건 · 관련도순
Identify security threats in system designs using STRIDE, a method covering six threat categories. Use structured questions to review components, prioritize threats by impact, and document findings and possible safeguards.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code and infrastructure for security risks, map potential threats, and plan stronger defenses. The skill covers OWASP checks, attack and defense exercises, and incident response, with validation required for each environment.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Identify security threats across system components and data flows, score their risks, and prioritize mitigations. Run a quick scan for exposed credentials and route requests beyond threat modeling to the appropriate specialist skills.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review plans involving customer data, compliance, or production access. Examine threats, potential damage, detection, incident response, notification requirements, and vendors, then summarize whether the plan can proceed, needs mitigation, or should be blocked.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Apply over 240 reusable prompt templates to summarize content, extract insights, improve writing, review code, or analyze security threats. It reads each template directly and returns results in the format defined for that task.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a structured threat-modeling session for a new feature, system, or architecture — STRIDE, attack trees, data flow diagrams, abuse cases. Use when the user mentions 'threat model,' 'threat modeling,' 'STRIDE,' 'attack tree,' 'abuse case,' 'data flow diagram,' 'DFD,' 'security architecture review,' 'security review,' 'design review,' 'pre-implementation security,' 'shift left,' 'what could go wrong,' or needs strategic security thinking before code is written.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Chief Security Officer mode. Infrastructure-first security audit: secrets archaeology, dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification. Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep scan, 2/10 bar). Trend tracking across audit runs. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates comprehensive threat models using STRIDE methodology with asset identification, threat enumeration, mitigation strategies, and residual risk assessment. Use for "threat modeling", "security analysis", "STRIDE", or "risk assessment".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Develop or port CPU kernels, the low-level calculation routines used by MNN. Follow staged implementation guidance, check data layout agreements, register functions, and verify correctness across processor instruction sets and numerical precision settings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a threat model that identifies valuable assets, attack entry points, potential threats, and mitigation priorities. Use source code and past vulnerabilities, an interview with the application owner, or a combination of both.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Security best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run an AWS Security Agent threat model review on spec/design documents. Use when the user asks to review a spec for security, run a threat model, check if a design introduces security risks, review requirements.md or design.md for security posture changes, or STRIDE analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AIDefence security layer with prompt injection blocking, input validation, sandboxed execution, output sanitization, and STRIDE threat modeling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture reviews, threat identification, and secure-by-design planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Consolidated Responsible AI standards reference: NIST AI RMF 1.0, AI STRIDE threat-modeling overlay, EU AI Act risk tiers, and an open-standards catalog with phase mapping
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Security planning and plan-drift analysis for STRIDE, standards, controls, backlog handoff, current findings, and TM7 generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Download raw sequencing reads from NCBI SRA using sra-tools (prefetch, fasterq-dump, vdb-validate) or the ENA mirror. Use when pulling FASTQ for SRR/ERR/DRR accessions, deciding between SRA-direct, ENA mirror, or AWS/GCP cloud mirror (STRIDES), handling --include-technical for 10x and other single-cell records, validating with MD5/vdb-validate, navigating SRR/SRX/SRS/SRP/PRJNA hierarchy, or finding accessions via pysradb. Encodes SRA cloud-egress economics, the fasterq-dump uncompressed-scratch trap, and the --max-size default that silently truncates large prefetches.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reconcile gene trees against a species tree under probabilistic models of duplication, transfer, and loss (DTL) using ALE (Szöllősi 2013 amalgamated likelihood), GeneRax (Morel 2020 ML reconciliation), AleRax (Morel 2024 co-estimation), Whale.jl (Bayesian DL+WGD), RANGER-DTL 2 parsimony, NOTUNG, ecceTERA, and Treerecs. Use when inferring ancestral gene-family content, distinguishing duplication from horizontal transfer from differential loss, rooting deep species trees from gene-content signals (STRIDE / Williams 2017 ALE-rooting), counting DTL events per branch, refining noisy gene trees against a species tree, modeling WGD events jointly with DTL, or producing publication-grade gene-family histories for phylogenomic / comparative analyses.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct threat modeling using STRIDE methodology. Identify threats, assess risks, and design security controls. Use when designing secure systems or assessing application security.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
STRIDE + OWASP-based security audit with optional auto-fix. Scans code for vulnerabilities, categorizes by severity, and can iteratively fix findings using vc-autoresearch pattern.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
STRIDE threat modeling, DREAD risk scoring, secret detection, and secure architecture design. Use when conducting threat models, reviewing code for vulnerabilities, designing defense-in-depth, or scanning for hardcoded secrets.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Infrastructure-first security audit across 14 phases: attack surface mapping, secrets archaeology (git history), supply chain analysis, CI/CD pipeline security, LLM/AI threat detection, OWASP Top 10, STRIDE threat modeling. Confidence gates, exploit scenarios, parallel verification, trend tracking. Read-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.