About this skill

Problem

Government secondary packages often rely on manual WOP task creation, searching S3 for base installers, configuring OEM items, and handling plugin files. This skill turns those repetitive steps into explicit workflows: quick packaging, Win/Linux CLI builds, base-package lookup, OEM annotation, and knowledge Q&A.

How It Works

It combines WOP platform APIs with a local web service. The architecture separates concerns: scripts/apis/ exposes S3 and task operations, build.py orchestrates BuildParams, and scripts/server/ provides the browser-based management page. Key capabilities include:
- Package lookup: locate Win/Linux installers by branch, arch, category, version, or date, for example with s3_find_linux_package
- OEM annotation: use annotate_oem.py to add # comments to configuration items and optionally save annotated content as a template
- Packaging execution: start the local service with python -m server start, then configure branch, base package, and OEM settings at http://localhost:8066
- Task management: create, run, and poll jobs using wop_create_task, wop_run_task, and poll_job

Boundaries and Caveats

This skill is useful for engineers who frequently build WPS government packages, manage OEM templates, or locate base packages by branch. It requires Python 3.10+, and login capture needs local Chrome or Edge. It accesses fantasy.wps.cn and the local loopback endpoint 127.0.0.1:8066. Credentials are stored in .env, while runtime files such as PID and task caches are written under .runtime/, so these paths should not be committed. Knowledge Q&A or OEM explanation can use the relevant flow without starting the web service.

Screenshots

Use Cases

Before releasing a government WPS build, locate the latest Linux base package by branch and x64 architecture.
After receiving an OEM configuration, add comment lines for each item and save the annotated result as a reusable template.
When building a Windows government package, open the local web packager, select branch, base package, and OEM, then start the task.
During packaging failures, query WOP task lists and job details to verify creation, execution, and polling status.

Best For

Engineers maintaining WPS government builds who repeatedly create WOP packaging tasks and verify job status.
Release managers handling OEM settings who need to explain configuration items and save reusable templates.
Test engineers delivering installers by branch who need to find base packages by version, architecture, and date.
Team members coordinating builds via the local web page who manage OEM presets and packaging history.