Derived from arXiv:2606.22925 - EEG Benchmarking Needs a Task Specification Layer: NeuroDoc for Rulebook-Guided, Executable Benchmark Construction
Scanned 9/11/2026
Install to Claude Code
Skills Directorynpx -y skills add hiyenwong/ai_collection --skill eeg-benchmarking-needs-a-task-specification-layer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Eeg Benchmarking Needs A Task Specification Layer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hiyenwong-eeg-benchmarking-needs-a-task-specification-layer)More formats (shields.io, HTML) on the badges page.
# EEG Benchmarking Needs a Task Specification Layer: NeuroDoc for Rulebook-Guided, Executable Benchmark Construction
Derived from arXiv:2606.22925 - EEG Benchmarking Needs a Task Specification Layer: NeuroDoc for Rulebook-Guided, Executable Benchmark Construction
## Core Concept
Electroencephalography (EEG) foundation models increasingly rely on multi-dataset training and evaluation, yet public EEG datasets still lack a shared task specification layer that can turn heterogeneous recordings into reusable benchmark units. Existing standards organize files, metadata, and provenance, but they do not specify EEG tasks under a common language and rulebook, leaving critical task semantics scattered across papers, code, and manual interpretation. We investigate whether heteroge...
## Key Insights
- Derived from arXiv:2606.22925
- Published: 2026-06-22
- Utility Score: 0.97
- Authors: Chengxuan Qin, Zhige Chen, Shu Peng et al.
## Activation
eeg-benchmarking-needs-a-task-specification-layer, 2606.22925
## References
- arXiv: https://arxiv.org/abs/2606.22925
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".
