582건 · 관련도순
Parse and analyze multiple sequence alignments using Biopython. Extract sequences, identify conserved regions, analyze gaps, work with annotations, and manipulate alignment data for downstream analysis. Use when parsing or manipulating multiple sequence alignments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate protein designs using AlphaFold2 structure prediction. Use this skill when: (1) Validating designed sequences fold correctly, (2) Predicting binder-target complex structures, (3) Calculating confidence metrics (pLDDT, pTM, ipTM), (4) Self-consistency validation of designs, (5) Multi-chain complex prediction with AlphaFold-Multimer. For faster single-chain prediction, use esm. For QC thresholds, use protein-qc.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Call this skill when faced with "wicked problems", complex challenges, or when a user asks for strategic innovation, root-cause analysis, or long-term problem solving. Do not use for simple, linear tasks. This skill forces the agent to bypass superficial symptoms, map the entire ecosystem, and anticipate second-order consequences before proposing an intervention.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate production-ready manga pages, chapter pages, covers, and panel sequences with strict recurring-character consistency. Use this when the user asks for a manga page, manga scene, chapter page, comic page, storyboard page, or character-consistent page generation. Before generating any page, inspect `img-memory`, create missing character sprites/reference sheets, make those images visible to image generation, then generate the final manga page.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Multi-angle review of responses before delivery. Audits from 4 perspectives -- factual accuracy, logical consistency, completeness, and safety. Use for high-stakes responses where errors have real consequences.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write scripts and programs against gatOS — the KSA mod that exposes live Kitten Space Agency simulation state as a 9P filesystem at /sim (also over HTTP /v1, MQTT, and an AI-oriented MCP server). Use this when asked to read game/celestial/vehicle telemetry, control vehicles (throttle, ignite, staging, attitude, burns, RCS, lights, docking), use game/debug controls (teleport, impulse kick, refuel, time-warp, switch vessel), direct the in-game camera / author cinematic shots and tracks, schedule timed command sequences, or write flight-computer / autopilot programs. Covers the full /sim catalog, the command model, KSA coordinate frames, and worked Bun/TypeScript + Rust examples.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Learn from consequences, not instructions — generate and enforce constraints from experience.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level real analysis knowledge. Use when working with limits, continuity, differentiability, Riemann and Lebesgue integration, sequences and series of functions, metric spaces, measure theory, or functional analysis foundations. Also use when the user mentions 'epsilon-delta', 'uniform continuity', 'uniform convergence', 'Lebesgue integral', 'measure theory', 'sigma-algebra', 'Banach space', 'Hilbert space', 'completeness', 'compactness', 'Heine-Borel', or 'dominated convergence'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Go / no-go gate before any deployment. Checks failure modes, rollback plan, cost, production bar, and definition of done. Trigger before releasing to any environment that carries real consequences.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this Canvas-owned clean-room skill when working with Remotion or React-based video generation. Trigger for Remotion projects, compositions, sequences, frame-based animation, rendering, captions, audio, video assets, templates, and debugging programmatic video output.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Discipline for repairing a false claim once it has propagated: select what depends on it, produce a replacement, and accept with an expiring verdict. Trigger when: - A claim, citation, premise, or documented fact is found wrong and its downstream consequences must be traced and fixed. - A refutation, a failed re-run, a retracted external source, or a human correction lands against something already closed or already promoted. - Prompt contains: /remediation, remediation, retraction, false claim, propagated error, scrub, correction propagation, born-false, became-false, currency verdict, impeachment queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts an architecture or design decision record (ADR) from the discussion notes, design review minutes, chat threads and diagram descriptions the user provides: context, decision drivers, options considered with arguments as stated, the decision as the group worded it, consequences and a review date, with every factual claim tagged evidenced, asserted or UNKNOWN so unsupported claims are marked for the author to substantiate. Use when the user asks to "write an ADR", "document the architecture decision", "record why we chose this design", "turn these design review notes into a decision record" or "draft the design decision log entry". Do not use for a business or governance decision with no technical design, use decision-memo-builder instead; for the change ticket that implements the decision, use change-request-pack. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
C4モデル レベル1 シーケンス図の新規作成・更新・レビューを支援する。C4モデル レベル1 の登場要素(アクター・対象システム・外部システム)だけを用い、ユースケースごとに 1 本の Mermaid シーケンス図を描く D2 成果物。ユースケース一覧・C4モデル レベル1(システムコンテキスト)・機能一覧の整備後に呼び出す。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate production-quality Excalidraw architecture diagrams from natural language. Visual structure maps to conceptual structure — fan-out for one-to-many, timelines for sequences, convergence for aggregation. Includes self-validation via Playwright render review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, build, or optimize SMS or MMS marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS. Also use when the user mentions "SMS marketing," "text message campaigns," "SMS sequence," "SMS automation," "abandoned cart text," "post-purchase SMS," "Klaviyo SMS," "Postscript," "Attentive," "Twilio," "A2P 10DLC," "TCPA," "SMS compliance," "short code," "toll-free SMS," "MMS campaign," "should I do SMS," or "SMS vs email." For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "set up my founder social-selling routine", "build a daily engagement block for target accounts", or "turn funding / hiring signals into selling plays"; produces the founder/seller daily operating block — a time-boxed engagement-block spec (substantive value-add comments on target-account posts, never a pitch), warm-touch-before-ask cadence rules, trigger-response plays consuming the social-pulse-monitor B2B trigger watchlist (funding / hiring / launch signals), and a quarterly diagnostic that reads LinkedIn SSI as an input diagnostic only (Estimated, vendor-defined — never a target metric). All volume norms are Estimated/community-derived; all execution is human — zero mass-DM, zero connection-request automation, zero engagement automation (LinkedIn UA §8.2 red line); 1:1 pitch and DM mechanics route to outreach-manager. Not for cold email sequences — use cold-outbound-sequencer. 社交销售/创始人日常互动块/热身触达节奏/触发信号剧本
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "build battle cards", "prep the sales team for launch", or "write the internal launch FAQ"; produces the internal enablement kit for a sales-led launch — battle cards vs each named alternative (where we win / where they win / trap questions, every fact traceable), a sales talk track derived from the PR-FAQ spine, an objection-handling table (objection → response → evidence), internal FAQ + CS macros, and an internal launch announcement with embargo discipline. Not for the external message house — use message-house-builder; not for competitor tracking itself — use competitor-tracker or competitor-analysis; not for outbound sequences — use cold-outbound-sequencer. 销售赋能/battle card/销售叙事/异议处理/内部FAQ
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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. 达人邀约建联/合作谈判话术
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design lifecycle email programs and sequences with segmentation, deliverability, personalization, testing and measurement.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.