'leverage' 검색 결과

Leveraged-prototype dev loop (`pulp loop`) — focus marker plus normal watch/rebuild loop, with AOT analyzer guidance and deferred ar-swap/PR-monitor playbook. Use when porting an existing UI/bundle to Pulp, doing visual/behavioral parity work, or batching upstream framework gap fixes.

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

Use when a task needs the judgment of a Credit Analyst — spreading financial statements and computing leverage/coverage ratios, writing a commercial credit memo, assigning or recommending an internal risk rating, structuring covenants on a term loan or revolver, or stress-testing a borrower's debt service under a downside case. Narrower than loan-officer (originates and manages the client relationship; the analyst underwrites the credit that officer brings in) and financial-risk-specialist (owns portfolio-level risk and concentration limits, not single-borrower underwriting).

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

Guides agents and users through migrating from Gemini API in Google AI Studio to Gemini Enterprise Agent Platform (formerly Vertex AI). Use this skill when moving applications to Google Cloud, to leverage Cloud credits, or to unify inferencing with other Cloud infrastructure (IAM, billing, telemetry).

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

Feature discovery agent — mines project docs, memory, user feedback, and competitor gaps to surface the highest-leverage features to build next. Outputs a prioritized feature backlog.

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

Consult the Eldar — audit a project's moflo + Claude Code setup for portable, high-leverage gaps and guide remediation. Default mode is read-only audit with severity-ranked findings; --fix presents an interactive triage menu and walks the user through each chosen fix (healer, missing CLAUDE.md, sparse guidance, hook/MCP wiring, empty memory namespaces, stack→guidance gaps). Use when starting in a new project, when Claude feels lost or inefficient, when guidance/CLAUDE.md is sparse, or as a periodic health check.

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

法律事项的运营性计费执行。月度账单准备和计费指示、LC 发票审查和代垫款处理、客户账单质询回应、现金流建模（LC 付款义务与客户收款对比）、杠杆和消耗分析（人员配置组合、预测总成本、利润轨迹）。触发词：‘prepare the bill’（准备账单）、‘billing instruction’（计费指示）、‘end of month billing’（月末计费）、‘LC invoice’（LC 发票）、‘local counsel invoice’（本地顾问发票）、‘pass through as disbursement’（作为代垫款转付）、‘client querying the invoice’（客户质疑发票）、‘billing dispute’（计费争议）、‘cashflow gap’（现金流缺口）、‘when will we get paid’（我们何时能收到付款）、‘LC payment due’（LC 付款到期）、‘leverage analysis’（杠杆分析）、‘staffing mix’（人员配置组合）、‘predicted total cost’（预测总成本）、‘burn rate by grade’（按职级消耗率）、‘are we on track’（我们在轨道上吗）、‘what will this matter cost’（此事项将花费多少）。

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

Manages datasets, tables, and jobs in BigQuery, and integrates with BigQuery ML and Gemini for advanced data analytics and AI-driven insights. Use when you need to interact with BigQuery, run SQL queries, manage BigQuery resources, or leverage BigQuery's built-in ML capabilities. Also use when performing data analysis, ingesting data into BigQuery, or developing AI applications on BigQuery.

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

Use when designing or improving a module interface, choosing a seam, reducing shallow modules, making code easier to test, or reviewing architecture for locality, leverage, adapters, and deep-module design.

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

Use when preparing hardest high-leverage work for a stronger or scarce model, building a ranked execution queue, asking for fable prep, frontier prep, round-collapse, wave queue, or model-upgrade readiness across code, design, copy, marketing, or architecture work.

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

Use for systems thinking, or when a change may ripple beyond its target: "what are the side effects?", "why does this keep coming back?", "how do these teams or services affect each other?". Maps loops, delays and leverage points. Skip for single-step fixes.

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

Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.

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

Bootstrap self-improving Symphony + Linear orchestration for a software repository. Use when Codex needs to inspect a repo, review or generate repo-local guidance, shape Linear issues, render a Symphony workflow, launch a high-leverage first execution wave, or run an orchestrator-led review, recovery, and learnings loop that makes future runs better.

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

Clarify the brief BEFORE any design work to avoid building the wrong thing. Interrogates goal, user, constraints, success criteria, and scope, then writes a short context doc the other design skills consume. Use when the user says "let's design X", "build a UI for Y", "get context", "clarify the brief", or kicks off any product-design task without a clear spec. First stage of the Product Design set — highest leverage for reducing rework.

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

Judge subskill for simmer. Scores a candidate artifact against user-defined criteria on a 1-10 scale and produces ASI (highest-leverage direction) for the next generator round. Supports judge-only, runnable evaluator, and hybrid evaluation modes. Do not invoke directly — dispatched as a subagent by the simmer orchestrator.

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

Use when mapping funnel-stage to content shape — conversion-pathway, content-as-system, leverage-point selection. Triggers on 'design our content funnel', 'why does mid-funnel leak'.

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

Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL. Translates Oracle-specific syntax, preserves method signatures and type-anchored parameters, leverages orafce where appropriate, and applies COLLATE "C" for Oracle-compatible text sorting. Use when converting Oracle stored procedures or functions to PostgreSQL equivalents during a database migration.

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

Use when writing, editing, or reviewing code, READMEs, docs, commits, changelogs, or any repo content. Pre-2020 human style — terse, opinionated, restrained, with project voice. Blocks the LLM tics (emoji headers, "leverage", "robust", "seamless", "delve", defensive bloat, type-hint overkill, marketing prose, "Whether you're X or Y", verbose error messages) catalogued from cpython, requests, flask, git, ripgrep, express, kubernetes, serde, and the Go stdlib. Triggers on "anti-ai", "human-style", "no slop", "write it like a human", or any time code/docs should look hand-written.

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

This skill covers detecting anomalies in Modbus/TCP and Modbus RTU communications in industrial control systems. It addresses function code monitoring, register range validation, timing analysis, unauthorized client detection, and deep packet inspection for malformed Modbus frames. The skill leverages Zeek with Modbus protocol analyzers, Suricata IDS with OT rules, and custom Python-based detection using Markov chain models for normal Modbus transaction sequences.

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

This skill covers detecting cyber attacks targeting Supervisory Control and Data Acquisition (SCADA) systems including man-in-the-middle attacks on industrial protocols, unauthorized command injection into PLCs, HMI compromise, historian data manipulation, and denial-of-service against control system communications. It leverages OT-specific intrusion detection systems, industrial protocol anomaly detection, and process data analytics to identify attacks that traditional IT security tools miss.

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

Leverages Splunk Enterprise Security and SPL (Search Processing Language) to investigate security incidents through log correlation, timeline reconstruction, and anomaly detection. Covers Windows event logs, firewall logs, proxy logs, and authentication data analysis. Activates for requests involving Splunk investigation, SPL queries, SIEM log analysis, security event correlation, or log-based incident investigation.

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

Reviews a proposal, business case, deck, plan or contract summary in character as a General Counsel archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage or clause, legal risks, what would change the verdict and five interrogation questions. Meeting preparation, not legal advice. Use when the user asks to "run a general counsel review", "what would legal say about this", "pressure-test the legal exposure in this deal" or "prepare me for the deal committee". Do not use for price, term, renewal or vendor leverage, use procurement-reviewer instead; for lawful basis and data flows, use cdo-reviewer; for security controls, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Shared vocabulary for designing deep modules, interfaces, seams, adapters, leverage, and locality. Use when designing or reshaping module boundaries, making code more testable, or evaluating interface depth.

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

This skill should be used when creating comprehensive project plans for system development or implementation projects. Use this skill when you need to create Project Charters, Project Plans, WBS, Gantt Charts, RACI matrices, Risk analysis, or other PMBOK-aligned project management artifacts. Outputs are in Markdown format with Mermaid diagrams for visualizations. Leverages comprehensive PM knowledge base in references/ directory (544KB, 11 files) including PMBOK standards, Software/SaaS best practices, IT industry guidance, and specialized PM methodologies.

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

Build leveraged buyout workbooks with IRR/MOIC in Excel.

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