unit-segmentation
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Split a paper's text into sentence- or clause-level units (with character offsets) for downstream classification, at a caller-specified granularity and scope (full text, abstract-only, or intro-only). Use this as the mandatory first step whenever any sentence/clause-level classification method (Argumentative Zoning, CoreSC, PubMed-RCT, CSAbstruct, Swales move analysis, CODA-19) needs its input pre-segmented — always precedes unit-classification.
In this repository34 other files it gives its agents.
- acu-nugget-recallSkill
- argumentative-zoningSkill
- atomic-unit-matchingSkill
- atomic-unit-recall-aggregateSkill
- atomic-unit-writingSkill
- claim-label-predictionSkill
- claim-writingSkill
- domain-level-judgmentSkill
- dual-column-self-checkSkill
- engineering-config-gradingSkill
- first-pass-skimSkill
- keshav-three-passSkill
- multi-stage-cascade-extractionSkill
- paper-fetchSkill
- qalmriSkill
- qalmri-worksheetSkill
- qasper-evidence-qaSkill
- quality-appraisal-checklistSkill
- question-framingSkill
- rationale-selectionSkill
- reforms-gradingSkill
- reporting-standard-checklistSkill
- reproducibility-third-party-verificationSkill
- research-question-appraisalSkill
- rhetorical-structure-qualitySkill
- second-pass-graspSkill
- signalling-question-answeringSkill
- star-awardingSkill
- study-design-tool-gateSkill
- sum-threshold-scoringSkill
- template-slot-fillingSkill
- third-pass-deep-readSkill
- unit-classificationSkill
- worst-case-lookupSkill
The file
Files
Unit Segmentation
Splits text into labeling units (sentence or clause granularity, scoped to full text/abstract/intro) — pure segmentation, no labeling.
Execution
Subagent — spawned via spawn-agent skill.
Why This Exists As Its Own Step
7 different classification methods (AZ, CoreSC, PubMed-RCT, NICTA-PIBOSO, CSAbstruct, CODA-19, Swales) all need pre-segmented units but disagree on granularity and scope — factoring segmentation out once, parameterized, avoids duplicating this logic inside unit-classification seven times over (graph correction L17/L18: the original graph was missing this step entirely, silently assuming pre-segmented input existed).
<!-- BEGIN available-tables (generated) -->Available SOPs
| SOP | When to use |
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. |
<!-- END available-tables (generated) -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.