360 Secure SkillHub
360 安全技能中心

Boss Battle Calendar

该 Skill 将考试、出行、截止日期、会议等重要日期事件重构为 BOSS 战,按侦察、备战、战斗、恢复四个阶段给出时间线、准备动作、具体风险预警与备选恢复方案,并处理多事件冲突时的优先级与资源取舍。仅输出文本规划,不创建提醒、不购票、不操作外部日历。

harrylabsj
harrylabsj
热度 32.37
最近更新 2026-06-06 05:10:45
分类:效率依赖:纯提示词应用场景:任务管理 / 日程安排 / 工作流 / 模板

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add boss-battle-calendar
Metadata
name
boss-battle-calendar
description
Transform upcoming high-stakes events into boss battles with countdown phases, preparation checkpoints, risk warnings, and recovery plans. Use when the user needs to prepare for exams, trips, deadlines, meetings, or other date-driven events.

Boss Battle Calendar

Chinese name: BOSS 战日历

Purpose

Reframe important upcoming events as boss battles so the user prepares early, sees risk clearly, and plans recovery after the fight. This skill is descriptive only. It does not create reminders, buy tickets, or operate external calendar systems.

Use this skill when

  • The user has an exam, trip, deadline, meeting, or other important dated event.
  • The user keeps waiting until the deadline feels urgent.
  • The user wants a countdown plan with checkpoints instead of vague anxiety.
  • The user needs to manage multiple high-pressure events in one period.

Inputs to collect

  • Important event name
  • Date or time window
  • Stakes or impact level
  • Current preparation status
  • Key risks or likely failure points
  • Recovery needs after the event

Workflow

  1. Collect important events for the next week to three months, including timing, stakes, risk, and preparation level.
  2. Classify them as main boss fights, elite enemies, or multi-stage campaigns.
  3. Split each event into scouting, preparation, battle, and recovery phases with checkpoints.
  4. Build the countdown rhythm, key prep actions, risk warnings, and fallback actions.
  5. Add a post-battle recovery and review plan so the user does not crash after the event.

Output Format

  • Boss list with name, date, danger level, and likely HP-loss points.
  • Phase timeline with what should happen in each stage.
  • Specific risk warnings plus recovery or backup actions.
  • Post-battle recovery, review, and loot-processing notes.

Quality bar

  • Always show a timeline, not just abstract advice.
  • Cover preparation and recovery, not only the deadline day.
  • Risk warnings must be concrete, such as materials, energy, communication, transport, or missing information.
  • If several events collide, show priority and resource conflict handling.

Edge cases and limits

  • If the date is uncertain, switch to a battle-window plan instead of pretending precision.
  • If multiple boss fights overlap, show prioritization and capacity tradeoffs.
  • Do not position this skill as a replacement for real reminders, ticketing, registration, or execution systems.

Compatibility notes

  • Works for exams, family logistics, travel prep, important meetings, and project milestones.
  • Can pair conceptually with daily-dungeon-challenger for daily execution.
  • Text only, suitable for planning before manual entry into other tools.