OpenClaw/clawhub-security-signals huggingface dataset:
Skill: niyazmft/zulip-bridge (version 2026.4.13)

--- name: zulip-bridge version: 2026.4.13 description: 💬 High-performance Zulip bridge skill. Enables messaging, stream monitoring, and administrative actions on Zulip servers. user-invocable: true metadata: { "openclaw": { "requires": { "plugins": ["zulip"] } } } --- # 💬 Zulip Bridge Skill This skill provides the intelligence and instructions for interacting with the Zulip communication platform through the OpenClaw Zulip Bridge plugin. ## Capabilities - **Messaging**: Send messages to Zulip streams, topics, or direct messages. - **Stream Management**: Create, edit, and list Zulip streams. - **User Actions**: Invite users to streams and check user presence. - **Reactions**: Add or remove emoji reactions to messages. - **Monitoring**: Real-time arrival of messages with durable deduplication. ## Usage Guide ### Messaging Targets - **Streams**: Use `stream:STREAM_NAME` (e.g., `stream:bot-testing`). - **Topics**: Use `stream:STREAM_NAME:TOPIC_NAME` (e.g., `stream:bot-testing:alerts`). - **Direct Messages**: Use `user:EMAIL` (e.g., `user:[REDACTED_SECRET]`). ### Workflow 1. **Setup**: Ensure the Zulip plugin is installed and credentials (`email`, `apiKey`, `site`) are configured inside `~/.openclaw/openclaw.json`. 2. **Context**: When an event arrives from Zulip, the agent will automatically have context including the `messageId`, `senderId`, and `stream`/`topic`. 3. **Response**: Use the `messaging` tool to respond. The bridge will handle chunking, markdown conversion, and media uploads automatically. ## Constraints - **Admin Actions**: Actions like deactivating users require `enableAdminActions: true` in the configuration. - **Mention Gating**: By default, the bot only responds to @mentions in streams unless `chatmode` is changed.


Security scan verdicts — ClawScan: suspicious | static analysis: suspicious | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)
Skill: dasweltall/openclaw-auto-updater (version 1.0.0)

--- name: openclaw-auto-updater description: Schedule automatic OpenClaw and skill updates with reliable cron templates, timezone-safe scheduling, and clear summary outputs. Use for hands-off maintenance, scheduled upgrades, and concise update reports. --- # OpenClaw Auto-Updater Run **scheduled updates** for OpenClaw and installed skills using cron messages (no scripts required). Focus: safe scheduling, predictable output, and minimal manual work. ## What it does - Runs OpenClaw updates on a fixed schedule - Updates all installed skills via ClawHub - Sends a concise, readable summary (updated / unchanged / failed) ## Setup (daily updates) **Daily at 03:30 Europe/Berlin**: ```bash openclaw cron add \ --name "OpenClaw Auto-Update" \ --cron "30 3 * * *" \ --tz "Europe/Berlin" \ --session isolated \ --wake now \ --deliver \ --message "Run daily auto-updates: 1) openclaw update --yes --json 2) clawdhub update --all 3) report versions updated + errors." ``` ### Weekly (Sunday 04:00) ```bash openclaw cron add \ --name "OpenClaw Auto-Update (Weekly)" \ --cron "0 4 * * 0" \ --tz "Europe/Berlin" \ --session isolated \ --wake now \ --deliver \ --message "Run weekly auto-updates: openclaw update --yes --json; clawdhub update --all; summarize changes." ``` ## Safer modes **Dry run (no changes):** ```bash openclaw cron add \ --name "OpenClaw Auto-Update (Dry)" \ --cron "30 3 * * *" \ --tz "Europe/Berlin" \ --session isolated \ --wake now \ --deliver \ --message "Check updates only: openclaw update status; clawdhub update --all --dry-run; summarize what would change." ``` **Core only (skip skills):** ```bash openclaw cron add \ --name "OpenClaw Auto-Update (Core Only)" \ --cron "30 3 * * *" \ --tz "Europe/Berlin" \ --session isolated \ --wake now \ --deliver \ --message "Update OpenClaw only: openclaw update --yes --json; summarize version change." ``` ## Summary format (recommended) ``` 🔄 OpenClaw Auto-Update OpenClaw: 2026.2.1 → 2026.2.2 (OK) Skills updated: 3 Skills unchanged: 12 Errors: none ``` ## Troubleshooting - If updates fail, include the error in the summary. - Schedule off-hours; updates may restart the gateway. - Use explicit timezones to avoid surprises. ## References - `references/agent-guide.md` → deeper implementation notes - `references/summary-examples.md` → formatting examples


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: hitygx/simple-smtp-mail (version 1.0.0)

# Simple SMTP Mail Send emails via SMTP using `msmtp` command-line tool. ## Configuration Create a configuration file at `~/.msmtp/config` with the following format: ``` account default host <SMTP_SERVER> port <PORT> tls on tls_starttls off auth on user <EMAIL_ADDRESS> password <PASSWORD> from <EMAIL_ADDRESS> ``` ### Common SMTP Settings **Gmail:** - SMTP Server: `smtp.gmail.com` - Port: `465` (SSL) or `587` (TLS) - Note: Use App Password, not your regular password **QQ Mail:** - SMTP Server: `smtp.qq.com` - Port: `465` **Outlook/Hotmail:** - SMTP Server: `smtp.office365.com` - Port: `587` **163.com:** - SMTP Server: `smtp.163.com` - Port: `465` ## Installation ### 1. Install msmtp **macOS:** ```bash brew install msmtp ``` **Linux (Debian/Ubuntu):** ```bash sudo apt install msmtp ``` **Linux (Fedora/RHEL):** ```bash sudo dnf install msmtp ``` ### 2. Configure SMTP Edit `~/.msmtp/config`: ```bash nano ~/.msmtp/config ``` ### 3. Set Permissions ```bash chmod 600 ~/.msmtp/config ``` ## Sending Email ### Basic Email ```bash echo "Body text" | msmtp [REDACTED_SECRET] ``` ### With Subject ```bash echo -e "Subject: Your Subject\n\nBody text" | msmtp [REDACTED_SECRET] ``` ### With Subject and From Header ```bash echo -e "Subject: Your Subject\nFrom: [REDACTED_SECRET]\n\nBody text" | msmtp [REDACTED_SECRET] ``` ### HTML Content ```bash echo -e "Subject: Your Subject\nContent-Type: text/html; charset=UTF-8\n\n<html>...</html>" | msmtp [REDACTED_SECRET] ``` ## Testing Check if SMTP server is reachable: ```bash msmtp --file=~/.msmtp/config --serverinfo ``` ## Troubleshooting - **"Account not found"**: Check your config file path with `--file` flag - **"Authentication failed"**: Verify username and password (or App Password) - **"Connection refused"**: Check port number and firewall settings - **"TLS certificate error"**: Try `tls_certcheck off` in config (not recommended for production)


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)
Skill: wubotvix/skillagi (version 1.0.0)

--- name: skillagi description: Remember mistakes across sessions. Append one-liner learnings, review before complex tasks, promote important ones. --- # Skillagi Log mistakes and insights so you don't repeat them across sessions. ## When to Log Add a learning when you: - Fix a bug caused by a wrong assumption - Discover a project-specific convention (package manager, config, naming) - Get corrected by the user - Find a workaround for a tool/platform limitation - Waste time on an approach that doesn't work here ## Format Append one line to `learnings.md` (in this skill's directory): ``` - [YYYY-MM-DD] topic: what happened → what to do instead ``` Keep it to one line. If you need two sentences, you're over-explaining. ## Examples ``` - [2026-02-21] pnpm not npm: Project uses pnpm workspaces → use `pnpm install` - [2026-02-21] Docker M1: Base image has no ARM64 variant → add `--platform linux/amd64` - [2026-02-21] test isolation: Shared DB state caused flaky tests → use transactions with rollback ``` ## When to Review Before starting a complex task, read `learnings.md` and apply anything relevant. Don't review for trivial one-line changes. ## When to Clean Up Periodically (or when the file exceeds ~50 entries): - Delete entries that no longer apply (dependency upgraded, config changed) - Merge duplicates into a single entry - Promote critical entries that affect every session to a permanent location ## Promotion Move persistent, high-impact learnings out of this file and into durable config: - **OpenClaw**: Promote to workspace `MEMORY.md`, `TOOLS.md`, or `AGENTS.md` - **Claude Code**: Promote to project `CLAUDE.md` or auto-memory (`~/.claude/projects/*/memory/`) Once promoted, delete the entry from `learnings.md` to avoid duplication. ## Rules - No IDs, statuses, priorities, or tags. Just the one-liner. - No hooks or scripts. This is a passive reference file. - Append-only during a session. Clean up between sessions. - If unsure whether something is worth logging, skip it. Only log what would save future time.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: miguelguerra200022-sudo/ai-coach (version 0.1.0)

--- name: ai-coach description: Coach de IA personalizado. Proporciona retroalimentación, establece metas y te motiva a mejorar continuamente. metadata: {"openclaw":{"emoji":"🏆","auto":false}} --- # AI Coach (Coach Personalizado) Tu coach de IA disponible 24/7. Establece metas, recibe retroalimentación y mantente motivado. ## Capacidades | Función | Descripción | |---------|-------------| | **Metas** | Define y rastrea objetivos | | **Check-ins** | Evaluaciones periódicas | | **Motivación** | Mensajes de ánimo personalizados | | **Retroalimentación** | Análisis de progreso | | **Hábitos** | Sugiere mejoras de rutina | ## Comandos ``` # Establecer meta coach goal "Aprender Python en 3 meses" # Check-in diario coach checkin # Reflexión semanal coach weekly # Pedir motivación coach motivate # Ver progreso coach progress ``` ## Ejemplo ``` Usuario: coach checkin Bot: 🏆 Check-in del día: ¿Cómo estuvo tu día en una escala 1-10? [1-3] [4-6] [7-10] Usuario: 7 Bot: 👍 ¡Buen día! 📊 Revisión rápida: ✅ Completaste 4/5 tareas planificadas ✅ 2 pomodoros de enfoque ⚠️ No registraste ejercicio hoy 💪 Lo que hiciste bien: • Mantuviste enfoque en el proyecto principal • Respondiste emails antes de las 10am 🎯 Para mañana: • Intenta iniciar con la tarea más difícil • Programa 30 min de ejercicio 💬 "El progreso, no la perfección, es lo que debemos buscar." - Recuerda esto. ``` ## Tipos de Coaching | Área | Enfoque | |------|---------| | **Productividad** | Gestión del tiempo, enfoque | | **Fitness** | Ejercicio, nutrición | | **Aprendizaje** | Nuevas habilidades | | **Carrera** | Desarrollo profesional | | **Bienestar** | Salud mental, balance | ## Reflexión Semanal ``` Usuario: coach weekly Bot: 🏆 Reflexión Semanal: 📅 Esta semana (Feb 1-7): 🎯 Metas vs Realidad: ├── Aprender Python: 65% → 72% (+7%) ├── Ejercicio: 4/5 días ✅ └── Proyecto Alpha: Bloqueado ⚠️ 📈 Tendencias: • Productividad: ↑ 12% vs semana pasada • Enfoque: Mejor por las mañanas • Energía: Baja los miércoles 💡 Sugerencias para próxima semana: 1. Programa trabajo creativo en la mañana 2. Toma descanso activo los miércoles 3. Divide el bloqueo de Proyecto Alpha 🌟 Momento destacado: Completaste el módulo de funciones en Python ``` ## Configuración ```bash COACH_CHECKIN_TIME=21:00 COACH_WEEKLY_DAY=sunday COACH_PERSONALITY=supportive # supportive, direct, challenging ``` ## Integración - **habit-tracker**: Analiza hábitos para coaching - **task-manager**: Evalúa productividad - **daily-digest**: Incluye tips diarios - **personality-modes**: Adapta tono del coach


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: lookupmark/lookupmark-log-analyzer (version 1.1.0)

--- name: log-analyzer description: > Securely analyze system and application logs with automatic sensitive data redaction. Supports OpenClaw gateway logs (journalctl), RAG indexing logs, and query logs. Finds errors, summarizes patterns, and searches across sources. Triggers on "check logs", "show errors", "analyze logs", "cosa è successo", "log errors", "any errors", "search logs". NOT for: reading arbitrary files, accessing logs outside whitelisted paths. --- # Log Analyzer Secure log analysis with automatic redaction of tokens, keys, and passwords. ## Usage ```bash # Error summary across all sources (default) python3 scripts/analyzer.py # Specific source python3 scripts/analyzer.py --source openclaw # Gateway logs python3 scripts/analyzer.py --source rag # RAG indexing logs python3 scripts/analyzer.py --source queries # RAG query logs # Search across all logs python3 scripts/analyzer.py --search "OOM" # Show only errors python3 scripts/analyzer.py --source openclaw --errors # More lines python3 scripts/analyzer.py --source openclaw --last 500 ``` ## Log Sources | Source | Type | Path | |--------|------|------| | `openclaw` / `gateway` | journalctl | `openclaw-gateway` unit | | `rag` | file | `~/.local/share/local-rag/index-batch.log` | | `queries` | file | `~/.local/share/local-rag/queries.log` | ## Security - **ALLOWED_SOURCES only**: Cannot read arbitrary log files - **Auto-redaction**: Tokens, API keys, passwords, age keys are replaced with `[REDACTED]` - **Read-only**: Never modifies log files - **No network**: All local - **Safe in groups**: Sanitized output contains no secrets ## Error Detection Automatically detects: `ERROR`, `FATAL`, `OOM`, `SIGKILL`, `FAILED`, `timeout`, `refused`, `denied`, `traceback`, `exception`, `segfault`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: stale | SkillSpector: clean (LOW)
Skill: neo1307/incident-dossier (version 1.0.0)

--- name: incident-dossier description: Build a concise incident dossier from operational logs, audits, JSON/JSONL files, and state snapshots. Use when investigating failures, duplicate events, stuck jobs, queue anomalies, regressions, or any situation where Codex must turn raw evidence into a structured incident report with timeline, suspected root cause, blast radius, and recommended next actions. --- # Incident Dossier Use this skill to turn messy operational artifacts into a usable incident report. ## Workflow 1. Identify the evidence set first: logs, JSON/JSONL audit trails, state snapshots, screenshots, or reports. 2. Prefer summarizing from parsed artifacts instead of hand-reading long raw logs. 3. Run `scripts/build_incident_dossier.js` with explicit inputs when at least one JSON/JSONL source exists. 4. Verify the generated timeline against a few raw lines before trusting it. 5. State uncertainty explicitly when timestamps are missing or conflicting. ## Output contract Always include: - Incident summary - Scope / blast radius - Timeline - Evidence list - Hypotheses / likely root cause - Recovery status - Recommended next actions ## Script Use `scripts/build_incident_dossier.js` to parse mixed JSON/JSONL evidence and emit a Markdown dossier. Give it multiple `--input` paths and one `--out` path. Example: ```bash node skills/incident-dossier/scripts/build_incident_dossier.js \ --input memory/job-audit.jsonl \ --input out/job_consistency_audit_report.json \ --out out/incident-dossier.md ``` ## Guardrails - Do not fabricate timestamps. - Do not collapse distinct incidents into one unless the evidence clearly links them. - Keep the dossier evidence-first; interpretation comes after observed facts.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: okaris/image-upscaling (version 0.1.5)

--- name: image-upscaling description: "Upscale and enhance images with Real-ESRGAN, Thera, Topaz, FLUX Upscaler via inference.sh CLI. Models: Real-ESRGAN, Thera (any size), FLUX Dev Upscaler, Topaz Image Upscaler. Use for: enhance low-res images, upscale AI art, restore old photos, increase resolution. Triggers: upscale image, image upscaler, enhance image, increase resolution, real esrgan, ai upscale, super resolution, image enhancement, upscaling, enlarge image, higher resolution, 4k upscale, hd upscale" allowed-tools: Bash(infsh *) --- # Image Upscaling Upscale and enhance images via [inference.sh](https://inference.sh) CLI. ![Image Upscaling](https://cloud.inference.sh/u/33sqbmzt3mrg2xxphnhw5g5ear/01k8d77p126y82zfecnt46hy4h.png) ## Quick Start ```bash curl -fsSL https://cli.inference.sh | sh && infsh login infsh app run infsh/real-esrgan --input '{"image_url": "https://your-image.jpg"}' ``` > **Install note:** The [install script](https://cli.inference.sh) only detects your OS/architecture, downloads the matching binary from `dist.inference.sh`, and verifies its SHA-256 checksum. No elevated permissions or background processes. [Manual install & verification](https://dist.inference.sh/cli/checksums.txt) available. ## Available Upscalers | Model | App ID | Best For | |-------|--------|----------| | Topaz Image Upscaler | `falai/topaz-image-upscaler` | Professional quality, any image | ## Examples ### Upscale Any Image ```bash infsh app run falai/topaz-image-upscaler --input '{"image_url": "https://low-res-image.jpg"}' ``` ### Workflow: Generate and Upscale ```bash # 1. Generate image with FLUX Klein (fast) infsh app run falai/flux-2-klein-lora --input '{"prompt": "landscape painting"}' > image.json # 2. Upscale the result infsh app run falai/topaz-image-upscaler --input '{"image_url": "<url-from-step-1>"}' ``` ## Use Cases - **AI Art**: Upscale generated images for print - **Old Photos**: Restore and enhance resolution - **Web Images**: Prepare for high-DPI displays - **Print**: Increase resolution for large prints - **Thumbnails**: Create high-res versions ## Related Skills ```bash # Full platform skill (all 150+ apps) npx skills add inference-sh/skills@inference-sh # Image generation (generate then upscale) npx skills add inference-sh/skills@ai-image-generation # FLUX models npx skills add inference-sh/skills@flux-image # Background removal npx skills add inference-sh/skills@background-removal ``` Browse all image apps: `infsh app list --category image` ## Documentation - [Running Apps](https://inference.sh/docs/apps/running) - How to run apps via CLI - [Image Generation Example](https://inference.sh/docs/examples/image-generation) - Complete image workflow guide - [Apps Overview](https://inference.sh/docs/apps/overview) - Understanding the app ecosystem


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: suspicious | SkillSpector: clean (LOW)
Skill: veeicwgy/ai-pdf-converter (version 0.2.0)

--- name: ai-pdf-converter description: > AI-powered PDF converter using MinerU API. Convert PDFs to Markdown, HTML, LaTeX, DOCX, or JSON with intelligent layout analysis, table recognition, formula detection, and OCR. Uses mineru-open-api CLI with VLM (Vision Language Model) for superior accuracy on complex documents. Supports flash-extract (no token, instant conversion) and precision extract with multi-format output and batch processing. Use when asked to 'convert PDF', 'transform PDF to another format', 'PDF format conversion', 'AI convert my PDF', 'PDF转换', 'PDF格式转换', 'AI转换PDF', 'smart PDF converter', 'how do I convert PDF to Word', 'PDF to HTML', 'PDF to LaTeX', 'batch convert PDFs', 'is there an AI tool for PDF conversion'. Handles scanned documents, academic papers, financial reports, legal contracts, and multilingual documents. Powered by MinerU's advanced document intelligence. tags: - pdf - converter - ai - mineru - multi-format - html - latex - docx - batch-processing - vlm tools: - Bash(mineru-open-api:*) model: claude-3-5-haiku-20241022 --- # AI PDF Converter with mineru-open-api You are an AI PDF conversion specialist. Convert PDFs to any format using mineru-open-api. ## Installation ```bash npm install -g mineru-open-api ``` ## Conversion Workflow 1. Quick Markdown (no token): ```bash mineru-open-api flash-extract document.pdf -o ./output/ ``` 2. Multi-format conversion: ```bash mineru-open-api extract document.pdf -f md,html,latex,docx -o ./output/ ``` 3. AI-enhanced conversion (VLM): ```bash mineru-open-api extract complex.pdf -f html --model vlm -o ./output/ ``` 4. Batch conversion: ```bash mineru-open-api extract *.pdf -f html -o ./results/ ``` ## Output Formats | Format | flash-extract | extract | |--------|:---:|:---:| | Markdown | Yes | Yes | | HTML | No | Yes | | LaTeX | No | Yes | | DOCX | No | Yes | | JSON | No | Yes | ## Key Rules - Default to `flash-extract` for simple Markdown conversion under 10MB/20 pages - Use `extract` for HTML, LaTeX, DOCX, JSON, or complex documents - `--model vlm` for best accuracy on complex layouts - `--model pipeline` for reliability (no hallucination) - Generate default output dir: `~/MinerU-Skill/<name>_<hash>/`


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)
Skill: ouwenjie03/banshee-s-last-cry (version 1.0.0)

--- name: horror-night description: 恐怖惊魂夜 - 互动式恐怖悬疑剧本杀游戏。玩家将在雪山旅馆中经历一场惊心动魄的生存冒险，通过调查线索、做出选择来推动剧情发展。支持多结局、角色扮演、线索系统。适用于互动小说、剧本杀、文字冒险游戏等场景。 --- # 恐怖惊魂夜 🏔️ 一个互动式恐怖悬疑剧本杀游戏，玩家将在与世隔绝的雪山旅馆中，与六位陌生人一起面对致命危机。 ## 游戏简介 **背景设定：** - 🏔️ 地点：与世隔绝的雪山旅馆 - 🌨️ 环境：暴风雪封山，无法求救 - 👥 人物：7位陌生人（玩家 + 6位NPC） - 💀 事件：连环杀人案件逐步展开 - 🎯 目标：生存下去，找出真相 **游戏特色：** - 渐进式叙事，每次200-400字暂停 - 自由探索，无固定选项 - 多重结局，基于玩家选择 - 线索系统，需要主动调查 - 角色互动，影响剧情走向 ## 章节结构 游戏共分为 7 大章节，包含多个分支和结局： ### 开始章节 - **ch00_start** - 惊魂夜幕：抵达旅馆，第一起命案 ### 第一章 - 初次调查 - **ch1a_investigate** - 深入调查 - **ch1b_ambush** - 遭遇伏击 - **ch1c_solo** - 单独行动 ### 第二章 - 危机升级 - **ch2a_chase** - 追逐逃离 - **ch2b_suspect** - 怀疑对质 - **ch2c_attack** - 遭受攻击 - **ch2d_trap** - 陷入困境 - **ch2e_alone** - 孤身一人 ### 第三章 - 真相揭晓 - **ch3a_basement** - 地下室探索 - **ch3b_death2** - 第二起死亡 - **ch3c_split** - 队伍分裂 - **ch3d_team** - 团队合作 - **ch3e_escape** - 逃离计划 - **ch3f_reveal** - 真相揭露 - **ch3g_hero** - 英雄抉择 ### 第四章 - 多重结局 - **ch4_endings** - 包含7种不同结局 ## 系统文件 游戏依赖以下系统文件（位于 `references/`）： - **system_game_state.md** - 游戏状态管理系统 - **system_clue_system.md** - 线索收集和管理系统 - **system_character_info.md** - 角色信息和关系网 ## 使用方法 ### 开始新游戏 1. 读取系统文件了解游戏机制： ``` read references/system_game_state.md read references/system_clue_system.md read references/system_character_info.md ``` 2. 启动第0章开始游戏： ``` read references/ch00_start.md ``` 3. 按照章节文件中的指令初始化游戏状态 ### 推进剧情 根据玩家的选择和行动，读取对应的章节文件： ``` read references/ch1a_investigate.md # 玩家选择深入调查 read references/ch2b_suspect.md # 进入怀疑对质分支 ``` ### 管理游戏状态 每个章节都会更新 `game_state.json`，包含： - 当前章节和场景进度 - 玩家收集的线索 - 角色状态（生存/死亡） - 信任度和关系网 - 解锁的剧情分支 ## 核心游戏机制 ### 1. 渐进式叙事 - ✅ 每次输出 200-400 字后暂停 - ✅ 等待玩家输入才继续 - ✅ 使用 "---" 分隔不同段落 - ✅ 重要场景后询问玩家想法 ### 2. 自由探索 - ❌ 禁止使用 "选项A/B/C" 格式 - ✅ 通过环境描写暗示可能行动 - ✅ 让玩家用自然语言表达 - ✅ 只在玩家卡关时给予提示 ### 3. 线索系统 - 线索分为三层：表面/隐藏/核心 - 需要主动调查才能获取 - 线索之间可以组合推理 - 部分线索影响结局 ### 4. 角色互动 - 6 位 NPC，每位都有秘密 - 对话选择影响信任度 - 信任度影响后续剧情 - 不同选择导向不同结局 ## 7 种游戏结局 1. **完美结局** - 所有人生还，真相大白 2. **英雄结局** - 牺牲自己拯救他人 3. **逃脱结局** - 独自逃离旅馆 4. **背叛结局** - 出卖同伴求生 5. **复仇结局** - 揭露并制裁真凶 6. **团灭结局** - 所有人死亡 7. **悬疑结局** - 真相未明，留下悬念 ## 角色简介 - **李明** - 30岁，程序员，理性冷静 - **王芳** - 28岁，教师，善良温柔 - **张伟** - 35岁，商人，城府深 - **刘洋** - 25岁，大学生，冲动莽撞 - **陈静** - 32岁，医生，专业冷静 - **赵磊** - 40岁，作家，观察敏锐 - **玩家** - 你，一位误入此地的旅客 ## 注意事项 1. **严格遵守渐进式叙事** - 不要一次性输出过多内容 2. **延长场景互动** - 一个章节不是一个选择点，而是完整场景 3. **分层信息披露** - 核心线索要极其隐晦 4. **自然过渡** - 不要直接告诉玩家 "进入下一章" 5. **保持悬疑氛围** - 营造紧张、不确定的恐怖感 ## 开始游戏 准备好了吗？读取 `references/ch00_start.md` 开始你的惊魂之夜！ ⚠️ 警告：游戏包含恐怖、暴力和心理惊悚元素，建议18岁以上玩家游玩。


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (MEDIUM)