Before you begin
Download Yammerknit 0.1.1 and extract it. The resulting folder is yammerknit-v0.1.1. It contains both host distributions.
Install the Codex plugin
You need Codex with plugin support and permission to add a local personal marketplace plugin.
- Copy
codex-plugin/yammerknitto%USERPROFILE%\plugins\yammerknit. - Open
%USERPROFILE%\.agents\plugins\marketplace.json. - Preserve its existing object and unrelated entries. Add the following object to the
pluginsarray:
{
"name": "yammerknit",
"source": {
"source": "local",
"path": "./plugins/yammerknit"
},
"policy": {
"installation": "AVAILABLE",
"authentication": "ON_INSTALL"
},
"category": "Productivity"
}- Run
codex plugin add yammerknit@personal. - Run
codex plugin list.
The package is installed and enabled only when Yammerknit reports installed, enabled. Start a new task, then verify discovery with:
Use $yammerknit to explain what source material you need
and what a complete Yammerknit contains.
Do not create an artifact yet.A successful response names the source, codefenced artifact, insight clusters, relational mesh, prompt seeds, sigil lexicon, provenance boundary, and the distinction between a prepared mesh and operating vector RAG. A generic summary is not proof of discovery.
personal, use its name after @.Install the Claude skill
Use claude/yammerknit-v0.1.1.zip from the customer kit.
Claude Code
Extract the ZIP's single yammerknit folder into ~/.claude/skills/yammerknit/. On Windows, use %USERPROFILE%\.claude\skills\yammerknit\. The installed folder must contain SKILL.md directly.
Claude chat
- Enable Code execution and file creation.
- Open Customize → Skills.
- Choose Create skill → Upload a skill.
- Upload
yammerknit-v0.1.1.zipwithout extracting it. - Enable Yammerknit in the skills list.
Start a new conversation or restart the host, then make the same discovery-only request shown for Codex. Verify the complete structure and RAG boundary before supplying private source material.
Use another capable agent
Give the host the complete yammerknit skill folder from either distribution. Keep SKILL.md and every sibling subfolder together. The host must provide its own skill discovery; Python is required only for persistence, validation, revision, inspection, and subtitle helpers.
Make the discovery-only request above. Host-specific activation remains unverified until that host is directly exercised.
Make your first Yammerknit
Turn this transcript into a Yammerknit.
Return the complete codefenced artifact.To save source and revision records, add:
Preserve the source and organize the result in <workspace>.The job is done when the agent returns the complete artifact—or saves the source, manifests, artifact, and validation record in the workspace you named.
Update, remove, and clean up
Update
Preserve workspaces outside the installed package. Replace only the installed plugin or skill folder, start a new task or conversation, confirm the version, and repeat discovery verification. Do not merge old and new runtime folders.
Remove
- Codex: run
codex plugin remove yammerknit@personal, then remove%USERPROFILE%\plugins\yammerknitonly after confirming the final path. - Claude Code: remove only
~/.claude/skills/yammerknit/or%USERPROFILE%\.claude\skills\yammerknit\. - Claude chat: disable or delete Yammerknit under Customize → Skills.
- Other hosts: use the host's removal mechanism, then remove only the installed Yammerknit folder.
Clean up records
Package removal does not delete workspaces, sources, artifacts, revisions, receipts, downloaded ZIPs, or extracted kits. Review those separately under your retention policy; back up required records, then delete only explicitly selected paths. Yammerknit has no vendor cloud account, telemetry store, or hosted data store to purge.