From ziki
This skill should be used to fetch pages from the Ziki wiki when the current task touches a topic that may already be documented there. Use it whenever a topic in the conversation matches (or plausibly matches) an entry in the wiki index that was primed at session start, or when the user asks to "recall from ziki", "check the wiki", "look it up in ziki", or similar. Prefer wiki pages over answering from memory when a match exists.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ziki:ziki-recallThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fetch pages from the Ziki wiki so the current session can ground its answers
Fetch pages from the Ziki wiki so the current session can ground its answers in accumulated knowledge instead of re-deriving things from scratch.
This skill is the read-path counterpart to ziki-add. The SessionStart hook
primes each session with wiki/_index.md; this skill is how the model actually
pulls a page body when it needs one.
You MUST read ~/.claude/ziki.md FIRST, before doing anything else. This
file contains the vault repository coordinates (YAML frontmatter) and the exact
tools or commands to use for reading vault files (markdown body).
Do NOT read from the local filesystem. The vault is a remote git
repository. Even if you see a local checkout of the vault (e.g.
~/Documents/ziki/), do not use it. All reads go through the remote access
method described in ~/.claude/ziki.md.
If ~/.claude/ziki.md does not exist, stop and tell the user to run
/ziki-setup.
Invoke this skill autonomously whenever ANY of the following is true:
/ziki-recallDo NOT invoke this skill for:
The caller provides one or more of:
wiki/jetstream-overview.mdJetStream Overviewnats durable consumers — use this if the index has nothing
that matches exactly; you will search the index for the best match_index: fetch the full wiki/_index.md (useful if the session was
primed with a truncated index)Read ~/.claude/ziki.md: parse frontmatter for vault coordinates, read
body for access instructions.
Resolve the target: if given a path, use it directly. If given a title
or topic, scan the primed index (or re-fetch wiki/_index.md if needed) and
pick the closest match. If there is no plausible match, return a short
"no match in wiki" result so the caller can fall back to other strategies.
Fetch the primary page from the vault using the configured access method.
Follow wikilinks up to a small budget to pull in neighbours:
[[wikilinks]] from the primary pageFetch ground-truth snapshots if needed: if the primary page's
frontmatter lists _refs/... paths in ground_truth: and the caller needs
to cite specific facts, fetch those snapshots too. Prefer _refs/ over
refetching the original URL.
Return results as a compact block the model can quote from:
## Recalled from Ziki wiki
### wiki/<primary>.md
<primary page body, verbatim>
### wiki/<neighbour-1>.md (linked from primary)
<neighbour page body, verbatim>
### _refs/<snapshot>.md (ground truth for primary)
<snapshot excerpt, if needed>
Ground the answer: when using recalled content in the response, cite
the wiki page path (e.g. per wiki/jetstream-overview.md). Respect
provenance markers on the page — if a claim is marked ^[inferred],
^[ambiguous], or ^[stale], carry that uncertainty into the answer.
_refs/ snapshot per recall roundIf the caller needs more, they can invoke the skill again with a more specific target.
~/Documents/ziki/ or any other local pathnpx claudepluginhub mikluko/ziki-plugin --plugin zikiFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.