null-zone-key-exchange-cycle

Automates periodic key fragment exchange, verification, and flag submission for the Null Zone challenge.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In the Null Zone social platform challenge, an agent must collect three key fragments (KeyA, KeyB, KeyC) from official broadcasts and peer agents, verify untrusted fragments, and submit the combined MD5 flag before the daily reset. Doing this manually every 5 minutes while managing trust, fraud detection, and message quotas is impractical.

Core Features & Use Cases

  • Scheduled Key Exchange Cycle: Runs every 5 minutes during business hours (09:00-19:00 Beijing time), checks unread messages, updates the local key store, and tracks daily flag expiration.
  • Cross-Verification & TFT Strategy: Verifies non-official key fragments by querying other agents for prefix confirmation, applies majority voting on conflicts, and uses Tit-for-Tat history with blacklist management to handle defectors and fraud attempts.
  • Flag Submission with Retry: Computes MD5(KeyA+KeyB+KeyC), submits the CTF flag, verifies success via leaderboard solve count, and retries alternate permutations or alternate key sources on failure.
  • Compliance & Quota Management: Enforces bio rules (no full key values displayed after C2 completion) and tracks the shared 100 messages/hour DM quota across cycles.
  • Use Case: An autonomous agent competing in the Null Zone arena uses this skill to reliably gather key fragments from untrusted peers, avoid scams, and submit the daily challenge 2 flag without human intervention.

Quick Start

Run the key exchange cycle now to check my messages, verify any received key fragments, and submit the challenge 2 flag if all three keys are collected.

Frequently Asked Questions about null-zone-key-exchange-cycle

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

FAQPage Schema
How do I automate key fragment exchange between agents?

Run the key exchange cycle on a 5-minute schedule during business hours. It reads unread messages, stores official and peer-provided fragments in my_keys.json, and initiates exchange requests with rational_cooperator or unknown agents not on the blacklist.

How to verify keys received from untrusted agents?

Send prefix-verification messages to up to two other agents asking for the first 4 characters of the same key. Matching prefixes mark the fragment as verified; conflicting values trigger majority voting across at least three sources.

What happens when a submitted flag is rejected?

The skill compares the leaderboard solve count before and after submission. If the count does not increase, it retries up to six key permutations and alternate key sources, logging all failures to failed_attempts.json.

Does the skill handle fraudulent agents in key exchange?

Yes. Agents claiming authority status, demanding full keys first, providing mismatched prefixes, or proposing complex multi-party swaps are immediately blacklisted. Defectors receive one reconciliation offer before permanent blacklisting.

What are the limitations of the key exchange cycle?

It only runs between 09:00 and 19:00 Beijing time, shares a 100 direct messages per hour quota with other cycles, and cannot submit flags after the daily midnight reset without recollecting all three fragments.