Hack‑Astron x openKylin Challenge Officially Launches | Enriching the AI Skills Ecosystem of Operating Systems
2026-09-08 05:57:34
Please create works around the following themes:
- openKylin local deployment and Astron Agent/Skillhub skill development
- UKUI desktop automation configuration skills: one-click theme/wallpaper switching, batch adjustment of brightness and volume, taskbar layout configuration
- openKylin package management skills: automatic search, installation, upgrade, batch configuration of development environments
- Community operation automation skills: automatically fetch Gitee Issues/PRs, generate community weekly reports, and count contribution data
- Office software RPA skills: automate WPS/LibreOffice operations on openKylin, batch process documents and spreadsheets
- System health inspection skills: automatically check system updates, disk space, service status, log anomalies, and generate reports
- Self-selected directions: must be strongly related to the openKylin system or community scenarios
No restrictions on specific implementation forms, but they must be clearly related to the challenge topics and must be runnable end-to-end on the openKylin system.
Bring your own computer. You must complete the following environment setup and work development on openKylin desktop operating system (2.0 or above):
Works developed only on SaaS cloud versions without local deployment on openKylin will not be accepted.
- Teams of 1-3 people
- Each team submits one work (may include one or multiple skills)
Please submit your work to the openKylin-skills repository via Pull Request.
Submission Path Reference:
- UKUI Desktop Category → skills/ukui/
- Linux General Category → skills/linux-generic/
- Community Contribution Category → skills/community/
- Development Operations Category → skills/devops/
- AI/LLM Category → skills/ai/
- Specific Domain Category → skills/domain/
- Fork Repository：Fork https://gitee.com/openkylin/openkylin-skills to your personal Gitee account
- Create a branch: git checkout -b skill/your-skill-name
- Add skill: Add skill files according to the repository specification (see the recommended work directory below)
- Update index: Update the corresponding category's README.md and the repository root README.md skill list
- Commit code: git commit -m "Add xxx skill"
- Push branch: git push origin skill/your-skill-name
- Create PR: Create a Pull Request on Gitee with the target branch as master
[Hack-Astron x openKylin #1] Skill Name + Most Highlighted Feature
Example:
- [Hack-Astron x openKylin #1] ukui-auto-config + RPA-based one-click UKUI desktop configuration
- [Hack-Astron x openKylin #1] community-report-gen + openKylin community major events scraping
- openKylin version and system architecture used (x86_64 / ARM64 / RISC-V / LoongArch)
- Astron Agent and Skillhub deployment method and version
- Skill functions implemented and RPA operation logic
- Applicable scenarios / Target users
- Whether it depends on models, plugins, knowledge bases, or external services
- Skill publishing and version management description on Skillhub
- Demonstration screenshots, screen recordings, or running result descriptions
Please create an independent directory under the corresponding category, for example:
skills/community/
└── community-report-gen/
├── SKILL.md
# Skill description (required)
├── config.json
# Configuration parameters (optional)
├── scripts/
# RPA scripts or execution code
│ └── main.py
├── references/
# Reference materials (optional)
│ └── record_template.md
└── preview.png
# Optional, it is recommended to include running effect screenshotsWhere:
- SKILL.md: Main skill description file, must include skill description, usage scenarios, execution flow, dependent skills, input/output, and precautions, following the openKylin skill contribution specification
- scripts/: RPA automation scripts, must be executable end-to-end in the openKylin environment
- preview.png: Optional, it is recommended to include skill running effect or RPA flow screenshots
- Competition Period: September 3 – September 24
- Award Evaluation: September 25 – September 30
Score priority for version and environment selection:
- Complete local deployment of Astron Agent open-source version + Skillhub open-source version on openKylin, with skills implemented based on native RPA
- Local deployment of Astron Agent open-source version on openKylin, with Skillhub using cloud or simplified solutions
- Only using Astron Agent SaaS version on openKylin (not recommended)
Key considerations:
- Completeness and reproducibility of the deployment in openKylin environment
- Actual runnability and stability of the RPA skills
- Full-chain closure of Skillhub skill publishing, version management, installation, and invocation
Key focus:
- Whether it truly solves real problems of openKylin users or the community
- Whether the interaction experience is natural and complete, and whether exception handling is adequate
- Whether there is innovative design, reflecting the combined advantages of RPA + Agent
- Whether it is easy to reuse and extend, and whether documentation is clear
Key focus:
- Whether the skill directory structure and naming conventions comply with the openKylin-skills repository requirements
- Whether the SKILL.md documentation is complete and standardized
- Whether the PR format is correct and the description is clear
- Whether the license is compliant (MulanPSL-2.0) and whether it contains sensitive information
- Cash reward: 500 RMB
- Honorary title: Hack-Astron x openKylin Challenge Champion
- Priority inclusion of the work into the official openKylin-skills repository
- Prize content: openKylin × Astron gift package
- Prize examples:
- Electronic products
- Canvas bags
- Virtual memberships
- Token
- openKylin custom polo shirts
- Please ensure the submitted content is related to the challenge topics and that the skill can run end-to-end on the openKylin system
- Do not submit code or workflows containing real keys, tokens, accounts, private addresses, or other sensitive information
- Please ensure the work can be imported, reproduced, and explained. The more complete the deployment documentation and skill description, the better for review and community reuse
- All code submitted to the openKylin-skills repository must use the MulanPSL-2.0 license and must not introduce incompatible third-party dependencies
- Skills must clearly indicate the compatible openKylin version and architecture, with multi-architecture support (x86_64 / ARM64 / RISC-V / LoongArch) preferred