wiki_submit

Submits wiki documentation pages to the Wegent backend API via a Node.js CLI.

772|135|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/wecode-ai/Wegent --skill wiki-submit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki_submit
Source: https://github.com/wecode-ai/Wegent/tree/main/backend/init_data/skills/wiki_submit
Command: npx skills add https://github.com/wecode-ai/Wegent --skill wiki-submit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mermaid, jsdom.

What problem does it solve?

Publishing AI-generated code wiki pages to the Wegent backend requires correctly sequenced HTTP calls, authentication tokens, page-path conventions, Mermaid diagram validation, and coordinated Writer/Reviewer checkpoints. This Skill wraps that entire submission protocol in a single command-line tool so agents can publish documentation without hand-crafting API requests.

Core Features & Use Cases

  • Page lifecycle commands: submit, read, remove, complete, and fail wiki pages identified by stable slash-separated paths, with automatic token resolution from TASK_INFO or environment variables.
  • Mermaid validation: validate-mermaid parses every Mermaid fence with the pinned Mermaid parser plus a subgraph/node ID collision guard before submission or completion.
  • Coordinated review workflow: review-open, review-status, and review commands persist Writer handoffs and Reviewer verdicts for plan, plan amendment, QA, and recheck phases defined in REVIEW_CONTRACT.md.
  • Use Case: During a full-rebuild wiki generation, an agent plans pages, opens a Plan review handoff, obtains a passed verdict, submits each page from Markdown files, validates diagrams, and runs complete with a structure order so the backend publishes the new version.

Quick Start

Ask the agent to submit the wiki page at path architecture/backend from your Markdown file for generation 123 using the wiki submit skill, then run complete with the head commit and reading order.

Frequently Asked Questions about wiki_submit

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

FAQPage Schema
How do I submit a wiki page to the Wegent backend?

Run node wiki_submit.js submit with --generation-id, --path, --title, and either --file pointing to a Markdown file or --content with inline text. The command POSTs the complete page content to the backend endpoint built from TASK_API_DOMAIN.

How do I validate Mermaid diagrams before publishing a wiki page?

Run node wiki_submit.js validate-mermaid --file page.md before submitting and again before complete. It parses every Mermaid fence with the pinned Mermaid parser, reports the failing block's line number, and exits nonzero until all diagrams pass.

Does wiki submit require a manually provided auth token?

No. The token is automatically read from TASK_INFO.auth_token inside executor containers, with WEGENT_SKILL_IDENTITY_TOKEN and WIKI_TOKEN as fallbacks. The endpoint is built from TASK_API_DOMAIN unless overridden by WIKI_ENDPOINT or --endpoint.

Why did complete refuse to publish my wiki generation?

Publication is refused when planned pages are missing, section ancestor paths lack overview pages, or a Mermaid diagram cannot render. Write the named missing pages or fix the named diagrams at the same paths, then run complete again.

What are the page path rules for the Wegent code wiki?

Paths are lowercase, slash-separated, extension-free, and at most four folders deep, matched case-insensitively. Every section with children needs its own substantive overview page, and paths should stay stable across runs to preserve links and search indexing.