“spike”的搜索结果

Analyze Neuropixels neural recordings with SpikeInterface, from loading and preprocessing to motion correction and spike sorting, which separates signals by neuron. Calculate quality metrics, review candidate units, and export plots and data for further inspection.

中文简介正在准备中。当前显示英语简介。

• Inspect and preprocess SpikeGLX, Open Ephys, or NWB recordings
• Check and correct movement-related drift before spike sorting
• Evaluate and select units using quality metrics

MUST USE for building FastAPI/REST API applications with Aerospike database (aerospike-py Rust/PyO3 async client). Covers AsyncClient lifespan management, FastAPI Depends injection, aerospike_py exception-to-HTTP-status mapping (RecordNotFound→404, RecordExistsError→409, BackpressureError→503, AerospikeTimeoutError→504), POLICY_EXISTS_CREATE_ONLY/UPDATE_ONLY for CRUD semantics, NamedTuple attribute access (record.bins not tuple unpacking), client.ping() readiness probe, batch_read returning dict, batch_write with in_doubt retry signal, and global AerospikeError handler. Triggers on: FastAPI + Aerospike, REST API + aerospike-py, CRUD API with Aerospike, client.ping() health probe, batch_read/batch_write endpoint, web server/HTTP service backed by Aerospike NoSQL, uvicorn + Aerospike.

中文简介正在准备中。当前显示原文说明。

Create Markdown documents for time-limited technical investigations before implementation. Define the decision to resolve, research tasks, success criteria, and deadlines, then record evidence, recommendations, and follow-up actions in a consistent structure.

中文简介正在准备中。当前显示英语简介。

• Investigating API capabilities before integration
• Comparing architecture options before implementation
• Planning experiments to check performance assumptions

Test an app idea through focused experiments and collect verified findings for development. It can also suggest what to explore next based on existing experiments and package findings as a reusable project skill.

中文简介正在准备中。当前显示英语简介。

• Testing whether an app idea is feasible
• Trying a specific feature before full development
• Choosing the next experiment from existing findings

Build ice and frost visual effects in Three.js using reusable modules. Combine branching frost growth, refractive ice spikes, cracks and settling fragments, freezing mist, and swirling snow into a coordinated sequence demonstrated on a snowy ground.

中文简介正在准备中。当前显示英语简介。

• Animate frost spreading across the ground
• Create erupting ice spikes that crack and shatter
• Combine freezing mist with a swirling blizzard

Neuropixels neural recording analysis. Load SpikeGLX/OpenEphys data, preprocess, motion correction, Kilosort4 spike sorting, quality metrics, Allen/IBL curation, AI-assisted visual analysis, for Neuropixels 1.0/2.0 extracellular electrophysiology. Use when working with neural recordings, spike sorting, extracellular electrophysiology, or when the user mentions Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, or unit curation.

中文简介正在准备中。当前显示原文说明。

[omh] Uncertain technical choice for a spike: bounded decision prototype workflow: resolve one uncertain interaction, API, performance, or integration choice with a disposable, isolated experiment whose observed result feeds planning. Use when the user says: decision-prototype, decision prototype, prototype this uncertain choice before planning, prototype before planning, prototype the uncertain choice, run a small spike, small spike, spike solution.

中文简介正在准备中。当前显示原文说明。

分布式训练梯度尖刺 (Gradient Spike) 根因定位。基于梯度监控数据 (trend.db/CSV)、 msprobe dump 统计数据，三阶段渐进式从异常坐标定位逐层深入到算子级根因。 当用户明确指明分析梯度尖刺问题时使用此 skill。 即便用户提供以上数据，但未指明分析梯度尖刺问题时，不可使用此skill。

中文简介正在准备中。当前显示原文说明。

Use when working with Aerospike — aerospike cluster management, namespace utilization, set analysis, and secondary index monitoring. Covers node health, storage engine statistics, migration tracking, UDF management, and XDR cross-datacenter replication status. Read this skill before any Aerospike operations.

中文简介正在准备中。当前显示原文说明。

MUST USE for deploying Aerospike on Kubernetes. Contains CE-specific YAML templates, validated AerospikeCluster CR examples, and critical constraints that prevent enterprise-only config mistakes (feature-key-file, security sections crash CE pods). Without this skill, deployments fail on first attempt due to CE 8.1 breaking changes (data-size not memory-size, no info port 3003) or webhook map/list shape rules (service/network must be maps; logging must be a list). Triggers on: deploy/create/set up Aerospike on K8s, kind, minikube, EKS, GKE; AerospikeCluster CR; ACKO operator; spec.operations / WarmRestart / PodRestart YAML; NoSQL database on Kubernetes. 9 ready-to-use YAML examples from minimal single-node to full-featured multi-rack.

中文简介正在准备中。当前显示原文说明。

Analyze access logs from AWS S3, GCS, and Azure Blob Storage to spot unusual downloads, unfamiliar IP addresses, and request spikes. Compare activity with normal patterns and prioritize findings for suspected data theft investigations.

中文简介正在准备中。当前显示英语简介。

• Investigating suspected data theft from cloud storage
• Finding bulk downloads outside normal working hours
• Checking unfamiliar IP addresses and sudden request spikes

Draft incident postmortems by aligning channel updates, GitHub deploys and merges, and Datadog spikes. It opens a review PR with a correlated timeline, proposed causes, and candidate follow-up actions for humans to confirm.

中文简介正在准备中。当前显示英语简介。

• Drafting a postmortem after an incident is resolved
• Comparing incident events with deploys and metric spikes
• Extending a draft when new evidence appears

Investigate a possible incident in Superset’s hosted services by checking deployments, error spikes, and service health. Produce a proposed severity and status page update for human review, without changing services or publishing messages.

中文简介正在准备中。当前显示英语简介。

• Investigating a reported Superset outage
• Checking the scope of a sudden increase in errors
• Drafting an incident severity and status page update

Normalizes ChIP-seq data using exogenous spike-in (ChIP-Rx with Drosophila chromatin per Orlando 2014 / Egan 2016; E. coli carryover for CUT&RUN/CUT&Tag). Distinguishes RRPM from Rx-Input scaling, integrates with DiffBind / DESeq2 / edgeR / csaw via sizeFactors and DiffBind library-size vectors, applies the Patel et al 2024 *Nat Biotechnol* failure-mode framework, and validates that normalization is applied at the read level (not peak counts). Use when global signal shifts are expected (HDACi, BETi, EZH2i, dosage, target knockdown), when ChIPseqSpikeInFree detects post-hoc shifts, or when validating internal-control regions before publication.

中文简介正在准备中。当前显示原文说明。

Write complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story or acceptance criteria, scope a spike, open an epic, or break work into tasks. Triggers on write a ticket, create an issue, file a bug, bug report, user story, spike, epic, task breakdown, turn this into tickets, break this down, acceptance criteria, definition of ready, ready for dev, backlog item, capitalization stage. Also triggers when the user pastes a PRD, a spec, or a bug description and asks what to do with it, even if they never say the word ticket.

中文简介正在准备中。当前显示原文说明。

Model-guided autonomous root-cause analysis over a UModel object-graph semantic layer. Use with `umodel-query` when diagnosing service degradation, SLO breach, latency/error spikes, incidents, outages, or questions like why a service is slow, degraded, erroring, or timing out. The skill guides evidence collection across object graph, metrics, logs, topology, runbooks, deployments, config changes, business traffic, and runtime capacity; it is especially useful for ruling out red herrings such as recent but unrelated deployments. Triggers: root cause, RCA, incident, SLO breach, outage, postmortem, latency spike, error spike, timeout, 根因分析, 故障排查, 告警定位, 为什么慢, SLO 击穿.

中文简介正在准备中。当前显示原文说明。

Internal harness probe for the OI-3 readability-guidance spike. Use only when explicitly told to invoke spike-probe. Verifies that a freshly-created project skill renders into a subagent's context via the Skill tool.

中文简介正在准备中。当前显示原文说明。

OI-3 spike harness — ADVERSARIAL inline guidance variant. Worst-case anchor: ends with a final-sounding completion statement and gives NO instruction to return to the caller. Use only when a spike consumer skill invokes it.

中文简介正在准备中。当前显示原文说明。

OI-3 spike harness — the FORKED (context fork) readability-guidance variant. Same payload as the inline variant but declared to run in a forked context. Use only when a spike consumer skill invokes it.

中文简介正在准备中。当前显示原文说明。

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

中文简介正在准备中。当前显示原文说明。

OI-3 spike harness — the INLINE (non-forked) readability-guidance variant. Surfaces the shared readability standard into the calling skill's own context. Use only when a spike consumer skill invokes it.

中文简介正在准备中。当前显示原文说明。

OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

中文简介正在准备中。当前显示原文说明。

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

中文简介正在准备中。当前显示原文说明。

OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

中文简介正在准备中。当前显示原文说明。