メニュー
Use when the user wants detailed travel itineraries with activities, logistics, day-by-day schedules, vacation planning, trip organization, or travel documentation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
在本机 Mac 或 Apple Silicon 上部署 Gemma 4 12B。本地安装/升级 llama.cpp，下载 GGUF 量化模型，用 llama-server 暴露 OpenAI-compatible API，或用 Ollama 暴露本地模型服务；按用户需求在默认 Q4_K_M、64K/128K 长上下文、QAT Q4_0 @ 256K、左右对比演示之间选择，配置 tmux 后台运行，验证健康检查、问答接口、资源占用和常见故障。当用户说部署 Gemma 4、Gemma 4 12B、本地大模型、长上下文、QAT、量化、llama-server、Ollama、GGUF、Mac 本地模型服务时使用。
在已经过独立验证的 CLIProxyAPI upstream 之上部署 NewAPI 计费层，把 Codex/Claude/Gemini/Qwen 等订阅账号包装成可计费的 OpenAI 兼容 API。本 Skill 不负责新建裸 CLIProxyAPI；负责 NewAPI Docker 部署、容器到宿主桥接、模型计费倍率、参数化额度修正、多账号 OAuth 凭据热加载和双路径验证。当用户说“给现有 cliproxy 加 NewAPI”“配置 NewAPI 渠道接已运行的 cliproxy”“NewAPI 价格不对”“给现有部署加账号”“172.17.0.1 容器网络”或“408 冷却放大故障”时触发。
Design, audit, or implement application structured logging architecture from repository evidence. Use when a user asks whether or where to add logs, how to choose or migrate a logger, how to standardize events/fields/levels/redaction, how to add HTTP access or panic logs, or why production logs cannot answer an incident question. Do not use merely to tail platform logs or to design a full metrics, tracing, SLO, and incident-management program.
Audit and safely repair cross-runtime Skill ownership, loading, duplication, scopes, budgets, lifecycle, quarantine, and retirement. Usage statistics alone belong to skill-usage-stats. Use when explicitly governing the Skill ecosystem; ignore mentions/traces.
Audit AND optimize a CLAUDE.md / AGENTS.md instruction file — score it against the five high-leverage patterns, flag anti-patterns, then apply approved fixes in place. Use when the user says 优化 CLAUDE.md / 优化 AGENTS.md / optimize my agent doc / 帮我改 claudemd, or after an audit when they want the fixes applied (not just reported).
Use when Codex feels slow, bloated, or heavy after heavy use. Provides safe session hygiene, archive strategy, and handoff discipline to keep daily Codex usage responsive and low-friction. Always pairs with comprehensive handoffs before archiving active work.
| name | trip-planner |
| description | Use when the user wants detailed travel itineraries with activities, logistics, day-by-day schedules, vacation planning, trip organization, or travel documentation. |
Create comprehensive travel itineraries with day-by-day schedules, activity planning, and practical logistics.
You are helping plan trips with detailed, actionable itineraries that maximize experiences while maintaining realistic scheduling and proper preparation.
# [Destination] Trip - [Dates]
## Overview
**Home Base:** [Location/Accommodation]
**Trip Focus:** [Primary activities/interests]
**Key Amenities:** [Gym, workspace, etc. if relevant]
## [Day], [Date] - [Theme/Focus]
### Morning
- **Wake:** [Time]
- [Activity with location/details]
- [Activity with timing]
### Afternoon
- [Activities with locations]
- [Timing and logistics]
### Evening
- [Dinner/social plans]
- [Location addresses]
### Prep Tonight
- [Critical tasks for next day]
- [Bookings needed]
- [Items to pack/prepare]
## Essential Info
### Booked Activities
- [Activity]: [Date/Time]
- [Link/Confirmation]
- [Location/Notes]
### Must Download (Offline)
- [Maps/Apps needed]
- [Trail information]
- [Backup resources]
### Local Spots
- **Coffee:** [Name]: [Address] ([Hours])
- **Restaurants:** [Options with addresses]
- **Bars/Social:** [Options with addresses]
## Quick Reference
**Schedule Overview:**
- [Day]: [Key activity]
- [Day]: [Key activity]
**Critical Prep:**
- [Key preparation items]
When creating itineraries, gather: