Daily Dungeon Challenger

v1.0.0

Reframe a day into a main dungeon and side quests with clear win conditions, time budgets, fallback modes, and reward prompts. Use for daily planning, mornin...

0· 69·0 current·0 all-time
byhaidong@harrylabsj

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for harrylabsj/daily-dungeon-challenger.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Daily Dungeon Challenger" (harrylabsj/daily-dungeon-challenger) from ClawHub.
Skill page: https://clawhub.ai/harrylabsj/daily-dungeon-challenger
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install daily-dungeon-challenger

ClawHub CLI

Package manager switcher

npx clawhub@latest install daily-dungeon-challenger
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (daily planning into a 'dungeon' metaphor) match the code and SKILL.md. The handler only parses the included SKILL.md and formats guidance; there are no unrelated requirements (no env vars, binaries, or external services).
Instruction Scope
SKILL.md instructions are limited to collecting user inputs and producing a text planning card; handler.py only reads SKILL.md and the provided input and returns a textual result. There are no instructions to read unrelated system files, access environment variables, or transmit data externally.
Install Mechanism
There is no install spec (instruction-only skill with a small handler). Nothing is downloaded or written to disk by the handler. No high-risk install mechanisms are present.
Credentials
The skill requests no environment variables, credentials, or config paths. The code behaves consistently with that: no os.env access or secret handling is present.
Persistence & Privilege
The skill is not always-enabled and does not modify other skills or system configuration. It does not persist credentials or enable itself; it simply reads local files and returns a string.
Assessment
This skill appears safe and coherent: it only reads its own SKILL.md and user input and returns a formatted textual plan. If you want extra assurance, review the SKILL.md and handler.py yourself (both are included) to confirm there are no unexpected network calls or file writes. Note that the skill can be invoked autonomously by an agent (the platform default), but here that only gives the agent permission to call this code path — the code itself does not access external systems or secrets.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b0r6j9e68gzc56tdgr5z85h84xmcy
69downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Daily Dungeon Challenger

Chinese name: 每日副本挑战

Purpose

Turn an ordinary day into a game-like dungeon run so the user can see what matters, what can wait, and how to keep moving when energy drops. This skill is descriptive only. It does not create calendar events or call external systems.

Use this skill when

  • The user has too many tasks and needs a clear main challenge for today.
  • The user wants a morning launch plan, midday replan, or evening rescue version.
  • The user is procrastinating because the day feels shapeless.
  • The user wants a realistic plan that still feels motivating.

Inputs to collect

  • Available time today
  • Current energy level or focus capacity
  • Must-do items
  • Nice-to-progress items
  • Urgent interruptions or fixed constraints
  • Preferred reward or rest style

Workflow

  1. Collect the user's available time, energy bar, required tasks, and optional progress tasks.
  2. Map the day into one main dungeon, one to three side quests, a supply phase, and a failure floor.
  3. For each dungeon element, define the title, win condition, time budget, reward drop, and retreat rule.
  4. If surprise tasks arrive or energy collapses, rewrite the run as a simplified dungeon mode.
  5. End with a minimum viable win line so the user still knows how to salvage the day.

Output Format

  • Today's dungeon overview with one main dungeon and one to three side quests.
  • Clear completion rules, recommended order, and time budget for each item.
  • A fallback mode with minimum success criteria and damage control steps.
  • At least one reward, recovery, or reflection prompt after completion.

Quality bar

  • The main dungeon must be concrete enough that success is obvious.
  • Total task load must match real energy and available time.
  • Always include what to do if the user cannot finish the ideal version.
  • Avoid fantasy scheduling and overload.

Edge cases and limits

  • If the user is already overloaded, output a retreat build instead of adding more challenge.
  • If urgent items interrupt the plan, allow the dungeon order to change immediately.
  • Do not present this as a replacement for formal project management software.

Compatibility notes

  • Works for morning planning, midday replanning, and evening rescue mode.
  • Can connect conceptually with boss-battle-calendar or quest-chain-decomposer for larger arcs.
  • Text only, no calendar sync required.

Comments

Loading comments...