quark-mswnlz-publisher

Automate the QuarkPanTool to mswnlz publishing pipeline with Git operations.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/2670044605/agent-skills-hub --skill quark-mswnlz-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quark-mswnlz-publisher
Source: https://github.com/2670044605/agent-skills-hub/tree/main/skills/registry/upstream/wlzh-skills/quark-mswnlz-publisher
Command: npx skills add https://github.com/2670044605/agent-skills-hub --skill quark-mswnlz-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This pipeline automates the entire QuarkPanTool → mswnlz publishing flow, turning raw share URLs into a fully updated content set across GitHub repos and a live site.

Core Features & Use Cases

  • End-to-end automation: creates batch folders, copies promotional assets into each resource, generates encrypted share links, classifies items into repos, updates YYYYMM.md and README indexes, and triggers site rebuild.
  • Notifications and traceability: emits unified Telegram group messages and exposes final site URL for validation.
  • Flexible deployment: reads secrets.env, supports GitHub token usage, and works with SSH-based repo pushes.

Quick Start

Provide the batch_share_results.json produced by the Quark batch runner to start the end-to-end publishing workflow.

Frequently Asked Questions about quark-mswnlz-publisher

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

FAQPage Schema
How do I automate publishing Quark share URLs to a GitHub site?

To automate Quark share URL publishing, provide a batch JSON file to trigger folder creation, generate encrypted links, update markdown indexes, and push updates to GitHub repos with a site rebuild.

What is needed to start the end-to-end Quark publishing workflow?

Starting the Quark publishing workflow requires a batch_share_results.json input file and a configured secrets.env file containing environment-based credentials like GitHub tokens and Telegram keys.

Does the Quark publishing pipeline support Telegram notifications?

Yes, the pipeline supports Telegram notifications by emitting unified group messages upon completion, while also exposing the final site URL for validation.

Can I use SSH-based Git pushes with the mswnlz publishing pipeline?

Yes, the mswnlz publishing pipeline works with SSH-based repo pushes for updating GitHub repositories, alongside supporting standard GitHub token authentication.

How does the pipeline classify resources into different GitHub repos?

The pipeline classifies Quark share items into repos during batch processing, applying classification logic to each resource before updating YYYYMM.md and README index files.

What are the limitations of automating Quark share link generation?

Automating Quark share link generation is limited by its strict dependency on the batch_share_results.json format produced by the Quark batch runner, requiring exact structural input for correct encrypted link creation.