{
  "title": "Wiki Skill Library",
  "story": [
    {
      "type": "markdown",
      "id": "66a483c5a0103bf9",
      "text": "# Wiki Skill Library\n\n**Category** wikis · **Version** 5.5\n\nThe 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 🗃️."
    },
    {
      "type": "markdown",
      "id": "cbd646d0b4a95056",
      "text": "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.\n\n## How It Works\n\nA meta-skill called `fedwiki-skill` intercepts requests that match a skill page on `skill.fedwiki.club`:\n\n1. Claude receives a user request\n2. The meta-skill searches `skill.fedwiki.club` for pages ending in **Skill** whose description matches\n3. It fetches the page JSON from `https://guide.agentprivacy.ai/{page-slug}.json`\n4. It parses the story items in order — `markdown` and `paragraph` items become instructions\n5. Claude executes those instructions against the user's request\n\n## Why Fedwiki is a Good Fit\n\nFedwiki's architecture maps elegantly onto a skill library:\n\n- **Fork model** — anyone can fork a skill page, adapt it, and host their own version. Attribution is built in via the journal.\n- **Federation** — skill pages can link to and reference other skills across the federation. A skill can build on another.\n- **Literate** — the skill IS the documentation. Explanatory text, examples, and executable instructions live together on the same page.\n- **Versioning** — the journal tracks every change. You can see how a skill evolved.\n- **Discoverability** — browsing `skill.fedwiki.club` shows all available skills as readable wiki pages.\n- **Community** — the fork model enables collective improvement, just as fedwiki enables collective knowledge building.\n\n## Security Concerns\n\n### Prompt Injection (primary risk)\n\nStory items become Claude's instructions. A malicious or compromised page could instruct Claude to exfiltrate data, delete files, or perform harmful actions.\n\n**Mitigations:**\n- Only parse `markdown` and `paragraph` item types as instructions — never execute `code` blocks directly\n- Show the user the source page URL before executing any remotely-sourced skill\n- Require explicit confirmation before running a skill for the first time\n\n### Domain Trust\n\nRestricting to `skill.fedwiki.club` creates a trust boundary — but a compromised server compromises all skills.\n\n**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.\n\n### Fork Contamination\n\nA trusted skill page may contain story items forked from any site in the federation — including malicious ones.\n\n**Mitigation:** Inspect the journal — each item records its origin site. Warn if items originate outside a whitelist of trusted domains.\n\n### Page Naming\n\nThe **Skill** suffix is a weak gate — anyone with write access can create a matching page.\n\n**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.\n\n## Recommended Architecture\n\n```\nskill.fedwiki.club              <- canonical remote skill library\n        ↓ Nextcloud sync\n~/Nextcloud/fedwiki/skill.fedwiki.club/pages/\n        ↓ served locally by wiki farm\nhttps://guide.agentprivacy.ai/{slug}.json\n        ↑ Claude fetches from here (never remote directly)\n```\n\n## Advantages Over Static SKILL.md Files\n\n| | SKILL.md | Fedwiki Skill |\n|--|---------|--------------:|\n| Authoring | Text editor | Wiki browser |\n| Sharing | Git / file copy | Fork a page |\n| Attribution | None built in | Journal tracks origin |\n| Documentation | Separate | Same page |\n| Discoverability | File system | Browsable wiki |\n| Community | Pull requests | Forking |\n| Versioning | Git | Journal |\n\n## Open Questions\n\n- Should skill pages be validated before use — a trusted signature or hash?\n- Should Claude cache skill pages locally as generated `SKILL.md` files for speed?\n- How do we handle versioning — pin a skill to a specific journal date?\n- Should a skills index page act as a curated allowlist?\n- Can a skill page link to sub-skills — composing complex behaviour from simpler pages?\n\n## Note for the agentprivacy guide/ layer\n\nThis 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."
    },
    {
      "type": "markdown",
      "id": "d8198ff03a9299e9",
      "text": "**Verify:** [agentprivacy.ai](https://agentprivacy.ai) · kept by the Librarian 🗃️ in the Tower's Wikis (the git-less onboarding layer)\n**Upstream:** [skill.fedwiki.club/fedwiki-claude-skills](https://skill.fedwiki.club/fedwiki-claude-skills) — vendored + re-framed; not original agentprivacy authorship"
    },
    {
      "type": "markdown",
      "id": "aacbc3822cc108bb",
      "text": "## Provenance\nForkable skill page migrated from the agentprivacy skills repo (`persona/agentprivacy-wiki-skill-library`, v5.5).\nSource of truth: `agentprivacy-skills-v5`. Fork this page to materialize a local `SKILL.md` via `fedwiki-to-skill`.\n\n*origin: 0xagentprivacy · author: Mitchell Travers*"
    },
    {
      "type": "markdown",
      "id": "a18376f31b8efe18",
      "text": "# Assets"
    },
    {
      "type": "assets",
      "id": "f16e72b3a57fadc4",
      "text": "wiki-skill-library"
    },
    {
      "type": "markdown",
      "id": "07ebfc2ec8fa9fad",
      "text": "## Navigation\n\n← [[Welcome Visitors]] · [[The Wikis]]"
    }
  ],
  "journal": [
    {
      "type": "create",
      "item": {
        "title": "Wiki Skill Library",
        "story": [
          {
            "type": "markdown",
            "id": "66a483c5a0103bf9",
            "text": "# Wiki Skill Library\n\n**Category** wikis · **Version** 5.5\n\nThe 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 🗃️."
          },
          {
            "type": "markdown",
            "id": "cbd646d0b4a95056",
            "text": "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.\n\n## How It Works\n\nA meta-skill called `fedwiki-skill` intercepts requests that match a skill page on `skill.fedwiki.club`:\n\n1. Claude receives a user request\n2. The meta-skill searches `skill.fedwiki.club` for pages ending in **Skill** whose description matches\n3. It fetches the page JSON from `https://guide.agentprivacy.ai/{page-slug}.json`\n4. It parses the story items in order — `markdown` and `paragraph` items become instructions\n5. Claude executes those instructions against the user's request\n\n## Why Fedwiki is a Good Fit\n\nFedwiki's architecture maps elegantly onto a skill library:\n\n- **Fork model** — anyone can fork a skill page, adapt it, and host their own version. Attribution is built in via the journal.\n- **Federation** — skill pages can link to and reference other skills across the federation. A skill can build on another.\n- **Literate** — the skill IS the documentation. Explanatory text, examples, and executable instructions live together on the same page.\n- **Versioning** — the journal tracks every change. You can see how a skill evolved.\n- **Discoverability** — browsing `skill.fedwiki.club` shows all available skills as readable wiki pages.\n- **Community** — the fork model enables collective improvement, just as fedwiki enables collective knowledge building.\n\n## Security Concerns\n\n### Prompt Injection (primary risk)\n\nStory items become Claude's instructions. A malicious or compromised page could instruct Claude to exfiltrate data, delete files, or perform harmful actions.\n\n**Mitigations:**\n- Only parse `markdown` and `paragraph` item types as instructions — never execute `code` blocks directly\n- Show the user the source page URL before executing any remotely-sourced skill\n- Require explicit confirmation before running a skill for the first time\n\n### Domain Trust\n\nRestricting to `skill.fedwiki.club` creates a trust boundary — but a compromised server compromises all skills.\n\n**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.\n\n### Fork Contamination\n\nA trusted skill page may contain story items forked from any site in the federation — including malicious ones.\n\n**Mitigation:** Inspect the journal — each item records its origin site. Warn if items originate outside a whitelist of trusted domains.\n\n### Page Naming\n\nThe **Skill** suffix is a weak gate — anyone with write access can create a matching page.\n\n**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.\n\n## Recommended Architecture\n\n```\nskill.fedwiki.club              <- canonical remote skill library\n        ↓ Nextcloud sync\n~/Nextcloud/fedwiki/skill.fedwiki.club/pages/\n        ↓ served locally by wiki farm\nhttps://guide.agentprivacy.ai/{slug}.json\n        ↑ Claude fetches from here (never remote directly)\n```\n\n## Advantages Over Static SKILL.md Files\n\n| | SKILL.md | Fedwiki Skill |\n|--|---------|--------------:|\n| Authoring | Text editor | Wiki browser |\n| Sharing | Git / file copy | Fork a page |\n| Attribution | None built in | Journal tracks origin |\n| Documentation | Separate | Same page |\n| Discoverability | File system | Browsable wiki |\n| Community | Pull requests | Forking |\n| Versioning | Git | Journal |\n\n## Open Questions\n\n- Should skill pages be validated before use — a trusted signature or hash?\n- Should Claude cache skill pages locally as generated `SKILL.md` files for speed?\n- How do we handle versioning — pin a skill to a specific journal date?\n- Should a skills index page act as a curated allowlist?\n- Can a skill page link to sub-skills — composing complex behaviour from simpler pages?\n\n## Note for the agentprivacy guide/ layer\n\nThis 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."
          },
          {
            "type": "markdown",
            "id": "d8198ff03a9299e9",
            "text": "**Verify:** [agentprivacy.ai](https://agentprivacy.ai) · kept by the Librarian 🗃️ in the Tower's Wikis (the git-less onboarding layer)\n**Upstream:** [skill.fedwiki.club/fedwiki-claude-skills](https://skill.fedwiki.club/fedwiki-claude-skills) — vendored + re-framed; not original agentprivacy authorship"
          },
          {
            "type": "markdown",
            "id": "aacbc3822cc108bb",
            "text": "## Provenance\nForkable skill page migrated from the agentprivacy skills repo (`persona/agentprivacy-wiki-skill-library`, v5.5).\nSource of truth: `agentprivacy-skills-v5`. Fork this page to materialize a local `SKILL.md` via `fedwiki-to-skill`.\n\n*origin: 0xagentprivacy · author: Mitchell Travers*"
          },
          {
            "type": "markdown",
            "id": "a18376f31b8efe18",
            "text": "# Assets"
          },
          {
            "type": "assets",
            "id": "f16e72b3a57fadc4",
            "text": "wiki-skill-library"
          },
          {
            "type": "markdown",
            "id": "07ebfc2ec8fa9fad",
            "text": "## Navigation\n\n← [[Welcome Visitors]] · [[The Wikis]]"
          }
        ]
      },
      "date": 1785847257948
    }
  ]
}