CtrlK
BlogDocsLog inGet started
Tessl Logo

neuropixels-analysis

End-to-end Neuropixels extracellular electrophysiology analysis (SpikeGLX/Open Ephys/NWB) including preprocessing, motion correction, Kilosort4 spike sorting, QC metrics, and Allen/IBL-style curation; use when processing Neuropixels recordings or when users mention Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, drift/motion correction, or unit curation.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Data Analysis/neuropixels-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and largely actionable with a complete example script, but suffers from redundancy between Key Features and Implementation Details, a missing validation/feedback loop for batch operations, and broken reference paths that undermine navigation to the otherwise well-organized bundle.

Suggestions

Fix the reference paths from `reference/` to `references/` and convert them to markdown links (e.g., [PREPROCESSING.md](references/PREPROCESSING.md)) so navigation resolves; also reference the unlinked ANALYSIS.md or remove it from the bundle.

Add explicit validation/verification checkpoints after batch operations — e.g., verify the Phy export folder and NWB file exist and are loadable after `si.export_to_phy` / `export_to_nwb`, with a fix-and-retry loop on failure — to lift workflow clarity above the batch-operation cap of 3.

Merge the "Key Features" bullets into "Implementation Details" (or vice versa) to remove the duplicated pipeline walkthrough and tighten conciseness, and add `neuropixels_analysis` (the `npa` wrapper) to the Dependencies section or clarify how it is provided so the example is fully runnable.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific guidance, but the "Key Features" section and the "Implementation Details" section walk the same pipeline in parallel, and there are a few explanatory asides ("Motion/drift can strongly degrade sorting quality") that could be trimmed; merging the two walkthroughs would tighten it, but it is not padded with concepts Claude already knows (which would warrant a 2).

3 / 5

Actionability

Provides a largely executable, copy-paste-oriented script with real SpikeInterface calls and specific function/parameter names, but the example imports `neuropixels_analysis as npa` — a wrapper not listed in the Dependencies section and not established as installable — leaving a minor gap that keeps it below a 5.

4 / 5

Workflow Clarity

Steps are clearly numbered and sequenced (1–8 in the example, 1–7 in Implementation Details) with one conditional checkpoint (drift > 10 µm), but the batch operations (sorting, curation labeling, Phy/NWB export) lack validation/verification or fix-and-retry feedback loops, so per the batch-operation cap workflow clarity cannot exceed 3.

3 / 5

Progressive Disclosure

Good overall structure (overview SKILL.md plus 10 reference files, 6 scripts, 1 asset) with a dedicated reference list, but the body cites `reference/` (singular) while the bundle directory is `references/` (plural) so the paths do not resolve, references are backtick spans rather than navigable links, and `ANALYSIS.md` exists in the bundle but is never referenced — references are present but not correctly signaled.

3 / 5

Total

13

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality description that concretely states capabilities and gives explicit, natural trigger guidance covering both what and when. The only gap is the absence of explicit file extensions, which keeps trigger-term quality just short of perfect.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "preprocessing, motion correction, Kilosort4 spike sorting, QC metrics, and Allen/IBL-style curation" — plus supported formats (SpikeGLX/Open Ephys/NWB), giving comprehensive coverage rather than the minor gaps of a 4.

5 / 5

Completeness

Explicitly answers both what ("End-to-end ... analysis ... including preprocessing, motion correction, Kilosort4 spike sorting, QC metrics, ... curation") and when ("use when processing Neuropixels recordings or when users mention Neuropixels, SpikeGLX, Open Ephys, Kilosort, quality metrics, drift/motion correction, or unit curation") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural-term coverage with synonyms ("drift/motion correction") and format names (SpikeGLX, Open Ephys, NWB), but no explicit file extensions (e.g., .nwb, .ap.bin), which is part of the anchor-5 criterion, so it sits at a strong 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

A clear specialized niche (Neuropixels ephys analysis) with distinct triggers (SpikeGLX, Kilosort, drift/motion correction, unit curation) and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aipoch/medical-research-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.