bazi-reading
把一份已完成的单人八字 JSON 命盘、或等价的经过核对的四柱数据,解读成一份逐条附依据的静态原局报告。适用于计算器交来文件时,或有人要求解读八字、看命局、说明日主强弱、格局与喜用神的场合。不适用于原始出生信息、双人合婚、大运流年、带日期的预测或数据不完整的情况。
- 分组
- 命理
- 版本
- 0.8.4
- 许可证
- MIT
安装
/plugin install chinese-metaphysics@misoto22然后这样调用:
/chinese-metaphysics:bazi-reading这个技能读已经排好的命盘,产出一份面向读者的原局分析,长度目标在 1400 到 1900 字之间——足够把每个格局、每处张力和可落地的观察展开讲,而不是给一段谁都看得懂但谁也用不上的概括。它的关键约束是「静态」:只讲命盘本身,不碰大运流年,也不做带时间的预测。所有技术性证据(分数、来源 ID、校验和、推算过程)写进单独的存档文件,读者拿到的报告里只有结论和它依据的那几个具体事实。
什么时候会触发
CI 实际用来评测这个技能的 prompt——所以它们不会和技能的真实行为脱节。
会触发
- Interpret the verified bazi_A.json that the calculator just created.
- 这是我的八字 JSON,帮我解读日主强弱和命局结构。
- I pasted all four pillars, fact ledger, score ledger, models, and boundary metadata below. Read the chart.
不会触发
- I was born 1990-03-14 07:42 in Shanghai. Read my BaZi.
- Compare my existing BaZi with my partner's chart.
- Use this chart to tell me the exact date I will get married.
BaZi Reading
Read one complete chart and write bazi_reading_<name>.md plus bazi_reading_evidence_<name>.md. Interpret; never recalculate. The first is a reader report; the second is a separate evidence artifact.
Before writing either file, read and follow shared/report-presentation.md. It defines the common localization, data-card, and separate-evidence boundary rules; this skill defines the natal evidence and section requirements.
Route and source gate
- Raw name/place/date/time belongs to
bazi-chartfirst. - Two-person matching belongs to
bazi-compatibility. - Da Yun, annual luck, dated events, and forecasts are outside this release.
Accept one of:
- A
chinese-metaphysics.bazi-chartJSON artifact at schema version 1 with a valid canonical checksum. - Its verified Markdown rendering together with the matching JSON. Markdown alone is not a machine source.
- Complete pasted equivalent data containing identity, all four pillars and boundaries, facts, interaction records, both score distributions, day-master ledger, model versions, confidence, and alternate sensitivity. Mark this source
pasted-complete; do not pretend it had a checksum.
Use the vendored shared/bazi/artifacts.py validator for a JSON artifact. Stop on checksum mismatch, unsupported schema/version, a missing hour pillar, an incomplete score ledger, or a sensitivity flag without a complete alternate. Name the exact defect and route raw details back to bazi-chart; never patch or infer a field.
Build an evidence ledger first
Assign stable raw evidence ids before writing prose:
- Collect
[P-year],[P-month],[P-day], and[P-hour]for primary pillars. - Collect
[B-year],[B-month],[B-day], and[B-hour]for boundary and time basis. - Preserve structural interaction ids such as
[interaction-001], scoring ids such as[base.visible.month]and[adjust.seasonal.木], and strength component names. - Prefix alternate evidence with
[ALT-...]; prefix Shen Sha with[SS-...]and label it secondary.
Use this ledger to build the evidence artifact's heading-based claim map. Do not expose its ids in the reader report.
Interpretation discipline
- Say “in this traditional model,” “suggests,” or “is commonly read as.” Never present metaphysical interpretation as scientific fact, certainty, diagnosis, or fate.
- Explain five-element percentages and the day-master score as outputs of the named heuristic model, not probabilities.
- Start from month command, day master, roots, visible support/control, and formed structural relations. A score does not establish a special structure by itself.
- Treat favorable and unfavorable tendencies as conditional balancing hypotheses tied to the ledger, not universal prescriptions.
- Keep Shen Sha secondary; no single Shen Sha may drive a conclusion.
- Do not infer gender or apply gender-dependent conventions unless the source explicitly supplies gender and the user requests that convention.
- Do not infer personality disorders, health conditions, fertility, lifespan, wealth amount, moral character, or inevitable relationship outcomes.
- Give practical actions as low-risk reflection prompts, not commands to make medical, legal, financial, employment, or relationship decisions.
Alternate-chart sensitivity
When a 00:00-boundary alternate exists, interpret primary and alternate independently. Separate:
- stable findings supported by both charts;
- changed day/hour evidence and every conclusion it affects;
- claims that should be withheld because the boundary choice changes them.
Never average their pillars, percentages, strength scores, or interpretations. Lower the report's claim confidence where sensitivity is material. Retain primary and alternate raw evidence separately in the evidence artifact.
Required report order
Keep exactly these five reader-report sections, using the structure in references/output-template.md:
- Main pattern
- Chart tendencies
- Strengths and tensions
- Relationships, work, and reflection
- Model data card
Put the conditional conclusion first, but lead with the person's lived pattern rather than source confidence or a method disclaimer. Develop the pattern, its countervailing tension, and its practical expression to the depth required by shared/report-presentation.md; do not reduce the reader report to a score summary. Show a concise four-pillar table only when it helps section 2. In section 5, state once that five-element percentages and day-master scores are heuristic model references, not probabilities.
Write the separate evidence artifact after the reader report. In addition to the shared evidence requirements, include source status, boundary rules, rule and scoring details, the component ledger, and separate alternate calculations. Classify natal evidence as primary, calculated heuristic, alternate, or secondary Shen Sha evidence.
Write safely
Create UTF-8 Markdown only after validation and evidence indexing. Use portable source names in bazi_reading_<name>.md and bazi_reading_evidence_<name>.md; preserve the display name inside both files. Do not overwrite a different report pair. When a same-name reader report or evidence artifact already exists, reuse the pair only if both record the same source checksum; otherwise append the first eight checksum characters to both names.
Report the reader-report path, evidence-artifact path, and source JSON path. Do not create new chart JSON, alter the source artifact, or invoke the chart calculator after a valid hand-off.
See references/examples.md for a hand-off, alternate-boundary treatment, and corrupt-source refusal.