keria-plus-pickup

Automates redeem-code pickup from plus.keria.cc.cd into a downloaded ZIP and unpacked directory.

2|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/zero-yx/static_flow --skill keria-plus-pickup-zero-yx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keria-plus-pickup
Source: https://github.com/zero-yx/static_flow/tree/main/skills/keria-plus-pickup
Command: npx skills add https://github.com/zero-yx/static_flow --skill keria-plus-pickup-zero-yx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually redeeming batches of pickup codes on plus.keria.cc.cd through the web UI is repetitive and error-prone. This Skill automates the multipart form POST to the site's /pickup endpoint, downloads the resulting ZIP bundle, and unpacks it locally with an explicit choice of output format. ## Core Features & Use Cases - Bulk Code Pickup: Submit a text file of pickup codes (one per line) to the /pickup endpoint in a single multipart request with browser-like headers. - Dual Output Formats: Choose between plus_json and sub2api bundle formats via an explicit --output-format flag. - Dry-Run and Result Verification: Preview the request plan with --dry-run, then inspect pickup.headers.txt and the unpacked 取件结果.txt to confirm success and failure counts. - Use Case: You receive 50 redeem codes in a text file and need them converted into a sub2api subscription bundle. Run the helper script with your codes file and output directory to get the ZIP and unpacked files in one step. ## Quick Start Use the keria-plus-pickup skill to redeem the codes in my codes.txt file from plus.keria.cc.cd and unpack the plus_json bundle into my output folder.

Frequently Asked Questions about keria-plus-pickup

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

FAQPage Schema
How do I bulk redeem pickup codes from plus.keria.cc.cd?▼

Place your codes in a text file with one code per line, then run the fetch_pickup_bundle.sh script with --codes-file, --output-dir, and --output-format. The script posts a multipart form to the /pickup endpoint and saves the ZIP plus an unpacked directory locally.

What output formats does the pickup endpoint support?▼

The /pickup endpoint supports two bundle formats: plus_json and sub2api. You must pass one explicitly via --output-format; the script rejects any other value and does not assume a default format.

Can I test the pickup request without actually calling the server?▼

Yes, use the --dry-run flag to print the request plan, including endpoint, code count, output directory, format, and progress ID, without executing the curl call. This lets you verify inputs before a real pickup.

How do I verify whether my code pickup succeeded?▼

After unpacking, check the 取件结果.txt file inside the unpacked directory if present. It reports success and failure counts for the submitted codes, and the script prints its contents automatically when found.

What tools are required to run the pickup script?▼

The script requires curl for the HTTP multipart POST, unzip for extracting the downloaded ZIP, and python3 for counting non-empty code lines. It checks for all three commands and exits with an error if any is missing.