Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

wiki-agent

Sterne11

Forks0

Aktualisiert24. Mai 2026 um 19:25

Help the user install, rebind, or stop using an agent — the `kind: agent` primitive that the kit passes via `claude --agent <name>` at scheduled-run time. Load this skill whenever the user names an agent ("the household-manager", "who runs my weekly digest", "why is `--agent` missing"), or when `wiki agents` / `wiki schedule list` / `wiki doctor` surface an agent binding the user wants to change. The kit ships eight default agents under three recipes; this skill bridges between what the user wants ("a different voice for my Sunday digest") and the verbs that effect it (`wiki add agent:<name>`, `wiki schedule install <op> --agent <name>`, and the v1 manual `rm -r <vault>/.claude/agents/<name>/` for removal until the dedicated `wiki remove` verb ships).

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

eugenelim

eugenelim/llm-wiki-kit

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

ingest

eugenelim/llm-wiki-kit

Unified entry point for ingesting any source (paste, URL, file, photo, transcript) into the vault. Routes on two axes — source-type (clean the input via the document/website/inline path) and content-type (apply schema and routing via a content-type primitive's ingester). Use whenever a user drops, pastes, or links any source for ingestion.

2026-06-2511

wiki-lint

eugenelim/llm-wiki-kit

Run health checks on the vault. Combines structural checks (broken wikilinks, orphan pages, missing frontmatter fields, stale `modified` dates, tag synonyms, convergence debt in `raw/`, asset coverage) with semantic checks (contradiction detection across pages claiming the same fact). Use on request — "lint the wiki" / "check wiki health" — weekly or per-sprint, or after bulk ingestion of new raw sources.

2026-06-2411

wiki-search

eugenelim/llm-wiki-kit

Search the vault by content and frontmatter (--genre, --subtype, --tag, --status, --top). Returns ranked pages with title, genre, subtype, status, tags, and per-file match count — ready to read. Today's backend is ripgrep (literal substring, zero install); the SKILL was designed against a future SQLite FTS5 auto-upgrade tier (BM25, stemming, phrase/prefix) that has not yet shipped. Use for any *vault content* question; reserve the IDE's built-in Grep for regex, code search, or inspecting a known path.

2026-06-2411

follow-up-tracker

eugenelim/llm-wiki-kit

Scan the vault for follow-up callouts (`> [!important] Follow-up due by YYYY-MM-DD`) and standalone `action-item` pages, then surface what's overdue and what's due in the next 60 days, grouped by owner and domain. Load when the user says "what follow-ups are due?", on a weekly sweep, or via `wiki run follow-up-tracker`. Writes one report page per run; pairs with `medical-summary` (which produces visit-specific summaries) and the content-type ingesters that emit the callouts in the first place.

2026-06-2411

ingest-decision

eugenelim/llm-wiki-kit

Ingest a decision source (meeting decision callout, email thread that landed on a choice, written rationale or short ADR-style doc) into a structured decision page. Load from the `ingest` skill when content-type routing identifies the source as a durable choice with context, alternatives, and consequences — distinct from a meeting (which captures *what happened*) or a stakeholder-update (which captures *what to communicate*). Produces one page under `wiki/library/`, links the owner to `wiki/people/`, and is read by downstream operations (status-synthesis, onboarding-pack).

2026-06-2411

ingest-meeting

eugenelim/llm-wiki-kit

Ingest a meeting source (transcript, notes paste, recording link) into a structured meeting page. Load from the `ingest` skill when content-type routing identifies the source as a meeting (calendar invite text, transcript turns, agenda+notes shape). Produces one page under `wiki/library/`, links attendees to `wiki/people/`, and registers decisions and follow-ups for downstream operations (weekly-digest, follow-up-tracker).

2026-06-2411

name	wiki-agent
description	Help the user install, rebind, or stop using an agent — the `kind: agent` primitive that the kit passes via `claude --agent <name>` at scheduled-run time. Load this skill whenever the user names an agent ("the household-manager", "who runs my weekly digest", "why is `--agent` missing"), or when `wiki agents` / `wiki schedule list` / `wiki doctor` surface an agent binding the user wants to change. The kit ships eight default agents under three recipes; this skill bridges between what the user wants ("a different voice for my Sunday digest") and the verbs that effect it (`wiki add agent:<name>`, `wiki schedule install <op> --agent <name>`, and the v1 manual `rm -r <vault>/.claude/agents/<name>/` for removal until the dedicated `wiki remove` verb ships).
license	MIT

wiki-agent

The kit's kind: agent primitives are vault-side personas: each is a markdown file at <vault>/.claude/agents/<name>/AGENT.md that Claude reads when the kit invokes claude --agent <name> at a scheduled or wiki run --exec time. The user owns which agent runs which operation; this skill is how you help them set that.

When to load this skill

Trigger phrases — the user named an agent or asked about identity:

"Who runs my weekly digest?"
"Can I have a different voice for <operation>?"
"Install the <agent-name> agent."
"Why does wiki agents show this binding?"
"Rebind <operation> to <other-agent>."
"What agents are available?"
"Stop using this agent."
"What does the household-manager actually do?"

Also load when the kit surfaces an agent the user might not have known about:

wiki agents output mentioning an agent the user didn't install deliberately (came in via the recipe).
wiki schedule list showing an AGENT column the user didn't set with --agent.
wiki doctor warning about a missing AGENT.md or a version-drift between an agent upgrade and the last OperationRunByAgentEvent.
A conflict where wiki-conflict SKILL names an agent the user wants to change.

When NOT to load it

The user is editing operations, not agents. Operations are the verbs (weekly-digest, meal-planning); agents are the who. Edit the operation's contract.yaml directly.
The user is asking about a vault-side SKILL (a core/files/skills/<name>/SKILL.md). Agents and SKILLs both shape Claude's behavior, but agents are per-invocation identities passed via claude --agent; SKILLs are read by Claude's own discovery from .claude/.
The user is asking about kit-development subagents in the repo root's .claude/agents/. Those are for working on the kit itself, not for user vaults. Per AGENTS.md §"Two scopes, one repo," never mix.

The mental model

Each agent is one file: <vault>/.claude/agents/<name>/AGENT.md. Frontmatter declares name, description, audience (family | work-os | personal), role, tone, and knows: (vault pages the agent treats as standing context). Body is freeform prose Claude reads at run time.

The kit reads zero bytes of AGENT.md. The kit's only responsibility is:

Install / remove the file (via the same PrimitiveInstallEvent path as any primitive).
Resolve which agent runs an operation (CLI --agent flag → recipe agents.<name>.runs: binding → operation contract preferred_agent: → none).
Pass the resolved name to claude --agent <name> when the operation runs.

The agent's behavior is what the user's Claude session does when it reads the file. That's a user-side concern, not a kit-side one.

How to help

When the user wants to see what's installed:

wiki agents

Prints a tab-separated table with NAME / RECIPES / OPERATIONS. Empty OPERATIONS column (—) means the agent ships installed but isn't bound to an operation — decision-companion is the default example.

When the user wants to install a new agent (one that ships in the catalog but isn't in this recipe's closure):

wiki add agent:<name>

Runs through the same install path as any primitive. Lands the AGENT.md under <vault>/.claude/agents/<name>/AGENT.md.

When the user wants to rebind a scheduled operation to a different agent:

wiki schedule uninstall <operation>
wiki schedule install <operation> --agent <new-agent>

The journaled ScheduleInstalledEvent.agent field is frozen at install time — there is no wiki schedule rebind. Uninstall and reinstall is the only path. Confirm with the user before the uninstall lands; the OS-side artifact gets dropped.

When the user wants to try an agent ad-hoc before binding it to a schedule:

wiki run --exec <operation> --agent <name>

The CLI --agent flag wins the resolution chain — even when the recipe binds the operation to a different agent. Use this to A/B the voice before committing.

When the user wants to edit an agent's voice or knowledge:

Edit <vault>/.claude/agents/<name>/AGENT.md directly. The kit ships the file but doesn't track its content — what the agent says is yours. Do not edit templates/agents/<name>/files/.claude/agents/<name>/AGENT.md in the kit source — that's the catalog source, not the vault copy. (Unless the user is in fact modifying the catalog, in which case they're a kit contributor, not a vault user.)

When the user wants to stop using an agent:

Delete the agent's directory from the vault:

rm -r <vault>/.claude/agents/<name>/

The kit's spec calls for a dedicated wiki remove agent:<name> verb (see docs/specs/wiki-agents/spec.md §Edge cases) that journals a PrimitiveRemoveEvent, but the verb is not in the shipped CLI today — the manual rm -r is the user-side recovery path. If a schedule still references the now-deleted agent, the next wiki run --exec for that schedule will refuse to invoke claude (the dispatch validation fails when the agent file isn't present). Warn the user before they delete: they likely want to either keep the agent or rebind the schedule first via the wiki schedule install --agent flow above.

The eight defaults

At v1 the kit ships eight agents across three recipes:

family — household-manager, trip-planner, care-coordinator.
work-os — stakeholder-steward, renewals-watch, customer-listener.
personal — personal-coordinator, decision-companion (installed but unbound).

A user who initialized with one recipe but wants an agent from another can always wiki add agent:<name> to pull it in — the catalog is repo-wide, not recipe-scoped.

Failure modes

wiki schedule install <op> --agent <name> refuses with "agent '' is not installed." The agent isn't in the vault. Suggest wiki add agent:<name> first, or check wiki agents for what's installed.
wiki agents shows an agent with OPERATIONS=—. Either the agent is decision-companion (intentionally unbound) or the recipe binds the agent without any operations in its runs: list. The latter is a recipe-author bug; flag it.
wiki doctor warns "agent '' was upgraded … since the last scheduled run". The agent's AGENT.md may have changed voice. Open the file with the user, read the diff in the catalog source (templates/agents/<name>/files/.claude/agents/<name>/AGENT.md), and decide whether to keep the new voice or roll back via wiki upgrade --to <old-version> (out of scope at v1; today the user edits the vault-side AGENT.md directly).
The kit invokes claude --agent <name> but the user's claude CLI doesn't recognize the flag. Older claude versions lack --agent. The authoritative surface for "is your claude CLI new enough" is wiki doctor's schedule section — per ADR-0009 the kit deliberately doesn't hard-code a version string here. Surface wiki doctor if a scheduled run fails with a claude CLI error mentioning the flag.