agentsclimarketplace

Agentprivacy wiki document plugin

Skill mitchuski/agentprivacy-skills/agentprivacy-skills-v5/wikis/agentprivacy-wiki-document-plugin

Publish documentation for a Federated Wiki plugin as wiki pages on plugin.fedwiki.club (the curated plugin-catalog wiki). Activates when documenting a fedwiki plugin or adding it to the catalog. The inverse of fedwiki-to-skill. Kept by the Librarian πŸ—ƒοΈ in the Wikis.From its SKILL.md

Install
npx -y skills add mitchuski/agentprivacy-skills --skill agentprivacy-wiki-document-plugin

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.8 KB, 638 tokens by cl100k_base, as published. Nobody here has run it

Document Wiki Plugin Skill

Note: the upstream page document-wiki-plugin-skill was unreachable (HTTP 404) when this skill was materialized on 2026-06-21. This body is reconstructed from the sitemap synopsis and cross-references (the fedwiki-to-skill page names this skill as its inverse; searching-for-plugins names plugin.fedwiki.club as the curated plugin-documentation catalog). Refresh it with agentprivacy-wiki-to-skill once the upstream page resolves.

The document-wiki-plugin skill publishes documentation for a Federated Wiki plugin as wiki pages on plugin.fedwiki.club β€” the curated catalog wiki where plugin docs are treated as authoritative. It is the inverse direction of fedwiki-to-skill: there a page becomes a skill; here a plugin becomes a documentation page.

What It Produces

For a plugin wiki-plugin-{name}, write a documentation page (and any companion pages) to:

~/Nextcloud/fedwiki/plugin.fedwiki.club/pages/{plugin-doc-slug}

The doc page typically covers:

  • What it does β€” the item type(s) it adds and the behaviour
  • Repositories β€” GitHub repo + npm package (wiki-plugin-{name})
  • How it works β€” the rendering / data model, any DSL in item.text
  • Item types β€” each new story item type and its fields
  • Server component β€” routes registered, if any
  • See also β€” links to related plugin pages

Steps

  1. Read the plugin's README.md and source (client/{name}.js, server/server.js).
  2. Author the page JSON with agentprivacy-wiki-page conventions (markdown items, unique IDs, full create journal).
  3. Write it to plugin.fedwiki.club's pages/ folder.
  4. Sync/push (agentprivacy-wiki-nextcloud-push if the desktop client stalls) and reindex the remote.
  5. Confirm the page resolves and is discoverable via agentprivacy-wiki-searching-plugins channel 6 (catalog wikis).

Related Skills

  • agentprivacy-wiki-create-plugin β€” build the plugin this skill documents
  • agentprivacy-wiki-publish-plugin β€” the full release that includes doc publishing
  • agentprivacy-wiki-page β€” the page JSON format the docs use
  • agentprivacy-wiki-to-skill β€” the inverse direction (page β†’ skill)

Verify: agentprivacy.ai Β· kept by the Librarian πŸ—ƒοΈ in the Tower's Wikis (the git-less onboarding layer) Β· reconstructed body β€” refresh from upstream when reachable Upstream: skill.fedwiki.club/document-wiki-plugin-skill β€” vendored + re-framed; not original agentprivacy authorship

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,614. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.