返回技能列表

research-word-etymology

pjt222
更新于 Yesterday
5 次查看
17
2
17
在 GitHub 上查看
测试wordtestingdata

关于

This skill researches word origins by tracing proto-language roots and identifying cognates across language families. It documents semantic drift with dated attestations and flags folk etymologies. Use it for investigating word histories, comparing related languages, or debunking unsupported origin stories.

快速安装

Claude Code

推荐
主要方式
npx skills add pjt222/agent-almanac -a claude-code
插件命令备选方式
/plugin add https://github.com/pjt222/agent-almanac
Git 克隆备选方式
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/research-word-etymology

在 Claude Code 中复制并粘贴此命令以安装该技能

技能文档

Wortetymologie erforschen

Trace a word's origin from its modern form back durch attested historical stages and reconstructed proto-language roots, identify cognates in related languages, document semantic drift with dated evidence, and flag any folk etymologies.

Wann verwenden

  • Investigating the origin and historical development of a specific word
  • Comparing cognate words across related languages to find a common ancestor
  • Charting how a word's meaning has changed over centuries with attestation dates
  • Evaluating whether a popular origin story is genuine or a folk etymology
  • Building a structured etymology entry for documentation or scholarly reference

Eingaben

  • Erforderlich: Target word (the modern form to research)
  • Erforderlich: Source language of das Ziel word (default: English)
  • Optional: Depth of reconstruction (default: earliest reconstructable root; alternative: stop at a specific historical stage)
  • Optional: Cognate languages to include (default: major branches of the same family)
  • Optional: Output format (default: structured entry; alternative: narrative prose)

Vorgehensweise

Schritt 1: Identifizieren the Modern Form and First Attestation

Establish the current usage and earliest documented appearance of das Ziel word.

  1. Erfassen the modern spelling, pronunciation (IPA if possible), and primary meaning(s) in die Quelle language.

  2. Suchen for the earliest attested use of the word in die Quelle language. Consult etymological dictionaries (OED for English, TLFi for French, DWDS for German) and historical corpora via WebSearch:

Search: "[target word] etymology first attested" site:etymonline.com OR site:oed.com
  1. Erfassen the attestation date, die Quelle text, and the meaning at first attestation. Note whether the modern meaning differs from the original.

  2. If the word entered die Quelle language via borrowing, identify the immediate donor language and approximate date of borrowing.

Erwartet: A dated first attestation with die Quelle text identified, the meaning at first use recorded, and the immediate donor language (if borrowed) established.

Bei Fehler: If no attestation date is found in online sources, note this explicitly and proceed with the oldest available evidence. Mark the attestation as "date uncertain" and continue to Step 2.

Schritt 2: Trace the Etymological Chain

Work backward from the modern form durch documented historical stages to the earliest reconstructable root.

  1. Fuer jede historical stage, record:

    • The form (spelling/transcription)
    • The language and approximate date range
    • The meaning at that stage
    • The phonological changes from the previous stage
  2. Follow this chain durch attested languages first, then into reconstructed proto-languages. Use standard notation: asterisk (*) for reconstructed forms, angle brackets for graphemes, slashes for phonemes.

  3. For Indo-European languages, a typical chain looks like:

    • Modern form (e.g., Modern English, post-1500)
    • Middle period form (e.g., Middle English, 1100-1500)
    • Old period form (e.g., Old English, 450-1100)
    • Proto-language form (e.g., Proto-Germanic, reconstructed)
    • Deep proto-language (e.g., PIE, reconstructed)
  4. For borrowed words, trace durch each donor language vor reaching the ultimate origin. A Latin borrowing in English might go: Modern English < Old French < Latin < PIE.

  5. At each stage, note relevant sound laws that explain the phonological changes (e.g., Grimm's Law for PIE-to-Germanic consonant shifts, the Great Vowel Shift for Middle-to-Modern English vowel changes).

Erwartet: A complete chain from modern form to earliest reconstructable root, with each stage dated, the form and meaning recorded, and sound changes explained by named phonological rules where applicable.

Bei Fehler: If the chain breaks at a particular stage (no further ancestor kann identified), mark that stage as the terminus with "origin beyond this point unknown" and proceed to Step 3 with what ist verfuegbar.

Schritt 3: Identifizieren Cognates Across Language Families

Finden words in related languages that descend from the same proto-form.

  1. From the deepest reconstructed root identified in Step 2, search for reflexes (descendant forms) in other branches of the language family.

  2. Fuer jede cognate, record:

    • The language and modern form
    • The meaning (noting any semantic divergence from das Ziel word)
    • The regular sound correspondences that connect it to the proto-form
  3. Group cognates by branch. For PIE, typical branches include: Germanic, Italic (Romance), Celtic, Hellenic, Balto-Slavic, Indo-Iranian, Armenian, Albanian, Tocharian, Anatolian.

  4. Verifizieren cognates by checking that the sound correspondences are regular (systematic across multiple word sets), not just superficial resemblance. False cognates (look-alikes from unrelated roots) sollte explicitly flagged and excluded.

  5. Format the cognate set as a 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]

Erwartet: A cognate set with mindestens 3 branches represented (where the root has surviving reflexes), each cognate verified by regular sound correspondences, and any false cognates explicitly excluded with explanation.

Bei Fehler: If the root has few surviving cognates (common for domain-specific or culturally bound vocabulary), document what exists and note the limited distribution. If the word has no cognates outside its immediate branch, state this and explain why (e.g., the word kann a substrate borrowing or an innovation innerhalb that branch).

Schritt 4: Dokumentieren Semantic Drift

Chart how the word's meaning has changed from the proto-root to the modern form.

  1. At each stage of the etymological chain (from Step 2), record the primary meaning. Where multiple senses coexist, note them all.

  2. Classify each meaning change gemaess standard categories:

    • Narrowing (specialization): meaning becomes more specific (e.g., "deer" once meant any animal)
    • Broadening (generalization): meaning becomes more general (e.g., "dog" once meant a specific breed)
    • Amelioration: meaning becomes more positive (e.g., "knight" from servant to noble warrior)
    • Pejoration: meaning becomes more negative (e.g., "villain" from farmworker to evildoer)
    • Metaphor: meaning shifts via analogy (e.g., "mouse" from rodent to computer device)
    • Metonymy: meaning shifts via association (e.g., "crown" from headwear to monarchy)
  3. Bereitstellen the approximate date of each semantic shift where attestation evidence supports it.

  4. Format the drift as a timeline:

Semantic drift: [word]
  [date/period]: "[meaning]" ([source])
  [date/period]: "[meaning]" — [drift type] ([source])
  [date/period]: "[meaning]" — [drift type] ([source])
  Present:       "[meaning]"

Erwartet: A dated semantic drift timeline with mindestens the original and modern meanings, each shift classified by type, and attestation sources cited.

Bei Fehler: If intermediate stages lack clear attestation evidence, note the gap explicitly (e.g., "semantic shift from X to Y occurred zwischen [date range] but the mechanism ist nicht attested") and proceed with available evidence.

Schritt 5: Flag Folk Etymologies

Identifizieren and evaluate any popular but incorrect origin stories associated with the word.

  1. Suchen for common folk etymologies, backronyms, or urban legends about the word:
Search: "[target word] folk etymology" OR "[target word] myth origin" OR "[target word] false etymology"
  1. Fuer jede folk etymology found, document:

    • The claimed origin story
    • Why it is linguistically unsupported (e.g., anachronistic, phonologically impossible, no attestation evidence)
    • The likely reason the folk etymology became popular (satisfying narrative, apparent plausibility, memorable acronym)
  2. If no folk etymologies exist for this word, state that explicitly anstatt omitting the section.

  3. 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 nach the word already existed

Erwartet: Any folk etymologies identified and debunked with linguistic evidence, or an explicit statement that no folk etymologies are known for this word.

Bei Fehler: If the status of a claimed etymology is genuinely uncertain (legitimate scholarly debate), present both sides with citations anstatt forcing a verdict. Mark as "disputed" with the competing hypotheses.

Schritt 6: Format the Structured Etymology Entry

Compile all findings into a standardized output format.

  1. Assemble the entry with die folgenden 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]
  1. Ueberpruefen the entry for internal consistency: does the etymological chain match the cognate set? Does the semantic drift timeline align with the attestation dates?

  2. Hinzufuegen a confidence assessment for the overall etymology, noting any weak links in the chain.

Erwartet: A complete, internally consistent etymology entry with all sections filled, sources cited, and confidence levels marked.

Bei Fehler: If any section could not be completed (e.g., no cognates found, no folk etymologies known), include the section with an explicit "not applicable" or "insufficient evidence" note anstatt omitting it.

Validierung

  • Modern form and first attestation are recorded with a date and source
  • Etymological chain traces mindestens two historical stages (or notes why fewer exist)
  • Reconstructed forms use standard notation (asterisk prefix)
  • Cognate set includes words from mindestens two language branches (where available)
  • Sound correspondences cited are regular (not ad hoc resemblances)
  • Semantic drift timeline has dated entries with classified shift types
  • Folk etymologies are addressed (either debunked or noted as absent)
  • Sources are cited (dictionary names, corpus names, or URLs)
  • Confidence level is explicitly stated
  • Entry is internally consistent (chain, cognates, and drift align)

Haeufige Stolperfallen

  • Surface resemblance mistaken for cognacy: Words that look similar across languages sind nicht necessarily related (e.g., English "much" and Spanish "mucho" are from different roots). Always verify with regular sound correspondences, not visual similarity.
  • Confusing borrowing with inheritance: A word present in two related languages may wurden borrowed from one to the other anstatt inherited from a common ancestor. Check the phonological form gegen expected sound-law outcomes to distinguish the two.
  • Treating reconstructed forms as attested: PIE roots and other proto-forms are scholarly hypotheses, not historical documents. Always mark them with asterisks and note that they are reconstructed.
  • Accepting folk etymologies uncritically: Popular origin stories are often more memorable than correct etymologies. Always check for attestation evidence and phonological plausibility vor accepting a claimed origin.
  • Ignoring semantic drift: A word's modern meaning kann very different from its original meaning. Tracing only the form ohne tracking the meaning can produce misleading results.
  • Stopping too early: Many online sources give only one or two stages of a word's history. Push back to the deepest available reconstruction for a complete picture.

Verwandte Skills

  • manage-memory — Dokumentieren etymology research findings for persistent reference across sessions
  • argumentation — Erstellen and evaluate arguments about contested etymologies

GitHub 仓库

pjt222/agent-almanac
路径: i18n/de/skills/research-word-etymology
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

相关推荐技能

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或清理等结构化选项。核心价值在于确保代码质量的同时,标准化分支收尾流程。

查看技能