← Plugin catalog
Entertainment

Guanyin Oracle · 观音灵签

Brandon Lim v1.0.0

Publisher description

From the marketplace listing

Guanyin Oracle offers a quiet, Chinese-first reflection ritual based on a bundled 100-sign Guanyin corpus. Hold one focused question, make one symbolic draw, then confirm it with one symbolic cup action. The source sign poem and traditional note remain in Chinese, with a detailed interpretation in Chinese and faithful English. Each reading connects the sign to the question, distinguishes reflection from prediction, and offers practical seven-day actions and clear boundaries for health, financial, legal, and other consequential topics. Users may optionally save a JPEG card for the exact sign they drew. The service processes only inputs needed to return the reading and does not persist ritual sessions.

Language: English · Automatically detected from descriptions.

Files & skills

File archives

Plugin package2 files · 1.05 KBBrowse files →
guanyin-oracle4 files · 16.2 KBBrowse files →
Skill instructions
guanyin-oracle8.73 KB

View saved version →

---
name: guanyin-oracle
description: Conduct a Chinese-first Guanyin oracle ritual using the bundled 100-sign corpus, cup confirmation, and a faithful English reading. Use when the user asks to draw a Guanyin sign, seek a Guanyin oracle, request 观音灵签, or asks for a Chinese spiritual reading.
---

# 观音灵签 · Guanyin Oracle

Conduct a respectful, bounded ritual for reflection. The original draw remains Chinese; every interpretation is written in Chinese first and followed immediately by a faithful English counterpart.

## Interactive temple first

When the `render_guanyin_temple` MCP tool is available, use it before any draw. Pass through the user's question, category, and selected mode when known. The resulting **观音殿 · Guanyin Temple** widget is the primary experience: the user sets their question, presses `合掌请签` once, then presses `掷筊定签` once. The full result appears immediately in the widget. A busy ritual action must be disabled, and duplicate calls must preserve the original sign and reading.

- Do not imitate the widget's buttons or animated ritual in Markdown.
- Do not run the legacy local scripts while the widget is available; they are the fallback for non-widget hosts only.
- The widget returns its full detailed bilingual reading itself. Do not issue a second chat prompt, `ui/message`, model-context update, or Markdown retelling after the ritual.
- The original sign poem and traditional note remain Chinese only. Translate the interpretation, not the source sign text.
- If the MCP widget cannot render, explain that briefly and use the legacy local-script flow below rather than pretending the interactive surface appeared.

## Core principles

- Preserve the bundled sign text exactly. Never invent or alter a poem, traditional note, rank, palace, or keyword.
- The sign is a reflective aid, not a factual prediction or professional decision system.
- Keep the ritual Chinese-first: use `观音灵签`, `摇签`, and `掷筊` in the ritual itself. Do not translate the original poem or traditional note as part of the draw.
- The **reading** is bilingual. English must convey the same judgment and caveats as the Chinese directly above it; it must not introduce a different interpretation.
- Use a few concise ritual beats in chat to evoke the app's temple flow. Do not claim to display 3D animation, physical randomness, temple audio, or a live visual when those are unavailable.

## Seamless result and sign card

- The complete result must require only two symbolic ritual taps after the user has entered their question: draw, then confirm. In strict mode, the widget presents all three confirming cups together in that second tap; it does not create a redraw loop.
- Never call `ui/message` or the built-in image-generation tool as part of this ritual. Both turn a private widget action into a separate host conversation or approval flow.
- The widget renders the full reading locally and offers one optional `保存本签 JPEG` action. It creates an exact local JPEG card for the specific sign drawn, with the real Chinese poem, traditional note, and key Chinese guidance; saving is never automatic.
- Do not claim that a hidden model or image-generation service was used. The sign data and reading rules are local to the plugin.

## Before drawing

Ask for one focused question and one category when either is missing. Available categories are:

| 中文 | English |
| --- | --- |
| 事业 | Career |
| 感情 | Love and relationships |
| 家庭 | Family |
| 学业 | Study |
| 迁移 | Relocation |
| 财务倾向 | Financial direction |
| 健康 | Health |
| 平安 | Peace and wellbeing |
| 失物 | Lost items |
| 一般问事 | General matter |

Do not turn an unclear or multi-part question into a confident conclusion. Help the user reduce it to one decision or condition first. Default to `一般问事` only if they explicitly ask to draw without a category.

Ask whether they want `一般模式:一圣杯` or `严肃模式:三圣杯(最多七次)` if they have not specified. Default to general mode after they provide their question.

## Ritual execution

1. Only when the interactive widget is unavailable, resolve this plugin's root from this file's location. Run `node <plugin-root>/scripts/draw-sign.mjs` and retain the returned JSON in the current ritual state.
2. Give a brief Chinese ritual beat, for example: `请静一静,只问这一事。签筒已起。`
3. Show the drawn sign in Chinese only: sign number, rank, palace, poem, traditional note, and keywords.
4. Run `node <plugin-root>/scripts/cast-cup.mjs` for general mode. In serious mode run `node <plugin-root>/scripts/cast-cup.mjs --strict --attempt <n>`.
5. In general mode, interpret only after a `圣杯`. For `笑杯` or `阴杯`, say that this sign is not confirmed and invite the user to return it and draw again; do not force a reading.
6. In serious mode, keep the current attempt count and the number of `圣杯` obtained since the latest draw. Three `圣杯` are required. A `笑杯` or `阴杯` means the sign is not confirmed: ask the user to draw again, preserve the attempt count, and reset the current sign's confirmation count. The script transparently guarantees `圣杯` on attempts 5-7 so the ritual cannot run indefinitely.
7. Never reuse a previous sign, cup, or random output as though it were a new draw. If the scripts cannot run, say so plainly instead of fabricating a ritual result.

## Reading format after confirmation

Use this exact order. Keep the original-sign block Chinese only; write each interpretation block in Chinese and then English. This is intentionally a substantial reading: each main prose section must add a different useful layer of interpretation rather than rephrasing the same point. Aim for 3–5 grounded sentences in Chinese for `签意总断`, `对应问事`, `事势层次`, `当前阻碍`, and `可行方向`, followed by an English rendering with the same substance.

```markdown
## 观音灵签 · Guanyin Oracle

**第 N 签 · 签级 · 宫位**

> 签诗:<original Chinese poem>
>
> 传统解曰:<original Chinese note>

关键词:<original Chinese keywords>
筊杯:<Chinese cup result and, in serious mode, confirmation count>

### 问事落点
<Chinese restatement of the real decision or condition being held; distinguish what is known from what the user has not supplied.>

### Question held
<Faithful English rendering.>

### 签意总断
<Chinese interpretation grounded in the poem, note, rank, palace, cup result, and user question.>

### Overall reading
<Faithful English rendering of the Chinese paragraph directly above.>

### 对应问事
<Chinese reading for the user's actual question.>

### Reading for your question
<Faithful English rendering.>

### 事势层次
<Chinese explanation of the sign's central tension: what it supports, what it makes conditional, the sequence it advises, and why it matters now.>

### Deeper pattern
<Faithful English rendering.>

### 当前阻碍
<Chinese>

### Present obstacle
<Faithful English rendering.>

### 可行方向
<Chinese>

### Practical direction
<Faithful English rendering.>

### 七日建议
1. <Chinese action>
2. <Chinese action>
3. <Chinese action>
4. <Chinese action>

### 7-day actions
1. <Faithful English action>
2. <Faithful English action>
3. <Faithful English action>
4. <Faithful English action>

### 不宜 / Avoid
- <Chinese caution> — <faithful English rendering>
- <Chinese caution> — <faithful English rendering>

### 复问时机
<Chinese: name a real-world condition to reassess before drawing again; never give a magical deadline.>

### When to revisit
<Faithful English rendering.>

### 依据 / Basis
- <exact short phrase from the poem or traditional note> — <brief explanation>
- <cup result> — <brief explanation>

### 边界 / Boundary
<Chinese boundary note>

### Boundary
<Faithful English rendering>
```

Use 1-2 exact short phrases from the poem or traditional note as evidence, plus the cup result. Do not create a new verse, historical source, deity quote, hidden fact, or unsupported real-world narrative. Be warm and temple-like, but not theatrical or mechanically "AI". Detailed means more specific and more useful—not more certain.

## Safety boundaries

- For health: discuss rest, seeking care, checks, and support only. Never diagnose, prescribe, interpret symptoms, or defer urgent care.
- For financial questions: never name a security, amount, trade, or timing. Emphasize cash-flow review, decision conditions, and qualified advice.
- For legal, pregnancy, safety, death, or other consequential decisions: do not offer a decisive outcome. State that the sign is reflective only and encourage the relevant professional or emergency support.
- Do not encourage repeated draws for the same unchanged issue. Suggest waiting at least seven days or until the real-world conditions change.

Referenced files: 3

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Brandon Lim

Package observed Oct 2, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Oct 2, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6a5844ea64f48191930701aef807c7b3

Download plugin data (JSON)