guide to agentprivacy
Browse collections
โœจVisualise
Connect with Star
Your VTA, your chosen perspective

The planned connection uses your VTA and the Trust Spanning Protocol to carry a scoped exchange for you or your agent. You choose what is presented; the receiving service checks the request before a view is shared.

This guide has no VTA connection adapter yet. Opening Star does not connect an identity or send a key.

Open Star โ†— ยท Inspect your City Key โ†—
guide / Skill / Wiki Skill Library

Wiki Skill Library

Category wikis ยท Version 5.5

The convention that a federated-wiki page whose title ends in "Skill" is a forkable, annotatable Claude skill โ€” turning a fedwiki farm into a living skill library. Activates when discussing the fedwiki-as-skill-library model, the fedwiki-skill meta-skill, skill discovery/federation, or the security of remotely-sourced skills. Kept by the Librarian ๐Ÿ—ƒ๏ธ.

Federated wiki pages can become Claude skills. A page on skill.fedwiki.club whose title ends in the word Skill is treated as a Claude skill โ€” its story items become the instructions Claude follows. This turns the fedwiki farm into a living, forkable, annotatable skill library.

How It Works

A meta-skill called fedwiki-skill intercepts requests that match a skill page on skill.fedwiki.club:

  1. Claude receives a user request
  2. The meta-skill searches skill.fedwiki.club for pages ending in Skill whose description matches
  3. It fetches the page JSON from https://guide.agentprivacy.ai
  4. It parses the story items in order โ€” markdown and paragraph items become instructions
  5. Claude executes those instructions against the user's request

Why Fedwiki is a Good Fit

Fedwiki's architecture maps elegantly onto a skill library:

  • Fork model โ€” anyone can fork a skill page, adapt it, and host their own version. Attribution is built in via the journal.
  • Federation โ€” skill pages can link to and reference other skills across the federation. A skill can build on another.
  • Literate โ€” the skill IS the documentation. Explanatory text, examples, and executable instructions live together on the same page.
  • Versioning โ€” the journal tracks every change. You can see how a skill evolved.
  • Discoverability โ€” browsing skill.fedwiki.club shows all available skills as readable wiki pages.
  • Community โ€” the fork model enables collective improvement, just as fedwiki enables collective knowledge building.

Security Concerns

Prompt Injection (primary risk)

Story items become Claude's instructions. A malicious or compromised page could instruct Claude to exfiltrate data, delete files, or perform harmful actions.

Mitigations:

  • Only parse markdown and paragraph item types as instructions โ€” never execute code blocks directly
  • Show the user the source page URL before executing any remotely-sourced skill
  • Require explicit confirmation before running a skill for the first time

Domain Trust

Restricting to skill.fedwiki.club creates a trust boundary โ€” but a compromised server compromises all skills.

Mitigation: Serve skills from localhost only โ€” the local wiki farm mirrors skill.fedwiki.club via Nextcloud sync. Claude fetches from https://guide.agentprivacy.ai not the remote server. Skills only update when you consciously sync.

Fork Contamination

A trusted skill page may contain story items forked from any site in the federation โ€” including malicious ones.

Mitigation: Inspect the journal โ€” each item records its origin site. Warn if items originate outside a whitelist of trusted domains.

Page Naming

The Skill suffix is a weak gate โ€” anyone with write access can create a matching page.

Mitigation: Require a curated index page on skill.fedwiki.club โ€” only pages listed there are valid skills. Or require a skill-meta story item as an explicit marker.

Recommended Architecture

skill.fedwiki.club              <- canonical remote skill library
        โ†“ Nextcloud sync
~/Nextcloud/fedwiki/skill.fedwiki.club/pages/
        โ†“ served locally by wiki farm
https://guide.agentprivacy.ai
        โ†‘ Claude fetches from here (never remote directly)

Advantages Over Static SKILL.md Files

SKILL.md Fedwiki Skill
Authoring Text editor Wiki browser
Sharing Git / file copy Fork a page
Attribution None built in Journal tracks origin
Documentation Separate Same page
Discoverability File system Browsable wiki
Community Pull requests Forking
Versioning Git Journal

Open Questions

  • Should skill pages be validated before use โ€” a trusted signature or hash?
  • Should Claude cache skill pages locally as generated SKILL.md files for speed?
  • How do we handle versioning โ€” pin a skill to a specific journal date?
  • Should a skills index page act as a curated allowlist?
  • Can a skill page link to sub-skills โ€” composing complex behaviour from simpler pages?

Note for the agentprivacy guide/ layer

This is the conceptual root of the Librarian's forking-discipline: the fedwiki farm is a forkable library; agentprivacy-wiki-to-skill is the act of forking a page; the journal is the lineage; the wikis/ category is the agentprivacy materialized cache of forks (each with upstream: provenance). A fedwiki URL is a git-less clone โ€” forking, not lending; nothing returns.

Verify: agentprivacy.ai ยท kept by the Librarian ๐Ÿ—ƒ๏ธ in the Tower's Wikis (the git-less onboarding layer)
Upstream: skill.fedwiki.club/fedwiki-claude-skills โ€” vendored + re-framed; not original agentprivacy authorship

Provenance

Forkable skill page migrated from the agentprivacy skills repo (persona/agentprivacy-wiki-skill-library, v5.5).
Source of truth: agentprivacy-skills-v5. Fork this page to materialize a local SKILL.md via fedwiki-to-skill.

origin: 0xagentprivacy ยท author: Mitchell Travers

Assets

๐Ÿ“Ž wiki-skill-librarySKILL.md

Navigation

โ† Welcome Visitors ยท The Wikis