'tiering' 검색 결과

Use this skill when a company needs to decide how much assessment each supplier deserves, or asks "tier our vendors", "which suppliers are critical", "we have 200 vendors and cannot assess them all", "build a third-party risk tiering", "rank suppliers by risk" or "which vendors need a security review this year". Builds the complete supplier population from finance, single sign-on and contracts, scores each supplier on data, access and dependency, assigns a tier by the highest axis, sets the assessment depth and cycle per tier, and writes a tiered list with the reason for every score.

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

Expert third-party risk management (TPRM) advisor — a vendor risk analyst for the full lifecycle: risk-based vendor tiering, tailored due-diligence questionnaires (SIG-style or mapped to ISO 27001, SOC 2, DORA, NIS2, HIPAA), SOC 2 Type II report review (exceptions, carve-outs, CUECs, bridge letters), DPA and sub-processor review under GDPR Art. 28, contract security addenda (DORA Art. 30 provisions), ongoing monitoring programmes, and vendor offboarding. Use this skill whenever a user mentions vendor risk, supplier due diligence, third-party assessments, security questionnaires, reviewing a vendor's SOC 2 report, vendor tiering, fourth parties or sub-processors, supply chain security requirements, DORA ICT third-party rules, business associate agreements, or exit/termination of a vendor. Also trigger for 'a customer sent us a questionnaire' and 'how do I assess this vendor' style requests.

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

Tier vocabulary from a text or topic into everyday, academic, and technical categories with teaching priorities. Use when pre-teaching vocabulary or identifying language barriers in a text.

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

Build, run, and improve a Security Operations Center — alert prioritization, runbook authoring, escalation criteria, on-call structure, alert tuning workflow, MTTD / MTTR / fidelity KPIs, analyst tiering, and shift handoffs. Use when the user mentions 'SOC,' 'security operations,' 'SOC analyst,' 'alert triage workflow,' 'runbook,' 'escalation,' 'on-call,' 'SOC tiering,' 'tier 1 / tier 2,' 'MTTD,' 'MTTR,' 'alert fatigue,' 'alert tuning,' 'shift handoff,' 'SOAR,' or wants to design or improve a security operations team.

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

Vendor privacy risk tiering methodology for processor management. Covers scoring factors including data volume, sensitivity, transfer locations, certifications, breach history, and control maturity with weighted risk calculation and tier assignment.

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

Tier vocabulary from a text or topic into everyday, academic, and technical categories with teaching priorities. Use when pre-teaching vocabulary or identifying language barriers in a text.

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

Design cost reduction strategies — model tiering, prompt compression, caching, batch inference. Use when asked to "reduce our AI costs", "set up model tiering", or "cut LLM spend".

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

Usage-based pricing in Revenue Cloud: metered billing, usage records, rating, tiering, consumption schedules. NOT for choosing a CPQ pricing method (List, Block, Cost Plus Markup, Percent of Total) - use admin/pricing-model-design. NOT for legacy Salesforce Billing (blng__) schedules and invoice runs - use admin/billing-schedule-setup.

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

Use when designing and operating the in-app purchase catalog of a game — SKU design, price-tier ladder, bundles, starter packs, battle pass tiering, A/B price tests, store config (App Store / Google Play / Steam DLC / web / web3), and per-region price localization. Triggers on "IAP catalog", "store SKUs", "pricing tiers", "starter pack", "bundle design", "battle pass tiering", "price test", "price localization", "App Store Connect", "Google Play Console", "Steam DLC", or when handed a monetization strategy with the catalog still open. Produces a catalog spec, per-region price tables, bundle compositions, and a price-test plan. For in-game economy curves see game-balancer.

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

Find and qualify prospective customers for B2B, SaaS, local businesses, or early-stage products. Define target criteria, gather supporting sources, verify email contacts, and prioritize prospects in a lead sheet or an evidence report for first-customer discovery.

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

• Build a prioritized list of B2B prospects
• Find local businesses in a target area
• Discover first customers from public demand signals

Design a partner program by defining value for your company, partners, and shared customers. Provides frameworks for partner tiers, phased pilots, joint marketing, and build-versus-partner decisions, with explicit measures for expanding or ending a partnership.

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

• Designing partner tiers and support levels
• Deciding whether to build internally or partner
• Defining pilot metrics and expansion criteria

Score and group accounts by customer fit and engagement, such as recent contact and open sales opportunities. Identify where to focus sales effort, choose next actions, and spot promising accounts with neglected outreach or missing information.

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

• Prioritize a portfolio of assigned accounts
• Find strong-fit accounts that need outreach
• Identify promising accounts with no recent activity

Use when the user asks to "write influencer outreach", "follow up with a creator", "pitch a journalist, hunter, or launch partner", or "negotiate partnership terms"; produces personalized pitches, multi-touch follow-up sequences, negotiation scripts with objection handling, and a status pipeline tracker — the shared outreach mechanics engine for creator, media/analyst, launch-partner, and social-selling / advocate-recruitment targets. Not for finalizing signed agreements — use contract-helper; not for media-list tiering, embargo terms, or press-release structure — use press-media-relations. 达人邀约建联/合作谈判话术

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

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

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

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

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

DataOps and DS/MLOps testing reference for data tiering, Bronze-to-Silver validation placement, pipeline invariants, pytest categories, and validation-versus-drift. Use when designing, reviewing, or generating data pipelines, transformation code, data validation, or data-science test suites.

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

Codex-native Amazon PPC keyword research using LaunchFast MCP. Use when the user wants competitor keyword discovery, keyword tiering, or a ready-to-upload Amazon Sponsored Products bulk file from 1-15 ASINs. Requires the LaunchFast MCP tool `amazon_keyword_research`.

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

Rank and prioritize neoantigen/epitope candidates by likely T-cell response using NeoFox feature annotation, PRIME2.0, BigMHC-IM, the Łuksza/Balachandran fitness model (agretopicity + foreignness), and pVACtools tiering. Encodes the field's hard truths that immunogenicity is the least-solved layer (dedicated scores ~AUROC 0.6-0.7, modest PPV), that scores are valid only for RANKING within one patient (never absolute go/no-go or cross-patient), that DAI has anchor-inflation and WT-denominator traps, and that stacking weak correlated scores into one number is a red flag. Use when ordering a candidate list for a vaccine. Binding lives in mhc-binding-prediction; calling in neoantigen-prediction.

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

Assigns GO terms, Pfam/InterPro domains, KEGG orthologs, EC numbers, and product names to predicted proteins using eggNOG-mapper (orthology), InterProScan (domain signatures), and KofamScan (KEGG), routing specialized functions to dbCAN/antiSMASH/AMRFinderPlus/SignalP. Covers the orthology-vs-domain-vs-homology paradigms, the annotation-error percolation cascade, domain-presence-is-not-function, GO IEA circularity in enrichment, evidence tiering, and bit-score/coverage thresholds. Use when adding functional annotation to predicted genes, choosing between eggNOG-mapper and InterProScan, or judging how much to trust a functional label.

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

Prioritizes rare-disease variants from trio/quad WES/WGS with de novo (DeNovoGear, Triodenovo), compound-heterozygous phasing (WhatsHap), mosaic VAF tiering, phenotype-driven ranking (Exomiser, Phen2Gene, AMELIE), ClinGen gene-disease validity gating, and ACMG SF v3.2 secondary findings reporting. Use when running diagnostic exome / genome pipelines, identifying candidate Mendelian disease genes, screening for incidental findings, or auditing VUS reclassification cycles. The ACMG/AMP classification framework (PVS1 decision tree, Pejaver PP3/BP4 calibration, Tavtigian point system) is in clinical-databases/acmg-classification.

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

Calculates tumor mutational burden from WES/WGS/panel data with Friends of Cancer Research harmonization equations, per-assay calibration (FDA 10/Mb = 7.8 TSO500 = 8.4 OncomineTML), synonymous/indel/germline filtering, hypermutator tiering, blood TMB, and integration with HLA-LOH and neoantigen quality (Luksza 2017 fitness). Use when assessing ICI eligibility under tumor-specific cutoffs (McGrail 2021), comparing tissue vs bTMB, or auditing TMB-H reporting against ESMO 2024 and FDA pembrolizumab pan-tumor 2020.

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

Vendor lifecycle — weighted selection scorecards, risk tiering, renewal and notice-deadline tracking, spend concentration, and SLA credits. Use when selecting a vendor, preparing a renewal, or reviewing a vendor portfolio.

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

Panel structure design, firm selection criteria, right-sourcing analysis, and coverage gap assessment for in-house legal teams. Build panel frameworks from scratch or formalise existing informal arrangements. Define weighted selection criteria for firm evaluation. Run right-sourcing analysis (ABC tiering) to identify work sent to expensive providers that doesn't require that level of resource. Assess existing panels for practice area, geographic, and capability gaps. Trigger on: 'design our panel', 'how many firms do we need', 'panel structure', 'firm selection criteria', 'which firms should we use', 'right-sourcing', 'are we sending work to the right firms', 'panel gaps', 'too many firms', 'consolidate our panel', 'we need a firm for', 'preferred provider', 'panel tiers', 'do we need BigLaw for this', 'convergence', 'D&I panel targets', 'how do we choose firms'.

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

Expert knowledge for Azure Files development including best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when using Azure File Sync, cloud tiering, SMB/NFS shares, RAG over Azure Files, or Storage Mover/Data Box, and other Azure Files related development tasks. Not for Azure Blob Storage (use azure-blob-storage), Azure NetApp Files (use azure-netapp-files), Azure Managed Lustre (use azure-managed-lustre).

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