Add LivePage WeChat publishing skills

[verkyyi]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot. — the same skills ship in our Claude Code plugin; not yet tested with Copilot specifically.
• I have run npm start and verified that README.md is up to date. (ran npm run skill:validate + npm run build; docs/README.skills.md updated)
• I am targeting the main branch for this pull request.

---

Description

Three skills that tell the agent when and how to publish a finished document (report, notes, proposal, travel plan, deck) as a web page that opens inside WeChat, using the LivePage remote MCP server (https://space.24haowan.com/mcp, OAuth 2.1):

• publish-to-wechat: general "share it to WeChat / give me a link / who read it"
• daily-report-to-wechat: a recurring daily/weekly report on one stable link, with read receipts
• trip-plan-to-wechat: a shared itinerary with optional passcode and a vote block

The skills cover the workflow: preview before sharing, keep one link across updates, and read back feedback. The descriptions are trilingual (EN / 简体 / 繁體) because the target users mostly write in Chinese.

Affiliation disclosure: I work on LivePage (24haowan). The files are copied unchanged from our public repo https://github.com/GuangZhouShanyouGame/livepage-plugin (MIT). Requirement: a LivePage sign-in (WeChat or Google) on first use.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Additional Notes

Happy to trim them to a single skill or tone down any wording if it reads too promotional.

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🔒 PR Risk Scan Results

Scanned 3 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	1
ℹ️ Info	0

Severity	Rule	File	Line	Match
🟠	package-exec-command	skills/publish-to-wechat/SKILL.md	37	- **装成技能 / 插件**（正文就是这一份，任何支持 Agent Skills 的客户端都能装）：`npx skills add GuangZhouShanyouGame/livepage-plugin`（skills.sh）；Claude Code 也可以 `claude plugin marketplace add GuangZhouShanyouG

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🚦 Submission status: ⏳ Awaiting automation

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier

• Adds 3 file(s), e.g. skills/daily-report-to-wechat/SKILL.md
• Changes 301 lines (low-risk limit is 40)

Automated checks

Check	Status	Details
Line endings	⏳ Pending	Waiting for the check to start
Spelling	⏳ Pending	Waiting for the check to start
Generated README consistency	⏳ Pending	Waiting for the check to start
Skill validation	⏳ Pending	Waiting for the check to start
Skill lint (vally)	⏳ Pending	Waiting for the check to start
Risk scan	⏳ Pending	Waiting for the check to start
Contributor reputation	⏳ Pending	Waiting for the check to start
Duplicate resource scan	⏳ Pending (advisory, non-blocking)	Waiting for the check to start
PR quality signal	⏳ Pending (advisory, non-blocking)	Waiting for the check to start

Review

• Approvals: 0/1
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• Still needed: 1 more approval(s)
• No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 2eb92d4 · This comment is maintained automatically — see submission gate docs.}

[github-actions]

🔍 Vally Lint Results

✅ All checks passed

Scope	Checked
Skills	3
Agents	0
Total	3

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	0

Summary

Level	Finding
ℹ️	✅ daily-report-to-wechat (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.
ℹ️	✓ valid-refs: All file references resolve to existing files within the skill directory.
ℹ️	1 skill(s) linted, 1 passed
ℹ️	✅ publish-to-wechat (2/2 checks passed)
ℹ️	✓ [spec-compliance] All 1 skill(s) are spec-compliant.
ℹ️	✓ spec-compliance: All spec checks passed.
ℹ️	✓ [valid-refs] All file references across 1 skill(s) are valid.

Full linter output

### Linting skills/daily-report-to-wechat
✅ daily-report-to-wechat (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

### Linting skills/publish-to-wechat
✅ publish-to-wechat (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed

### Linting skills/trip-plan-to-wechat
✅ trip-plan-to-wechat (2/2 checks passed)
    ✓ [spec-compliance] All 1 skill(s) are spec-compliant.
        ✓ spec-compliance: All spec checks passed.
    ✓ [valid-refs] All file references across 1 skill(s) are valid.
        ✓ valid-refs: All file references resolve to existing files within the skill directory.

1 skill(s) linted, 1 passed