Boss Battle Calendar

Transform upcoming high-stakes events into boss battles with countdown phases, preparation checkpoints, risk warnings, and recovery plans. Use when the user...

Security Scan

The skill's code and runtime instructions are consistent with its stated purpose (a text-only planning helper); it reads only its SKILL.md and returns a descriptive plan, requests no credentials, and performs no external actions.

Purpose & Capability

Name, description, SKILL.md instructions, and handler.py all align: the skill is a descriptive planner that formats guidance from SKILL.md and user input. There are no unexpected capabilities (no calendar integration, network calls, or cloud access).

Instruction Scope

SKILL.md limits the skill to collecting event/context from the user and producing a timeline and risk plan; handler.py implements only local parsing of SKILL.md and formatting of the output. It does not read unrelated files or environment variables, nor transmit data externally.

Install Mechanism

There is no install spec (instruction-only behavior with small accompanying code). Nothing is downloaded or written to arbitrary system paths by the skill.

Credentials

The skill declares no required environment variables, credentials, or config paths. The handler does not access environment variables or secrets.

Persistence & Privilege

The registry flags are default (always: false, model invocation allowed). The skill does not request permanent presence, nor does it modify other skills or system-wide settings.

Assessment

This skill appears to be a small, local, read-only planner: it reads its SKILL.md and formats a planning card based on user input. It requests no credentials and has no network or subprocess behavior. If you care about provenance, note the skill source/homepage is unknown—if you prefer, review handler.py yourself (it's short and readable) before installing. Also remember the skill is descriptive only: it will not create calendar reminders or perform external actions, so you'll need to enter plans into your calendar or task manager manually.

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.