MCP HubMCP Hub
스킬 목록으로 돌아가기

apply-gematria

pjt222
업데이트됨 2 days ago
4 조회
17
2
17
GitHub에서 보기
문서 처리word

정보

이 스킬은 단어나 구문에 대해 표준, 서수, 축소 방식을 사용하여 히브리어 게마트리아 값을 계산합니다. 용어 간 비교를 가능하게 하며, 생명나무와 같은 해석 체계에 수치 결과를 연결합니다. 이소세피 분석, 성경 구절 연구, 또는 신비주의 문헌에서 수치적 상응 관계를 찾는 데 활용하세요.

빠른 설치

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/apply-gematria

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Apply Gematria

Compute and analyze gematria — the system of assigning numerical values to Hebrew letters and words. Covers standard (Mispar Hechrachi), ordinal (Mispar Siduri), and reduced (Mispar Katan) methods, isopsephy comparisons between words of equal value, and interpretive frameworks for contemplation.

When to Use

  • You want to compute the numerical value of a Hebrew word or phrase
  • You are comparing two words to determine if they share a gematria value (isopsephy)
  • You need to understand which gematria method is appropriate for a given analysis
  • You are studying a biblical verse or divine name and want to uncover numerical correspondences
  • You are exploring the relationship between a word's meaning and its numerical value
  • You want to connect a numerical result to its position on the Tree of Life

Inputs

  • Required: A Hebrew word, phrase, or divine name to analyze (in Hebrew script or transliteration)
  • Optional: A second word/phrase for comparison (isopsephy)
  • Optional: Preferred gematria method (standard, ordinal, reduced, or all three)
  • Optional: Context or question guiding the analysis (e.g., "Why do these two words share a value?")

Procedure

Step 1: Transliterate and Identify the Hebrew Source

Establish the exact Hebrew spelling of the word or phrase.

HEBREW LETTER VALUES — Standard Gematria (Mispar Hechrachi):

Units:
  Aleph (A)  = 1     Bet (B)    = 2     Gimel (G)  = 3
  Dalet (D)  = 4     Heh (H)    = 5     Vav (V)    = 6
  Zayin (Z)  = 7     Chet (Ch)  = 8     Tet (T)    = 9

Tens:
  Yod (Y)    = 10    Kaf (K)    = 20    Lamed (L)  = 30
  Mem (M)    = 40    Nun (N)    = 50    Samekh (S) = 60
  Ayin (Ay)  = 70    Peh (P)    = 80    Tzadi (Tz) = 90

Hundreds:
  Qoph (Q)   = 100   Resh (R)   = 200   Shin (Sh)  = 300
  Tav (Th)   = 400

Final Forms (Sofit — used when letter appears at end of word):
  Kaf-final  = 500   Mem-final  = 600   Nun-final  = 700
  Peh-final  = 800   Tzadi-final = 900

Note: Whether final forms carry different values depends on the
gematria system. Standard (Mispar Hechrachi) typically uses the
same values for regular and final forms. The 500-900 values above
follow the extended system (Mispar Gadol).
  1. If the input is in English transliteration, convert to Hebrew letter sequence
  2. Verify the spelling: Hebrew has multiple possible spellings for some words (plene vs. defective)
  3. Note if the word contains final-form letters (Kaf-sofit, Mem-sofit, Nun-sofit, Peh-sofit, Tzadi-sofit)
  4. State the source: is this a biblical word, a divine name, a modern Hebrew word, or a technical Kabbalistic term?
  5. If ambiguous, present both common spellings and compute gematria for each

Got: The Hebrew letter sequence is established with confidence. The user knows exactly which letters are being summed and can verify the spelling.

If fail: If the transliteration is ambiguous (e.g., "chai" could be Chet-Yod or Chet-Yod-Yod in some contexts), present both options with their gematria values and let the user select.

Step 2: Apply Standard Gematria (Mispar Hechrachi)

Sum the letter values using the standard Hebrew number table.

  1. Write out each letter with its standard value
  2. Sum the values left to right (Hebrew reads right to left, but addition is commutative)
  3. State the total clearly
  4. Note if the total matches a significant number:
    • A sephira number (1-10)
    • A path number (11-32)
    • A well-known gematria value (26 = YHVH, 18 = chai, 72 = Shem ha-Mephorash, 137 = Kabbalah)
  5. If the total exceeds 400, note that it requires summing multiple hundreds

Got: A clear numerical result with the computation shown step by step. The user can verify each letter's value against the table.

If fail: If the user provides a word with uncertain Hebrew spelling, compute values for all plausible spellings and note the range. The "correct" spelling depends on the source text.

Step 3: Apply Ordinal and Reduced Methods (Optional)

Compute alternative gematria values that reveal different patterns.

ORDINAL GEMATRIA (Mispar Siduri):
Each letter receives its ordinal position (1-22):
  Aleph=1, Bet=2, Gimel=3, Dalet=4, Heh=5, Vav=6,
  Zayin=7, Chet=8, Tet=9, Yod=10, Kaf=11, Lamed=12,
  Mem=13, Nun=14, Samekh=15, Ayin=16, Peh=17, Tzadi=18,
  Qoph=19, Resh=20, Shin=21, Tav=22

REDUCED GEMATRIA (Mispar Katan):
Reduce each letter's standard value to a single digit:
  Aleph=1, Bet=2, ... Tet=9, Yod=1, Kaf=2, ... Tzadi=9,
  Qoph=1, Resh=2, Shin=3, Tav=4

  Then sum the digits. If the sum exceeds 9, reduce again.
  Example: Shin(3) + Lamed(3) + Vav(6) + Mem(4) = 16 → 1+6 = 7

ATBASH:
A substitution cipher: first letter ↔ last letter.
  Aleph ↔ Tav, Bet ↔ Shin, Gimel ↔ Resh, etc.
  Used in biblical and Kabbalistic cryptography (Jeremiah's
  "Sheshach" = Babel via Atbash).
  1. Compute ordinal gematria: sum each letter's position (1-22) in the alphabet
  2. Compute reduced gematria: reduce each standard value to single digit, then sum and reduce again
  3. Present all three values together for comparison
  4. Note which method reveals the most interesting connections for this particular word

Got: Three numerical values (standard, ordinal, reduced) presented side by side. The reduced value often links to single-digit sephirotic numbers, making it useful for Tree of Life mapping.

If fail: If the user only wants one method, provide that method and mention the others exist for future exploration. Do not overwhelm with calculations if a single method was requested.

Step 4: Search for Isopsephy Connections

Identify other Hebrew words or phrases that share the same numerical value.

  1. Take the standard gematria value from Step 2
  2. Search for well-known words, divine names, or phrases with the same value
  3. Present 2-5 connections, prioritizing:
    • Biblical words and phrases
    • Divine names and sephirotic titles
    • Traditional Kabbalistic connections documented in classical sources
    • Surprising or illuminating connections
  4. For each connection, note the source tradition (Zohar, Talmud, later Kabbalistic commentary, Hermetic tradition)
  5. Note if no significant connections are found — not every number has rich isopsephy

Got: A set of words sharing the same gematria value, each with a brief note on why the connection might be meaningful. The user has material for contemplation.

If fail: If no well-known connections exist for the computed value, acknowledge this. Offer to compute the value's relationship to nearby significant numbers (e.g., "your value is 378, which is 2 more than shalom [376] — what does that suggest?").

Step 5: Interpret Connections and Correspondences

Move from computation to contemplation — what do the numerical relationships suggest?

  1. State clearly: gematria reveals correspondences for contemplation, not proofs or predictions
  2. For each isopsephy connection found, pose a contemplative question:
    • "Word A and Word B share the value N. How might their meanings illuminate each other?"
    • "The reduced value points to sephira X. How does this word's meaning relate to that sephira's quality?"
  3. Note connections to the Tree of Life:
    • Standard value 1-10 → direct sephirotic correspondence
    • Reduced value 1-9 → sephirotic resonance
    • Value = a path number (11-32) → resonance with that path's Hebrew letter
  4. If the user provided a guiding question (from Inputs), address it directly using the gematria results
  5. Close with one integrative statement connecting the numerical analysis to the word's meaning

Got: The numerical analysis has become meaningful — not arithmetic but a lens for understanding the word's place in the symbolic network of Kabbalah.

If fail: If interpretation feels forced or speculative, say so directly. Some gematria computations are more fruitful than others. Honest acknowledgment of thin connections is better than fabricating significance.

Validation

  • The Hebrew spelling was established with confidence (or multiple spellings presented)
  • Standard gematria was computed with each letter's value shown
  • At least one additional method (ordinal or reduced) was applied
  • Isopsephy connections were searched and results presented with source notes
  • Interpretation was framed as contemplative, not demonstrative
  • The computation is verifiable — the user can check each letter against the value table

Pitfalls

  • Spelling ambiguity: Hebrew words can be spelled with or without vowel letters (matres lectionis). The gematria changes significantly — always confirm the spelling
  • Final-form confusion: Whether Mem-final = 40 or 600 depends on which gematria system is used. State the system explicitly
  • Finding what you expect: Gematria with enough methods will eventually connect any two words. Privileging connections that confirm a preexisting belief is confirmation bias, not analysis
  • Ignoring tradition: Classical Kabbalistic gematria connections (e.g., YHVH = 26, echad [one] = 13, ahavah [love] = 13, so love + unity = God) are documented in authoritative sources. Novel connections should be distinguished from traditional ones
  • Treating gematria as proof: Numerical equality between words suggests a correspondence to contemplate, not an identity or causal relationship
  • Forgetting context: The same word may have different gematria significance in a biblical verse vs. a liturgical text vs. a Kabbalistic meditation. Context shapes interpretation

Related Skills

  • read-tree-of-life — Map gematria values to sephirot and paths for structural context
  • study-hebrew-letters — Understanding individual letter symbolism deepens gematria interpretation
  • observe — Sustained neutral attention to patterns; gematria is a form of numerical pattern recognition

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-lite/skills/apply-gematria
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

release-standards

문서 처리

이 스킬은 소프트웨어 릴리스에 대한 시맨틱 버저닝(semver) 가이드라인과 변경 로그 형식 표준을 제공합니다. 릴리스를 준비할 때 버전 번호(메이저/마이너/패치)를 올바르게 증가시키고 변경 로그 항목을 구성하려면 이 스킬을 사용하세요. 사전 릴리스 식별자 규칙과 개발자를 위한 명확한 예시가 포함되어 있습니다.

스킬 보기

commit-standards

문서 처리

이 스킬은 Conventional Commits 표준에 따라 Git 커밋 메시지를 형식화합니다. 커밋 작성이나 리뷰 시 일관성을 보장하기 위해 템플릿과 유형 정의(예: `feat`, `fix`, `refactor`)를 제공합니다. 커밋 과정에서 이를 사용하여 명확하고 구조화된 커밋 기록을 생성할 수 있습니다.

스킬 보기

huggingface-tokenizers

문서 처리

이 스킬은 HuggingFace의 Rust 기반 라이브러리를 사용하여 1GB 텍스트를 20초 이내에 처리하는 고성능 토크나이제이션을 제공합니다. BPE, WordPiece, Unigram 알고리즘을 지원하며 사용자 정의 토크나이저 학습과 정렬 추적 기능을 포함합니다. 프로덕션 수준의 고속 토크나이제이션이 필요하거나 transformers 생태계와 통합된 맞춤형 토크나이저를 구축할 때 사용하세요.

스킬 보기

nano-pdf

문서 처리

nano-pdf는 개발자가 특정 페이지의 텍스트 변경이나 오타 수정과 같은 자연어 지시를 사용해 PDF를 편집할 수 있는 CLI 도구입니다. 터미널에서 직접 빠르고 프로그래밍 방식으로 PDF를 수정하는 데 이상적입니다. 페이지 번호 매기기가 버전마다 다를 수 있으므로 출력 결과는 항상 확인하세요.

스킬 보기