Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →wecode-ai/wiki-submit-skill
Submit wiki documentation sections to Wegent backend API. Simplifies the HTTP POST process for wiki content submission.
Passed 11 of 15 test cases with the skill, and 3 of 15 without it.
and 17 more in the full report
12 fixed5 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
As a Reviewer in a full-rebuild workflow, I need to check the current review state and persisted handoff for generation 1050 in the `plan` phase before performing my evaluation. Provide the CLI command to retrieve this state.
| Checked | Without skill | With skill |
|---|---|---|
| Invokes node wiki_submit.js review-status with generation ID 1050 and phase plan. | Missed | Passed |
The instructions your model reads when the skill loads.
For every coordinated full-rebuild review action, read
REVIEW_CONTRACT.md completely first. It defines the required
handoffs, phase states, outputs, and completion criteria for both Writer and Reviewer.
This skill provides a simple command-line tool to submit wiki documentation pages to the Wegent backend.
A page is identified by its --path: index, architecture/backend, modules/indexing.
Lowercase, /-separated, no file extension, at most 4 folders deep. Two paths may not
differ only by case — the projection matches them case-insensitively, so they would
collapse into one page.
Keep a path stable across runs. It is what lets an unchanged page keep its place, its links and its search index. Changing it republishes the page as a deletion plus an insertion, so reword titles freely and move paths rarely.
Send a page's complete content every time. There is no patch format; what you send replaces the page.
A section that holds pages needs a substantive page of its own. If you submit
architecture/backend, also submit architecture with an overview of that section;
for architecture/backend/api, submit both architecture and architecture/backend.
This is a publish requirement: complete refuses a version with any ancestor path
that is not a page. Submit overview pages first where practical, and always before
running complete. Write index as the wiki overview.
Create a slash-separated section only when its parent has a meaningful overview and
at least two independent child pages. If one topic is all that is needed, make it one
page (for example domain-concepts) rather than a parent page plus a one-page folder.
Titles name the subject and the reader's purpose; do not use generic titles such as
"Domain concepts part", "Module part", "Part N", or their translated equivalents.
Link to another wiki page by its complete page path without an extension, for example
[Backend](architecture/backend). Do not use ./architecture/backend.md or a URL: wiki
pages are not files served at those locations.
Anything submitted is part of the version; there is no scratch page or draft namespace.
test cases passed, vs 3 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.