'dora' 검색 결과

ordercli로 Foodora 주문 내역과 진행 중인 주문의 상태, 도착 정보를 확인합니다. 주문을 계속 모니터링하고 상세 정보를 조회하며 이전 주문 상품을 장바구니에 추가합니다.

• 주문 상태와 도착 정보를 확인합니다
• 진행 중인 주문을 계속 모니터링합니다
• 이전 주문 상세 정보를 JSON으로 받습니다

Diagnose Fedora Linux problems with a structured troubleshooting plan. Get commands for checking services, logs, and packages, followed by remediation, validation, and rollback steps that account for SELinux and firewalld where relevant.

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

• Investigating a service that will not start
• Troubleshooting package-related problems
• Checking SELinux or firewall involvement

Expert DORA (Regulation (EU) 2022/2554 — Digital Operational Resilience Act) compliance advisor for EU financial entities. Use this skill whenever a user asks about DORA compliance, ICT risk management frameworks, ICT incident classification or reporting, threat-led penetration testing (TLPT), ICT third-party risk management, Register of Information, contractual provisions with ICT providers, ICT concentration risk, oversight of critical ICT third-party service providers (CTPPs), or any DORA RTS/ITS obligation. Also trigger for: "DORA gap analysis", "DORA readiness", "Art. 6 ICT risk framework", "Art. 17 incident reporting", "Art. 26 TLPT", "Art. 28 third-party policy", "Art. 30 contractual provisions", "Register of Information CIR 2024/2956", "critical TPSP designation", "DORA vs NIS2", "DORA simplified framework", or EBA/ESMA/EIOPA digital resilience guidance.

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

Expert DORA (Regulation (EU) 2022/2554 — Digital Operational Resilience Act) compliance advisor for EU financial entities. Use this skill whenever a user asks about DORA compliance, ICT risk management frameworks, ICT incident classification or reporting, threat-led penetration testing (TLPT), ICT third-party risk management, Register of Information, contractual provisions with ICT providers, ICT concentration risk, oversight of critical ICT third-party service providers (CTPPs), or any DORA RTS/ITS obligation. Also trigger for: "DORA gap analysis", "DORA readiness", "Art. 6 ICT risk framework", "Art. 17 incident reporting", "Art. 26 TLPT", "Art. 28 third-party policy", "Art. 30 contractual provisions", "Register of Information CIR 2024/2956", "critical TPSP designation", "DORA vs NIS2", "DORA simplified framework", or EBA/ESMA/EIOPA digital resilience guidance.

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

Use this skill when a bank, payment or e-money institution, investment firm, insurer, crypto-asset service provider or other financial entity in scope of DORA needs to know whether its ICT risk management setup holds up, or when someone asks "DORA gap analysis", "are we DORA compliant on ICT risk", "check our ICT risk management framework", "prepare for the supervisor's DORA review", "does our ISO 27001 ISMS cover DORA" or "audit our Article 6 framework". Confirms the entity type and whether the simplified regime applies, maps the entity's own documents and records against the ICT risk management articles, and writes a gap list with owners, evidence and priorities.

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

Review engineering delivery plans, hiring proposals, and team changes through six operational questions. Assess delivery metrics, recruitment stages, management structure, and production practices, then produce a verdict and three concrete actions to address the findings.

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

• Reviewing quarterly delivery commitments
• Checking an engineering hiring plan
• Assessing a proposed team reorganization

Detects m6A modifications from Oxford Nanopore direct-RNA-seq (DRS) signal using m6Anet (multiple-instance-learning over DRACH 5-mer signal). Covers the upstream pipeline (Dorado/Guppy basecalling -> minimap2 map-ont -> nanopolish eventalign -> m6anet dataprep -> m6anet inference), per-site vs per-read probability including the mod_ratio stoichiometry column, the DRACH-only constraint, minimum-coverage thresholds (20-50 reads/site), multi-condition comparison via xPore/Nanocompore/ELIGOS, Dorado native modification calling (RNA004, 2024+), and the cDNA-vs-DRS distinction (cDNA Nanopore CANNOT detect modifications). Use when calling m6A from ONT DRS without immunoprecipitation, choosing m6Anet vs xPore vs Nanocompore vs ELIGOS vs Dorado native, interpreting probability_modified vs mod_ratio vs per-read probabilities, deciding between m6Anet (known DRACH sites) and Dorado/Remora (genome-wide screening), pinning RNA002 vs RNA004 chemistry and basecaller versions, or troubleshooting eventalign/dataprep failures.

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

DORA (EU 2022/2554) digital operational resilience compliance for financial entities, covering all 5 pillars. Use for DORA readiness assessments, ICT risk management, incident classification, and third-party ICT oversight.

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

Detects m6A modifications from Oxford Nanopore direct-RNA-seq (DRS) signal using m6Anet (multiple-instance-learning over DRACH 5-mer signal). Covers the upstream pipeline (Dorado/Guppy basecalling -> minimap2 map-ont -> nanopolish eventalign -> m6anet dataprep -> m6anet inference), per-site vs per-read probability including the mod_ratio stoichiometry column, the DRACH-only constraint, minimum-coverage thresholds (20-50 reads/site), multi-condition comparison via xPore/Nanocompore/ELIGOS, Dorado native modification calling (RNA004, 2024+), and the cDNA-vs-DRS distinction (cDNA Nanopore CANNOT detect modifications). Use when calling m6A from ONT DRS without immunoprecipitation, choosing m6Anet vs xPore vs Nanocompore vs ELIGOS vs Dorado native, interpreting probability_modified vs mod_ratio vs per-read probabilities, deciding between m6Anet (known DRACH sites) and Dorado/Remora (genome-wide screening), pinning RNA002 vs RNA004 chemistry and basecaller versions, or troubleshooting eventalign/dataprep failures.

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

Diagnoses and fixes Fedora Linux problems with Fedora tooling: dnf, systemd, journalctl, and SELinux-aware guidance. Use when a Fedora system has package, service, boot, or permission issues.

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

Detects m6A modifications from Oxford Nanopore direct-RNA-sequencing (ONT DRS) signal data using m6Anet (Hendra 2022 *Nat Methods* 19:1590; multiple-instance-learning neural network over DRACH 5-mer signal). Covers the required upstream pipeline (Dorado / Guppy basecalling -> minimap2 transcriptome alignment with `-ax map-ont -uf -k14 --secondary=no` -> nanopolish eventalign with `--scale-events --signal-index` (m6Anet-required) plus `--summary` / `--threads` housekeeping -> m6anet dataprep -> m6anet inference), per-site vs per-read probability interpretation including the `mod_ratio` per-site stoichiometry column, the DRACH-only modeling constraint, minimum-coverage thresholds (20-50 reads per site for stable probability estimates), multi-condition comparison via xPore (Pratanwanich 2021 *Nat Biotechnol* 39:1394), Nanocompore (Leger 2021 *Nat Commun* 12:7198), ELIGOS (Jenjaroenpun 2021 *NAR* 49:e7), and Dorado native modification calling (RNA004 chemistry, 2024+), reference-transcriptome version pinning, the cDNA-vs-DRS chemistry distinction (cDNA-Nanopore CANNOT be used for modification detection), and orthogonal validation against MeRIP / GLORI. Use when calling m6A from ONT DRS without immunoprecipitation, choosing m6Anet vs xPore vs Nanocompore vs ELIGOS vs Dorado native, interpreting per-site `probability_modified` vs `mod_ratio` vs per-read modification probabilities, comparing methylation between conditions from ONT data, deciding between m6Anet for known DRACH sites and Dorado/Remora for genome-wide screening, pinning RNA002 vs RNA004 chemistry and basecaller model versions, or troubleshooting eventalign / dataprep failures.

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

Detects m6A modifications from Oxford Nanopore direct-RNA-sequencing (ONT DRS) signal data using m6Anet (Hendra 2022 *Nat Methods* 19:1590; multiple-instance-learning neural network over DRACH 5-mer signal). Covers the required upstream pipeline (Dorado / Guppy basecalling -> minimap2 transcriptome alignment with `-ax map-ont -uf -k14 --secondary=no` -> nanopolish eventalign with `--scale-events --signal-index` (m6Anet-required) plus `--summary` / `--threads` housekeeping -> m6anet dataprep -> m6anet inference), per-site vs per-read probability interpretation including the `mod_ratio` per-site stoichiometry column, the DRACH-only modeling constraint, minimum-coverage thresholds (20-50 reads per site for stable probability estimates), multi-condition comparison via xPore (Pratanwanich 2021 *Nat Biotechnol* 39:1394), Nanocompore (Leger 2021 *Nat Commun* 12:7198), ELIGOS (Jenjaroenpun 2021 *NAR* 49:e7), and Dorado native modification calling (RNA004 chemistry, 2024+), reference-transcriptome version pinning, the cDNA-vs-DRS chemistry distinction (cDNA-Nanopore CANNOT be used for modification detection), and orthogonal validation against MeRIP / GLORI. Use when calling m6A from ONT DRS without immunoprecipitation, choosing m6Anet vs xPore vs Nanocompore vs ELIGOS vs Dorado native, interpreting per-site `probability_modified` vs `mod_ratio` vs per-read modification probabilities, comparing methylation between conditions from ONT data, deciding between m6Anet for known DRACH sites and Dorado/Remora for genome-wide screening, pinning RNA002 vs RNA004 chemistry and basecaller model versions, or troubleshooting eventalign / dataprep failures.

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

Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.

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

• Prioritizing technical debt reduction
• Planning hiring and engineering team structure
• Comparing technologies and vendors

Assess startup engineering operations across delivery, hiring, team structure, and production practices. Use delivery metrics, hiring conversion rates, and staffing data to identify bottlenecks, estimate candidate needs, and plan management roles and operational improvements.

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

• Find where development work waits before release
• Estimate candidate volume needed for hiring goals
• Review team structure and manager hiring needs

Plan technology investments and engineering team growth using structured assessments. Evaluate technical debt, compare building versus buying, document architecture choices, and define engineering health metrics to produce prioritized plans grounded in costs, risks, and business needs.

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

• Prioritize technical debt fixes by impact and effort
• Plan engineering hiring, timing, and budget
• Compare building internally with buying a service

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.

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

Risk-based vendor assessment framework for IT service providers, technology vendors, and third-party partners under DORA, NIS2, GDPR. Provides three-phase process (Initial Screening / Detailed Assessment / Final Evaluation), six-dimension risk scoring (Financial/Operational/Compliance/Security/Reputational/Strategic) with weighted matrices, full DORA Art. 28-30 contractual checklist, NIS2 Art. 21(2) security measures enumeration, GDPR Art. 28 documentation checks, red flags per dimension, trigger-based review criteria, and document templates. Use when: (1) Evaluating new vendors or technology providers, (2) Conducting critical ICT third-party due diligence under DORA, (3) Performing supply chain security assessment under NIS2, (4) Creating vendor onboarding documentation, (5) Establishing ongoing vendor monitoring, (6) Assessing concentration risk, or (7) Generating executive vendor risk reports.

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

Use when reviewing, designing, or modifying Java enterprise systems that may support financial entities, critical ICT services, third-party ICT provider integrations, or operational resilience obligations under DORA. This should trigger for requests such as Review a Java platform for DORA ICT risk controls; Design operational resilience evidence for a financial service; Add incident, continuity, backup, recovery, or third-party ICT controls; Assess resilience testing and monitoring before production release. Part of Plinth Toolkit

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

Computes DORA delivery-performance metrics from git and GitHub API. Use when assessing deployment frequency, lead time, or change failure rate.

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

Especialista em criar ferramentas geradoras compartilháveis que viralizam - geradores de nomes, criadores de quiz, criadores de avatares, testes de personalidade e ferramentas de calculadora. Abrange a psicologia do compartilhamento, mecânicas virais e construção de ferramentas que as pessoas não conseguem resistir em compartilhar com amigos. Use quando: ferramenta geradora, criador de quiz, gerador de nomes, criador de avatares, ferramenta viral.

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

Use this skill when a financial entity in scope of DORA needs to build or refresh its register of ICT third-party arrangements, and someone asks "build our register of information", "list our ICT providers for the regulator", "which providers support critical or important functions", "refresh the DORA register", "map our ICT contracts to functions" or "where is our provider concentration". Builds the population of ICT arrangements including intra-group ones, maps each to the functions it supports, collects the fields a supervisor will ask about, flags concentration, missing exit plans and contract gaps, and writes a working register with open questions for function owners.

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

Run OpenShell’s Release Canary checks to verify that published development packages and Helm charts install and support basic sandbox operations. Use workflow logs and local Kubernetes reproduction steps to investigate failures before a public release.

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

• Checking published development artifacts before release
• Testing changes to the Release Canary workflow
• Investigating installation or sandbox test failures

Convert raw Nanopore signal data (FAST5/POD5) to nucleotide sequences using Dorado basecaller. Covers model selection, GPU acceleration, modified base detection, and quality filtering. Use when processing raw Nanopore data before alignment. Guppy is deprecated; use Dorado for all new analyses.

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

Basecalls raw Oxford Nanopore signal (POD5/FAST5) into reads with Dorado, choosing the chemistry-matched model and accuracy tier (fast/hac/sup), requesting modified bases (5mCG_5hmCG, 6mA, m6A) at basecall time, and handling duplex, demultiplexing, trimming, and HERRO read correction. Covers why the model+version is an irreversible analysis decision, why methylation cannot be recovered later, and why downstream polish/variant models must match the basecaller. Use when converting POD5/FAST5 to reads, picking a Dorado model for R9/R10 or RNA004, enabling methylation calling, basecalling duplex, demultiplexing barcoded runs, or correcting reads for assembly.

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