research-word-etymology
关于
This skill traces word origins through historical languages and reconstructed proto-roots, identifying cognates across language families. It documents semantic changes with dated attestations and flags unsupported folk etymologies. Use it to investigate word history, compare cognate sets, and debunk incorrect origin stories.
快速安装
Claude Code
推荐npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/research-word-etymology在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Research Word Etymology
Trace word origin from modern form back through attested historical stages + reconstructed proto-lang roots, ID cognates in related langs, document semantic drift w/ dated evidence, flag folk etymologies.
Use When
- Investigate origin + historical dev of specific word
- Compare cognate words across related langs → common ancestor
- Chart how meaning changed centuries w/ attestation dates
- Eval whether popular origin story genuine or folk
- Build structured etymology entry for docs/scholarly ref
In
- Required: Target word (modern form)
- Required: Source lang (default English)
- Optional: Reconstruction depth (default earliest reconstructable; alt: stop at specific historical stage)
- Optional: Cognate langs (default major branches of same family)
- Optional: Output format (default structured entry; alt narrative prose)
Do
Step 1: ID Modern Form + First Attestation
Establish current usage + earliest documented appearance.
-
Record modern spelling, pronunciation (IPA if possible), primary meaning(s) in source lang.
-
Search earliest attested use in source lang. Consult etymological dicts (OED for English, TLFi for French, DWDS for German) + historical corpora via WebSearch:
Search: "[target word] etymology first attested" site:etymonline.com OR site:oed.com
-
Record attestation date, source text, meaning at first attestation. Note if modern meaning differs from original.
-
If word entered source lang via borrowing, ID immediate donor lang + approx borrowing date.
→ Dated first attestation w/ source text ID'd, meaning at first use recorded, immediate donor lang (if borrowed) established.
If err: no attestation date in online sources → note explicit + proceed w/ oldest available evidence. Mark "date uncertain" + continue Step 2.
Step 2: Trace Etymological Chain
Work backward from modern form through documented historical stages → earliest reconstructable root.
-
Each historical stage record:
- Form (spelling/transcription)
- Lang + approx date range
- Meaning at stage
- Phonological changes from prev
-
Follow chain through attested langs first, then into reconstructed proto-langs. Use std notation: asterisk (*) for reconstructed, angle brackets for graphemes, slashes for phonemes.
-
For Indo-European, typical chain:
- Modern form (e.g. Modern English, post-1500)
- Middle period (e.g. Middle English, 1100-1500)
- Old period (e.g. Old English, 450-1100)
- Proto-lang (e.g. Proto-Germanic, reconstructed)
- Deep proto-lang (e.g. PIE, reconstructed)
-
Borrowed words → trace through each donor before ultimate origin. Latin borrowing in English: Modern English < Old French < Latin < PIE.
-
Each stage note relevant sound laws explaining phonological changes (e.g. Grimm's Law for PIE→Germanic consonant shifts, Great Vowel Shift for Middle→Modern English vowels).
→ Complete chain modern → earliest reconstructable root, each stage dated, form + meaning recorded, sound changes explained by named phonological rules.
If err: chain breaks at stage (no further ancestor) → mark terminus w/ "origin beyond this point unknown" + proceed Step 3 w/ what's available.
Step 3: ID Cognates Across Families
Find words in related langs descending from same proto-form.
-
From deepest reconstructed root in Step 2, search reflexes in other branches.
-
Each cognate record:
- Lang + modern form
- Meaning (note semantic divergence from target)
- Regular sound correspondences connecting to proto-form
-
Group cognates by branch. PIE typical branches: Germanic, Italic (Romance), Celtic, Hellenic, Balto-Slavic, Indo-Iranian, Armenian, Albanian, Tocharian, Anatolian.
-
Verify cognates → check sound correspondences regular (systematic across multi word sets), not just superficial. False cognates (look-alikes from unrelated roots) flagged + excluded.
-
Format cognate set as comparison table:
Root: PIE *[root] "[meaning]"
├── Germanic: English [form], German [form], Old Norse [form]
├── Italic: Latin [form] > French [form], Spanish [form], Italian [form]
├── Hellenic: Greek [form]
├── Balto-Slavic: Russian [form], Lithuanian [form]
└── Indo-Iranian: Sanskrit [form], Persian [form]
→ Cognate set w/ ≥3 branches (where root has reflexes), each verified by regular correspondences, false cognates explicitly excluded.
If err: root has few cognates (common for domain-specific or culturally bound vocab) → document what exists + note limited distribution. Word has no cognates outside immediate branch → state + explain (substrate borrowing or innovation).
Step 4: Document Semantic Drift
Chart how meaning changed proto-root → modern form.
-
Each stage of chain (Step 2) record primary meaning. Multi senses coexist → note all.
-
Classify each meaning change by std categories:
- Narrowing (specialization): meaning becomes more specific (e.g. "deer" once any animal)
- Broadening (generalization): meaning becomes more general (e.g. "dog" once specific breed)
- Amelioration: meaning more positive (e.g. "knight" servant → noble warrior)
- Pejoration: meaning more negative (e.g. "villain" farmworker → evildoer)
- Metaphor: shifts via analogy (e.g. "mouse" rodent → computer device)
- Metonymy: shifts via association (e.g. "crown" headwear → monarchy)
-
Provide approx date of each shift where attestation supports.
-
Format drift as timeline:
Semantic drift: [word]
[date/period]: "[meaning]" ([source])
[date/period]: "[meaning]" — [drift type] ([source])
[date/period]: "[meaning]" — [drift type] ([source])
Present: "[meaning]"
→ Dated semantic drift timeline w/ at least original + modern meanings, each shift classified, attestation sources cited.
If err: intermediate stages lack clear attestation → note gap explicit ("semantic shift X to Y between [date range] but mechanism not attested") + proceed.
Step 5: Flag Folk Etymologies
ID + eval popular but incorrect origin stories.
- Search common folk etymologies, backronyms, urban legends:
Search: "[target word] folk etymology" OR "[target word] myth origin" OR "[target word] false etymology"
-
Each folk found document:
- Claimed origin story
- Why linguistically unsupported (anachronistic, phonologically impossible, no attestation)
- Likely reason became popular (satisfying narrative, apparent plausibility, memorable acronym)
-
No folk etymologies for word → state explicit, no omit section.
-
Use clear verdict markers:
- Confirmed: Supported by linguistic evidence
- Probable: Well-supported but not conclusively proven
- Speculative: Possible but lacking sufficient evidence
- Folk etymology (unsupported): Popular but contradicted by evidence
- Backronym: Acronym invented after the word already existed
→ Folk etymologies ID'd + debunked w/ linguistic evidence, or explicit statement none known.
If err: status of claimed etymology genuinely uncertain (legitimate scholarly debate) → present both sides w/ citations not force verdict. Mark "disputed" w/ competing hypotheses.
Step 6: Format Structured Entry
Compile findings → standardized output.
- Assemble entry w/ structure:
## Etymology: [word]
**Modern form**: [word] ([language], [part of speech])
**Pronunciation**: /[IPA]/
**First attested**: [date], [source text/author]
### Etymological Chain
[Modern form] ([language], [date])
< [intermediate form] ([language], [date]) "[meaning]"
< [older form] ([language], [date]) "[meaning]"
< *[proto-form] ([proto-language]) "[reconstructed meaning]"
### Cognates
[Cognate table from Step 3]
### Semantic Drift
[Timeline from Step 4]
### Folk Etymologies
[Findings from Step 5, or "None known"]
### Sources
[Etymological dictionaries and corpora consulted]
### Confidence
[Overall confidence level: certain / probable / speculative / contested]
[Notes on any gaps or uncertainties in the analysis]
-
Review entry for internal consistency: chain matches cognate set? Drift timeline aligns w/ attestation dates?
-
Add confidence assessment for overall etymology, note weak links.
→ Complete internally consistent etymology w/ all sections, sources cited, confidence marked.
If err: section couldn't complete (no cognates, no folk known) → include section w/ explicit "not applicable" or "insufficient evidence" note, no omit.
Check
- Modern form + first attestation recorded w/ date + source
- Chain traces ≥2 historical stages (or notes why fewer)
- Reconstructed forms use std notation (asterisk prefix)
- Cognate set has words from ≥2 branches (where available)
- Sound correspondences cited regular (not ad hoc resemblances)
- Semantic drift timeline dated w/ classified shift types
- Folk etymologies addressed (debunked or noted absent)
- Sources cited (dict names, corpus names, URLs)
- Confidence level explicit
- Entry internally consistent (chain, cognates, drift align)
Traps
- Surface resemblance for cognacy: Look-alike words across langs not necessarily related (e.g. English "much" + Spanish "mucho" diff roots). Always verify regular correspondences not visual similarity.
- Confuse borrowing w/ inheritance: Word in 2 related langs may be borrowed not inherited from common ancestor. Check phonological form vs expected sound-law outcomes.
- Treat reconstructed as attested: PIE roots + other proto-forms = scholarly hypotheses not historical docs. Always mark asterisks + note reconstructed.
- Accept folk etymologies uncritically: Popular origins often more memorable than correct. Always check attestation + phonological plausibility.
- Ignore semantic drift: Modern meaning may be very diff from original. Tracing only form w/o meaning → misleading.
- Stop too early: Online sources give only 1-2 stages. Push back to deepest reconstruction for complete picture.
→
manage-memory— document etymology research findings for persistent ref across sessionsargumentation— build + eval arguments about contested etymologies
GitHub 仓库
相关推荐技能
evaluating-llms-harness
测试该Skill通过60+个学术基准测试(如MMLU、GSM8K等)评估大语言模型质量,适用于模型对比、学术研究及训练进度追踪。它支持HuggingFace、vLLM和API接口,被EleutherAI等行业领先机构广泛采用。开发者可通过简单命令行快速对模型进行多任务批量评估。
cloudflare-cron-triggers
测试这个Claude Skill提供了关于Cloudflare Cron Triggers的完整知识库,用于通过cron表达式定时执行Workers。它支持配置周期性任务、维护作业和自动化工作流,并能处理常见的cron触发错误。开发者可以用它来设置定时任务、测试cron处理器,并集成Workflows和Green Compute功能。
webapp-testing
测试该Skill为开发者提供了基于Playwright的本地Web应用测试工具集,支持自动化测试前端功能、调试UI行为、捕获屏幕截图和查看浏览器日志。它包含管理服务器生命周期的辅助脚本,可直接作为黑盒工具运行而无需阅读源码。适用于需要快速验证本地Web应用界面和交互功能的开发场景。
finishing-a-development-branch
测试这个Skill用于开发分支完成后的集成决策,当代码实现完成且测试通过时,它会引导开发者选择合适的工作流。它首先验证测试状态,然后提供合并、创建PR或清理等结构化选项。核心价值在于确保代码质量的同时,标准化分支收尾流程。
