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 To Skill

Wiki To Skill

Category wikis ยท Version 5.5

The fork desk / inclusion engine โ€” converts a federated-wiki page into a Claude Code SKILL.md. Activates when materializing a fedwiki skill, exporting a wiki page to ~/.claude/skills, or pulling a skill from skill.fedwiki.club into a repo. This is the git-less clone: the wiki stays source of truth, the SKILL.md is a fork (a copy that remembers its origin). The Librarian's ๐Ÿ—ƒ๏ธ core forking act in the Tower's Wikis.

The fedwiki-to-skill skill converts a federated wiki page (page-json) into a Claude Code SKILL.md file. Author a skill as an ordinary wiki page, then export it to ~/.claude/skills/{slug}/SKILL.md where Claude Code can load and invoke it. It is the inverse direction of the document-plugin skill โ€” here the page itself becomes the skill.

How It Works

A fedwiki page has a title and a story array of items, each with a type and a text. The converter maps each item type to markdown:

  • markdown โ†’ kept as-is (already markdown)
  • paragraph โ†’ plain text paragraph
  • code โ†’ fenced code block
  • html โ†’ wrapped HTML block
  • reference, roster, assets โ†’ omitted (navigation/structure, not instructions)

The page title derives the skill name (lowercase, hyphenated slug), used for the name: frontmatter field and the top # Heading of the body.

Skill Frontmatter

Every SKILL.md opens with YAML frontmatter. The description is the critical field โ€” Claude Code uses it to decide when to auto-invoke the skill, so it must name the trigger phrases.


name: skill-name
description: One or two sentences describing WHEN to trigger โ€” include the user phrases that should activate it.


Pull the description from the first `paragraph` or `markdown` item if it reads like a purpose statement; otherwise ask the user to supply one.

## Output Location

Personal skills (available in all projects):

~/.claude/skills/{skill-name}/SKILL.md


Project skills (current project only):

.claude/skills/{skill-name}/SKILL.md


Default to `~/.claude/skills/` unless the user specifies otherwise.

## Conversion Steps

1. **Read the source** โ€” a page-json path, or a slug + domain located under `~/Music/Guides/Private/{domain}/pages/{slug}` (local) or `~/Nextcloud/fedwiki/{domain}/pages/{slug}` (public).
2. **Extract** the `title` and `story`.
3. **Build frontmatter** โ€” `name` from the slug, `description` from the first descriptive item (ask if unclear).
4. **Convert story items** following the mapping above, with a blank line between items.
5. **Write** to `~/.claude/skills/{slug}/SKILL.md`, creating the directory if needed.
6. **Confirm** โ€” show the output path and the first lines of the generated file.

## What to Watch Out For

- **`reference` items are navigation** โ€” omit unless the user wants them kept as "see also" notes.
- **`assets` and `roster` items** โ€” always omit; they are structural wiki UI elements.
- **Escaped characters** โ€” fedwiki `text` fields may carry escaped newlines or quotes; unescape them when writing markdown.
- **Wikilinks `<a class="wlink" href="page-name.html">Page Name</a>`** โ€” won't resolve inside a skill; convert to plain text or backticked names.
- **Long pages** โ€” many items make a large skill; consider splitting into focused skills.
- **Missing description** โ€” prompt the user before writing if no clear purpose statement exists.
- **Existing skill** โ€” if the target `SKILL.md` already exists, show a diff and ask before overwriting.

## Note for the agentprivacy guide/ layer

When materializing into `agentprivacy-skills/.../guide/`, the agentprivacy framing adds: full metadata frontmatter (`category: guide`, `layer: onboarding`, `keeper: librarian`), an `upstream:` provenance field, and a body footer crediting the source page. The skills are *vendored + re-framed* โ€” the wiki remains the source of truth; the materialized file is a fork that carries its lineage.

## Related Skills

- `agentprivacy-wiki-page` โ€” create the page-json this skill consumes
- `agentprivacy-wiki-skill-library` โ€” the convention that "โ€ฆSkill" pages are a forkable library
- `agentprivacy-wiki-document-plugin` โ€” document a plugin instead of exporting a skill
- `agentprivacy-wiki-create-plugin` โ€” scaffold a new fedwiki plugin

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

Provenance

Forkable skill page migrated from the agentprivacy skills repo (persona/agentprivacy-wiki-to-skill, 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-to-skillSKILL.md

Navigation

โ† Welcome Visitors ยท The Wikis