'defensive' 검색 결과

Stops defensive writing across the entire paper lifecycle — writing, revising, cutting, and organizing experiments. Treats the paper as a press conference, not a project summary, lab log, or self-audit: identify the single most publishable strength of the work and build the most favorable, complete, and persuasive narrative around it. Never present everything evenly, never volunteer weakness, never write an experiment diary, never attack the paper on the reviewer's behalf. Triggers: polish my paper, revise manuscript, write abstract, write introduction, write conclusion, shorten paper, rebuttal, respond to reviewers, organize experiments, defensive writing, AI-flavored academic writing.

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

Reduce defensive writing in drafts and revisions by removing unnecessary caveats, disclaimers, hedges, apology-like framing, negative self-limiting statements, and over-explanations while preserving necessary scope, accuracy, safety, legal, ethical, and methodological limits. Use when drafting or revising academic writing, papers, essays, abstracts, introductions, contribution statements, discussions, conclusions, technical explanations, grant writing, product writing, policy writing, professional reports, or any text the user wants to be clearer, stronger, more direct, more concise, more confident, less verbose, less caveated, less apologetic, or less defensive.

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

Route authorized reverse engineering, security analysis, CTF challenge, and defensive testing requests to specialist skills in a local repository. This Codex adapter selects the relevant workflow and checks the task scope before target actions begin.

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

• Selecting a specialist skill for reverse engineering
• Starting security analysis with a defined scope
• Routing CTF challenge tasks to a suitable workflow

Review common AI slops of defensive programming patterns, avoid silent errors. TRIGGER when reviewing code for defensive anti-patterns, writing fail-fast code, or auditing error handling quality.

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

Practice aikido as a defensive martial art emphasizing harmony, redirection, and controlled resolution. Covers centering and grounding, ukemi (safe falling and rolling), core techniques (irimi-nage, shiho-nage, kote-gaeshi, ikkyo), blending and tai sabaki (body movement), randori (multiple attacker practice), weapons awareness, and applying principles off the mat. Use when learning a defensive martial art that prioritizes de-escalation, developing the ability to redirect aggression without causing unnecessary harm, building safe falling skills, or cultivating calm centeredness under physical pressure.

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

Stops defensive writing across the entire paper lifecycle — writing, revising, cutting, and organizing experiments. Treats the paper as a press conference, not a project summary, lab log, or self-audit: identify the single most publishable strength of the work and build the most favorable, complete, and persuasive narrative around it. Never present everything evenly, never volunteer weakness, never write an experiment diary, never attack the paper on the reviewer's behalf. Triggers: polish my paper, revise manuscript, write abstract, write introduction, write conclusion, shorten paper, rebuttal, respond to reviewers, organize experiments, defensive writing, AI-flavored academic writing.

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

Analyze software protections during authorized reverse engineering, the examination of compiled programs. Helps identify mechanisms that hinder debugging, obscure code, or prevent tampering, then choose safe analysis methods, document findings, and develop defensive recommendations.

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

• Analyze protected software with written permission
• Examine malware within an authorized scope
• Study protection mechanisms in CTFs or approved training

Write more reliable Bash scripts for production automation, CI/CD pipelines, and system administration. Covers input validation, error handling, structured logs, safe temporary files, dry runs to preview changes, and scripts designed for safe reruns.

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

• Writing production automation scripts
• Improving error handling in CI/CD scripts
• Adding dry runs to deployment scripts

Structure research on war, sanctions, and supply disruptions using risk indicators and scenarios. Map potential effects across stocks, commodities, and currencies, then examine warning signals, defensive allocations, and possible market reversals as a crisis eases.

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

• Organize early warning indicators for geopolitical crises
• Trace sanctions and shipping disruptions through supply chains
• Compare crisis scenarios across asset classes

Map threat groups and their attack techniques to MITRE ATT&CK, a catalog of adversary behavior. Generate Navigator visualization files, compare groups, and overlay detection coverage to identify gaps that can guide defensive planning.

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

• Profiling the attack techniques used by a specific threat group
• Comparing techniques across multiple threat groups
• Finding detection gaps against a target adversary

Assess security weaknesses in CI/CD systems that automate software builds and delivery. Covering GitHub Actions, Jenkins, GitLab CI, and Azure DevOps, the skill examines unsafe inputs, excessive permissions, exposed credentials, and tampered build outputs, alongside detection and defensive controls.

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

• Reviewing workflow inputs and execution triggers
• Assessing pipeline permissions and credential exposure
• Checking build artifact handoffs for tampering risks

Defensive Golang coding against accidental bugs — nil panics, typed-nil interfaces, `append` backing-array aliasing, silent int64-to-int32 truncation, float `==` comparison, `defer` inside loops, defensive copies of slices and maps, and usable zero values. Use when a Go program panics on a nil map write or nil pointer dereference, when reviewing code for nil-safety, numeric conversion overflow, or resource lifecycle, or when designing a type whose zero value must be safe. Not for designing concurrent access with goroutines, channels, or sync primitives (→ See `samber/cc-skills-golang@golang-concurrency` skill), not for exploitable vulnerabilities such as injection, weak crypto, or leaked secrets (→ See `samber/cc-skills-golang@golang-security` skill), and not for debugging an already-failing program (→ See `samber/cc-skills-golang@golang-troubleshooting` skill).

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

论文写作、修改、压缩和实验组织全流程中阻止【防御性写作】。把论文视为一场学术发布会， 而不是项目总结、实验日志或自我审查报告：识别这项工作最值得发表的价值，围绕它建立 最有利、最完整、最有说服力的叙事。不平均展示、不主动示弱、不写实验流水账、不替审稿人 攻击自己。 触发词：论文润色、论文修改、写摘要、写引言、写结论、压缩论文、rebuttal、回复审稿意见、 组织实验、论文AI味、防御性写作、心虚。

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

Detects market top probability using O'Neil Distribution Days, Minervini Leading Stock Deterioration, and Monty Defensive Sector Rotation. Generates a 0-100 composite score with risk zone classification. Use when user asks about market top risk, distribution days, defensive rotation, leadership breakdown, or whether to reduce equity exposure. Focuses on 2-8 week tactical timing signals for 10-20% corrections.

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

Reduce defensive disclaimers, stacked hedging, and self-protective narration when drafting, rewriting, or auditing proposals, articles, case studies, captions, and other reader-facing prose. Use when defensive wording is requested for review or appears in a draft, including wording the assistant adds. Preserve meaningful limits; do not perform general style cleanup or ordinary code work.

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

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

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

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

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

Transparent, itemized impressions of AI-generated WRITING STYLE — the repo's ONLY non-integrity track. Two passes: a deterministic defensive-hedge density screen (tools/check_ai_style.py, AIS-DEFENSIVE-HEDGE) plus a fresh cross-model GROSS-cases-only semantic pass over the 13 AIS-* style tells (broken narrative arc, LLM phrase tics, jargon-stuffing, invented codenames, clause/formula walls, gratuitous pseudocode, bullet overuse, bold-module spam, restatement loops, focus drift, single-style figures, appendix dumping). Every finding is named, LOCATED, span-anchored to the evidence ledger (claims.json), carries not_integrity_finding:true + false_positive_risk:high + an fp_case, and gets ZERO verdict weight: the adjudicator forces it to info, excludes it from overall_verdict, and renders it in a SEPARATE report section. NOT an AI-text classifier — no scores, no "this is AI-written", no authorship probability; a paper can be CLEAN_GIVEN_EVIDENCE and still list many. Emits ai-style-impressions.findings.json; computes NO verdict; if a tell is actually substantive it routes to the integrity auditor. Triggers: "AI style", "vibe check", "writing fingerprint", "AI 文风", "vibe paper".

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

Botnet architecture taxonomy, detection techniques, and defensive analysis. Covers C2 topologies, DGA analysis, fast-flux detection, P2P overlay mapping, blockchain C2, and ML-based traffic fingerprinting. Defensive research for understanding and countering distributed malicious infrastructure.

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

Cultivate defensive situational awareness, threat assessment, and mental clarity under pressure. Covers the Cooper color code awareness system, body language reading and intent detection, verbal de-escalation, moving mindfulness in public spaces, combat focus and the OODA loop, rapid grounding techniques for acute stress, context-specific integration, and ongoing review and refinement of awareness skills. Use when entering unfamiliar or potentially hostile environments, needing to assess a situation for safety, de-escalating a verbal confrontation, or integrating awareness practice into daily movement.

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

Master defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts with POSIX compliance, modern Bash 5.x features, and comprehensive error handling. Use when writing shell scripts, bash automation, CI/CD scripts, system utilities, or mentions "bash", "shell script", "automation", "defensive programming", or needs production-grade shell code.

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

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

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

Remove signs of AI-generated code from a codebase while preserving behavior. Use when editing or reviewing code to make it read like a human engineer on this team wrote it. Works through a test-guarded detect-modify-verify loop: pin down the functional contract and edge cases first, write or run tests as a safety net, then rewrite AI tells (redundant comments, emoji, verbose names, reflexive try/except, defensive null-guards, over-decomposition, speculative abstraction, dead code, non-idiomatic constructs, hallucinated dependencies) and re-verify after every change. The tests decide whether a defensive block is slop or a real safeguard.

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

Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.

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