Build and evaluate RACE style multiple choice candidate records for DeBERTa recovery experiments.
Scanned 9/9/2026
Install to Claude Code
npx -y skills add VectorSpaceLab/AREX-Skill --skill deberta_race_multiple_choice_protocol --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Deberta Race Multiple Choice Protocol?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vectorspacelab-deberta-race-multiple-choice-protocol)More formats (shields.io, HTML) on the badges page.
---
name: deberta_race_multiple_choice_protocol
description: Build and evaluate RACE style multiple choice candidate records for DeBERTa recovery experiments.
---
# DeBERTa RACE Multiple Choice Protocol
Use this skill when a DeBERTa recovery needs a RACE-style article, question, four-option candidate layout, and accuracy calculation. The skill owns label handling and metric computation; attention and decoder helpers should return scores, not final benchmark semantics.
## Inputs
- Article text.
- Question text.
- Four answer option strings.
- Gold label `A`, `B`, `C`, or `D`.
- Optional token budget.
## Outputs
- Four candidate records containing article, question, option, label, candidate text, token positions, and absolute option position.
- Predicted label from candidate logits.
- Accuracy as a numeric metric.
## Workflow
1. Normalize whitespace.
2. Tokenize deterministically for reduced recovery, or preserve supplied tokenizer output in full recovery.
3. Build one candidate per option using the conceptual layout `[CLS] article [SEP] question option [SEP]`.
4. Score candidates externally.
5. Use `scripts/race_protocol.py` to choose the maximum-logit label and compute accuracy.
## Validation
The tests confirm four-option validation, label preservation, packed candidate records, and exact accuracy behavior.
## Limitations
This skill does not download or parse the full RACE benchmark. A reduced recovery item must clearly mark whether it is benchmark-style or resource-derived.
The standard-library tokenizer is only a recovery proxy. When truncation is used, record the requested `max_seq_len`, the emitted candidate token lengths, and whether absolute positions refer to the original untruncated item or the truncated packed sequence.
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!