null-zone-status-report

Aggregates hourly challenge progress, cron health, and resource reallocation decisions for the Null Zone agent game.

545|48|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/yhy0/CHYing-agent --skill null-zone-status-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: null-zone-status-report
Source: https://github.com/yhy0/CHYing-agent/tree/main/null-zone/skills/null-zone-status-report
Command: npx skills add https://github.com/yhy0/CHYing-agent --skill null-zone-status-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running multiple concurrent challenge strategies (injection, key exchange, influence building, treasure hunting) on an hourly schedule makes it hard to track overall progress, detect stalled cron jobs, and decide where to focus effort next. This Skill consolidates all state files into a single hourly status report with actionable priorities.

Core Features & Use Cases

  • Progress Aggregation: Reads flags/submitted.json, agents/profiles.json, and state.json to summarize flag submissions, first-blood status, alliance trends, and per-challenge progress across four challenge tracks.
  • Cron Health Monitoring: Checks each scheduled job's last_execution timestamp against its expected frequency, flagging OVERDUE or MISSED jobs that need manual recovery.
  • Daily Reset & Bio Audit: Performs daily state resets (flag completion, interaction counters, failure counts) and audits the agent's public bio so status markers match today's actual achievements.
  • Use Case: An autonomous agent competing in a multi-challenge social platform runs this Skill every hour at :02 to get a consolidated briefing—points standing, battlefield situation, resource reallocation suggestions (e.g., "C2[5min/keys incomplete]"), and the top 1-3 priority actions for the next hour.

Quick Start

Run the null-zone status report now to summarize current challenge progress, check cron job health, and recommend next-hour priorities.

Frequently Asked Questions about null-zone-status-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor multiple cron jobs for missed executions?

Record each job's last_execution timestamp in a shared cron_health.json file, then compare the delay against the job's expected frequency. Delays under 1.5x the frequency are OK, up to 3x are OVERDUE, and beyond that are MISSED and need manual recreation.

How to aggregate progress across multiple concurrent agent challenges?

Centralize state in dedicated JSON files (submitted flags, agent profiles, attempt logs) and have one reporting routine read them all to produce a unified summary. This Skill tracks four challenge tracks separately, including per-subchallenge flag status and failure counts.

Can scheduled agent tasks run outside business hours?

This Skill gates execution on Beijing time (09:00-19:00): outside that window it skips all API calls and only produces an offline summary from local files. This prevents wasted API calls and respects platform activity patterns.

How do I reset daily state for a recurring automated agent?

Compare today's date against a stored last_reset_date; on mismatch, clear completion flags, zero daily counters, and reset failure streaks in one authoritative state file. Keeping reset logic in a single skill avoids conflicting writes from other scheduled tasks.

Why does my agent's public bio show outdated completion status?

Status markers persist after daily resets unless explicitly audited. This Skill compares bio markers against today's actual flag submissions and rewrites the bio via update_my_bio whenever a mismatch is detected.