9천건 · 관련도순
Detect allele-specific chromatin accessibility from ATAC-seq using WASP, GATK ASEReadCounter, or RASQUAL. Use when mapping cis-regulatory genetic variants from heterozygous SNPs, separating cis from trans regulation, building chromatin QTL (caQTL) maps, validating GWAS variant function with allelic imbalance, or detecting reference allele mapping bias before downstream analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trim multiple sequence alignments using ClipKIT, trimAl, BMGE, Divvier, or HMMcleaner with mode selection guidance per downstream goal. Use when removing unreliable columns or contaminating residues before phylogenetic inference, HMM building, or selection analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks the cost of pulling a Motor Vehicle Record (MVR) in a specific state, or wants to compare MVR fees across multiple states, or is budgeting annual compliance costs for a multi-state fleet. Reference the canonical fee table below; flag that fees change (re-verify with state DMV before annual budget planning).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when buying a used tractor or trailer. Covers verifying compliance status, hidden issues, and what to inspect before signing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a carrier asks about the full pre-employment investigation process for new CDL drivers under 49 CFR 391.23, 391.25, 391.27, 382.413, and 391.21 — the complete file build required before a driver operates a CMV. Covers application, MVR, employment history, drug/alcohol history, PSP, Clearinghouse, road test, and documentation requirements.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about onboarding a new CDL driver — pre-hire process, day-zero requirements, application + DQF setup, road test, drug & alcohol pre-employment, Clearinghouse Full query, MVR initial pull, PSP report, ELDT verification, sequence of activities + timing, and what NOT to do (handing keys before testing complete). Cite 49 CFR 391, 382.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when conducting a self-audit of your DQF library before an FMCSA compliance review. Covers the systematic approach to verifying all 12 documents are current, complete, and properly maintained.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to run an internal audit before FMCSA does. Covers what to check, common gaps, and remediation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for sensemaking, frame revision, anomaly handling, questioning strategy, and ambiguity diagnosis with the Data/Frame model before action is chosen. NOT for deterministic classification, settled execution planning, or situations where the frame is already stable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Classify every destructive/gated action an agent body can attempt (git, filesystem, network, shell, github) into block/approve/allow tiers, and audit whether the pre-tool and post-tool governance backing that classification is real: blocked actions proven zero-side-effect by a negative fixture, every denial backed by a receipt and a transcript event, every block-tier denial paired with a safe alternative, and no unmanaged or same-UID body ever marked "contained." Use when building or reviewing Agent Harbor's C5 governance gate (destructive git blocker, approval request/result, denial receipts), gating a new tool surface before it can run destructive commands, or auditing whether an existing "destructive-action blocked" claim actually has evidence behind it. NOT for proving an existing sandbox boundary actually contains an adversary once an action is isolated (use sandboxed-adversarial-test-harness), deciding where in a DAG to place a human review node or designing the approval UX itself (use human-gate-designer), or designing the general work-receipt schema across an entire agent task (use agent-work-receipt-designer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan database migrations before executing them: risk assessment, dependency mapping, multi-service sequencing, rollback budgets, and stakeholder communication plans. Use when deciding HOW to migrate, not when writing the actual DDL. NOT for: writing migration SQL (use database-migration-manager), data ETL pipelines (use data-migration-specialist), query optimization, or ORM configuration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Conduct Critical Decision Method (CDM) interviews to elicit expert reasoning strategies (L3 knowledge) from practitioners about specific challenging past incidents. Use when capturing expertise for skill development, preserving knowledge before practitioner departure, building post-incident learning artifacts, or investigating decisions in complex sociotechnical systems. Outputs structured incident reconstructions with cues, decisions, alternatives considered, and counterfactual analysis suitable for distillation into skills or training material.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Treat tokens as a coding swarm's cost-of-goods-sold and legibility engine while accounting for finite subscription allowance when per-call price is unknown. Covers provider windows, remaining-usage evidence, burn forecasts, preemptive checkpoint/model switching, per-agent budgets, compaction, shared digests, context degradation, and spend metering. Activate on: "token budget", "context budget", "compaction strategy", "briefing as compression", "context rot", "summarization collapse", "COGS for agents", "subscription usage remaining", "five-hour or weekly limit", "burn forecast", "model switch before limit", or "/context-economics-for-agent-swarms". NOT for: memory architecture (use always-on-agent-architecture), single-prompt wording (use prompt-engineer), mechanism-design proofs (use nisan-et-al-2007-algorithmic-game-theory), physical containment (use sandboxed-adversarial-test-harness), or production rebodiment and fencing (use agent-resurrection-and-body-continuity).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor apps so backend owns runtime truth and UI only projects snapshots. Use when tools have split authority. NOT for cosmetic UI work or new features before drift is removed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verifies build output integrity after code changes. Runs builds, validates artifact structure, checks for regressions in bundle size, asset references, and static export completeness. The last line of defense before a bad deploy ships.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verify every visual-evidence artifact (screenshot/GIF/recording) attached to a PR carries a provenance manifest binding it to real daemon-backed truth — daemon port, run id, transcript head hash, agent node id, commit, and an honest real/fixture/mock source label — and that operator-control-panel PRs cover the required set of proof states. Use when gating a PR's proof artifacts before merge, auditing whether a "LIVE" visual claim is backed by a real daemon run versus a reused or fixture-backed mock, or defining the required state-coverage set for a control-panel change. NOT for the capture technique itself — headless Playwright, `screencapture -x -l`, non-interruptive capture (use port-daddy-agent-skill's visual-evidence doctrine), designing the receipt body schema an artifact attaches to (use agent-work-receipt-designer), or the broader dogfood/Potemkin product-quality bar (use multi-agent-authoring-product-bar).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discipline an AI agent needs to work an issue/task tracker (Jira, Linear, GitHub Issues) as the shared source of truth: pull the right next item instead of inventing work, search before creating to avoid duplicates, write actionable items with checkable acceptance criteria, keep status transitions honest, and link work to items via branches/PRs/commits so progress is legible. Use when an agent picks up tracker work, files a new issue, updates status, or closes an item. NOT for authoring the PR itself (use agent-pr-authoring), roadmap-level planning and prioritization (use legible-roadmap-with-sidequests), or the mechanics of multiple agents coordinating on the same codebase (use multi-agent-coordination).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Declare an agentic application's interaction disclosure, state, context, capabilities, and effect-control boundaries. Use for a reviewable design specification and static consistency audit before implementation. NOT for proving that controls are deployed or enforced, exposing private chain-of-thought, selecting a model/router, or designing a multi-agent protocol.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Comprehensive overview of ALL Coval platform resources, their hierarchy, relationships, API endpoints, and ID formats. Use when user asks about Coval resources, data model, how things relate, what endpoints exist, or needs context about the platform structure before making API calls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Compare before/after Coval runs using matched cases, stable metric versions and inspected conversation evidence. Use to assess a regression or proposed improvement; does not automatically launch or tune anything.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the full static analysis suite — ruff lint, ruff format check, pyright type check, auth analysis, license headers, example.env check. Use before committing or to verify code quality after changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SEO drift monitoring: capture baselines of SEO-critical elements, detect changes, and track regressions over time. Git for SEO: baseline, diff, and track changes to your on-page SEO. Use when user says "SEO drift", "baseline", "track changes", "did anything break", "SEO regression", "compare SEO", "before and after", "monitor SEO changes", or "deployment check".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.