'stl' 검색 결과

Evaluate older Wi-Fi clients and embedded devices for KRACK and FragAttacks vulnerabilities. Covers test suites, likely patch status, practical impact, and reporting findings by device, firmware version, and vulnerability identifier.

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

• Assessing older Wi-Fi clients
• Reviewing IoT firmware patch status
• Distinguishing KRACK and FragAttacks impacts

Analyze GPU operation timings and execution traces to find costly data access, repeated computation, launch overhead, and synchronization waits. Check whether improving an individual operation actually reduces the time needed to complete a full request.

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

• Investigating slow GPU operations
• Assessing whether combining operations reduces data access
• Checking pipeline dependencies and buffer reuse

Build transfers and messaging between Solana and EVM chains with the deBridge Solana SDK. This development guide covers token transfers, destination contract calls, fee calculations, and checks that validate incoming transfer details.

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

• Build token transfers between Solana and EVM chains
• Send messages between blockchains
• Call a contract on the destination chain

Generate several separate solutions, compare them against criteria fixed in advance, and verify the selected result through executable checks or an independent reviewer. Keep a proof log documenting candidates, evidence, failures, and remaining limits.

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

• Comparing implementation options before choosing one
• Verifying a solution when a wrong choice would be costly
• Keeping evaluation evidence for delivery or audit

Analyze MSBuild binary logs and timing summaries to find why builds are slow. Identify costly reference resolution, code analysis, file copying, restore work, or serialized tasks, then prioritize improvements by their share of total build time.

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

• Investigate unexplained MSBuild slowness
• Measure code analysis and source generator overhead
• Find expensive reference resolution or file copying

Diagnose slow MSBuild startup by measuring project evaluation, the work done before compilation. Inspect logs for costly file searches, imported configuration, and repeated evaluations, then identify targeted changes supported by timing evidence.

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

• Investigating delays before compilation starts
• Checking file searches across large directories
• Analyzing deep import chains

Inspect TLS certificates, DNS records, and email authentication settings, then separate configuration advice from demonstrable vulnerabilities. The skill guides evidence collection and impact assessment for subdomain takeover, client certificate bypass, internal hostname exposure, and email spoofing.

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

• Review TLS certificates and encryption settings
• Assess DNS records for subdomain takeover
• Validate email spoofing evidence

Test CDN-backed websites for cache poisoning and Web Cache Deception, where private pages are mistakenly cached as public content. The skill guides cache behavior checks, input testing, and independent-client verification to establish reproducible impact.

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

• Reviewing cache behavior on CDN-backed websites
• Checking whether private pages enter public caches
• Verifying cached responses influenced by headers

Assess whether a multi-agent workflow justifies its coordination costs. Examine handoffs, lost context, and distinct contributions, then compare the setup with one capable agent to recommend keeping, simplifying, or restructuring it.

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

• Reviewing a workflow before adding another agent
• Finding costly handoffs in a slow workflow
• Checking whether agent agreement adds useful evidence

Read WeChat Official Account articles through available web or browser tools. Summarize the content actually accessed, check article details and relevant images, and clearly report reading limits, verification barriers, and claims that remain unverified.

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

• Summarize a WeChat article from its link
• Check the title, author, and publication date
• Inspect key images alongside the article

Find and improve slow React components while preserving interface behavior. It targets unnecessary renders, costly calculations, and long lists, then compares render counts and timings with baseline measurements using React DevTools Profiler.

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

• Investigating sluggish input and screen updates
• Reducing repeated renders caused by timers
• Improving long-list scrolling

Review completed work and its process against the original goals and acceptance criteria. Identify specific problems, root causes, and actionable fixes, while checking external criticism against evidence and correcting valid issues.

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

• Review deliverables before handing them over
• Reflect on work at a project checkpoint
• Check criticism and address valid points

[omh] Rust ownership, lifetime, or unsafe trouble: prepare Rust changes with ownership, error, and API discipline, and escalate any unsafe, FFI, or lock-free change to the UB checklist. Use when the user says: rust, rust code, rust skill, rustlang, borrow checker, lifetime error, ownership error, trait bound.

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

Amazon Redshift is NOT PostgreSQL; corrects LLM mistakes; covers SQL, metadata, connectivity/auth, storage, query performance, and operations. Applies ONLY to Redshift (provisioned or Serverless). Pushes back on: CREATE INDEX, string_agg, pg_catalog, text type, SERIAL, stl_query. Triggers on: Redshift SQL, Redshift CREATE TABLE, Redshift COPY/UNLOAD, slow or suddenly slow Redshift query, EXPLAIN plan, queue wait, stale statistics/ANALYZE, result cache, Redshift permission denied, Redshift disk full, storage growth, snapshot/backup cost, ghost rows/bloat, VACUUM, spill to disk, distribution skew, Redshift system views, QUALIFY, PIVOT, MERGE, materialized views, Redshift Data API (Python/boto3), Redshift workload management (WLM), concurrency scaling, Redshift resize, Spectrum, awsdatacatalog, connection failures (SSL/TLS, ODBC/JDBC, connection limit), IAM/SAML federation, IAM Identity Center, datashares. Does NOT apply to: S3 policies, Athena, Glue/Iceberg outside Redshift, Aurora, RDS, DynamoDB.

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

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product decision, or wants to de-risk a costly idea before investing in development. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday. For ongoing experimentation and MVPs, see lean-startup. For customer job analysis, see jobs-to-be-done. For non-leading user interviews, see mom-test.

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

Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick, influence-psychology, high-perf-browser, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, DESIGN.md, POSITIONING.md, IMPROVE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a clunky product, cut UX friction, sharpen in-app copy, or says 'the app works but feels rough'. Not for code, tests, or hardening - use improve-code-quality (fresh prototype) or remove-technical-debt (aged); no app yet, create-app; needs growth loops, grow-app; marketing-site friction, improve-website; one leaking flow, conversion-optimization. For one framework in isolation, invoke that skill directly.

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

Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.

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

Answers a business question with data without fooling yourself — framing the question so an answer would change something, choosing the right comparison, checking the data before trusting it, recognizing the traps that produce confident wrong answers (aggregation reversals, survivorship, regression to the mean, multiple comparisons), and reporting uncertainty honestly. Use this to run an analysis, review one before acting on it, or work out why two people looking at the same data reached opposite conclusions.

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

Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to design a customer success motion, decide who gets a named contact, work out why renewals surprise you, or fix a health score everyone ignores.

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

Clinical Research Bias Assessment - Case-Control Study (NOS) v2.3.0. Use when you need to assess the bias of a case-control study using the Newcastle-Ottawa Scale (NOS) criteria, or when evaluating the quality of a medical paper.

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

Evaluates the quality of cohort studies using the Newcastle-Ottawa Scale (NOS). Use when the user provides a cohort study article or text and needs a quality assessment report.

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

Analyzes 3D mesh files (STL) to calculate geometric properties (volume, components) and extract attribute data. Use this skill to process noisy 3D scan data and filter debris.

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

Read Microsoft Excel (.xlsx) files robustly with `openpyxl` (or `pandas`). Covers multi-sheet workbooks, header rows, empty cells, merged cells, comma-separated list cells, and converting a sheet to a list-of-dicts the rest of your code can consume. Use when a task input or reference document is an `.xlsx` file rather than JSON/CSV.

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

Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.

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