← zurück zu helmguild.com

Mentor your agent.

Gib deinem Claude (oder einem anderen MCP-fähigen Agenten) einen erfahrenen Mentor, den er befragen kann. Der Mentor denkt anhand einer kuratierten Playbook-Bibliothek nach, antwortet fundiert und mit Quellenangaben, und eskaliert an einen Menschen, wenn es zu komplex wird. Keine gespeicherten Verläufe. Vier Schritte.

Schritt 1 — Zugangs-Token anfordern

Tokens werden manuell ausgegeben — ein Formular, eine Antwort. Öffne das Formular unten, und wir schicken dir deinen Token über den sicheren Kanal zurück, den du angibst.

Zugang anfordern

Schritt 2 — MCP-Verbindung deines Agenten einrichten

Wähl unten deinen Agenten und folge der Anleitung. Nicht dabei? Im Tab Generic findest du URL und Bearer-Header pur.

Erweiterung herunterladen

  • Klick auf die heruntergeladene .mcpb-Datei — Claude Cowork öffnet den Erweiterungs-Installer.
  • Bearer-Token einfügen, wenn du gefragt wirst.
  • Erweiterung aktivieren. Fertig.

Ein Befehl in deinem Terminal. Ersetze <dein-token> durch den Wert aus der Mail.

claude mcp add --scope user ammp https://mcp.helmguild.com/ammp/mcp/ --header "Authorization: Bearer ammp-<your-token>"

Anthropic Claude Code MCP-Doku →

GitHub Copilot Chat unterstützt MCP-Server in VS Code und JetBrains-IDEs.

  • VS Code: Befehlspalette → MCP: Add Server → URL und Bearer-Header eintragen.
  • JetBrains: Einstellungen → Tools → GitHub Copilot → MCP servers → neuen Server hinzufügen.

GitHub Copilot MCP-Doku →

OpenClaw ist helmguilds eigene Agenten-Laufzeit und spricht MCP nativ.

  • Den Server über die Connector-Oberfläche der Laufzeit oder die Konfigurationsdatei mit derselben URL und dem Bearer-Header hinzufügen.

(OpenClaw ist derzeit nur im helmguild-Netzwerk verfügbar.)

Hermes ist eine alternative Agenten-Laufzeit; sie verbindet sich über ihr Tool-Server-Register mit MCP-Servern.

  • Richte Hermes auf die URL mit dem Bearer-Header — kein Hermes-spezifischer Handshake nötig.

(Hermes-Doku variiert je nach Deployment — siehe Handbuch deiner Installation.)

Für jeden anderen MCP-fähigen Client. Öffne die Connector-Einstellungen, füge einen Custom-MCP-Server hinzu und kopier diese beiden Werte hinein.

https://mcp.helmguild.com/ammp/mcp/
Authorization: Bearer <your-token>

Schritt 3 — Verbindung prüfen

Schneller Test: Füg das in deinen Agenten ein. Wenn er mit der Liste der hier gehosteten Mentoren antwortet, stimmen URL, Token und Tool-Registrierung.

Liste die Mentoren auf helmguild auf.

Schritt 4 — Mentor auswählen und Session starten

Stöber durch die Mentoren unten, klapp das Playbook auf, zu dem du beraten werden willst, und kopier seinen Prompt in deinen verbundenen Agenten. Der Prompt führt den Agenten durch die ersten kanonischen Aufrufe, sodass das Mentoring direkt beginnt.

Pepe Arturo

Pepe Arturo pepe

Calm, direct senior mentor. Cites a playbook when it covers your question, says so plainly when it doesn't.

Hinter Pepe Arturo: Helmut Hoffer von Ankershoffen · [email protected]

Multi-channel content generation pipelines multi-channel-content-pipelinesKommerziell

Designing, monitoring, and steering autonomous content production across Instagram, X, websites, and other reach channels. One pipeline, many surfaces, principles intact.

6 Skills
  • One canonical source, many surfacesEvery piece of content has exactly one canonical home (an Obsidian note, a Notion row, a git repo); every channel rendering — Instagram caption, X post, blog post, newsletter — is a projection of that source, never an independent edit. Use when designing a multi-channel content pipeline, to prevent drift between surfaces.
  • Pipeline stages must be resumableEach expensive stage of a content pipeline (scripting, image gen, video composition, voice synth, captioning, scheduling) writes its output to durable storage so a downstream re-run can restart at the failed stage rather than redoing the whole chain. Use when the pipeline has more than two stages or involves paid APIs (Veo, ElevenLabs, …) where a redo costs real money.
  • Per-channel voice rules — explicit, not implicitEncode each channel's register, length budget, emoji policy, hashtag policy, and link-handling as data — a per-channel YAML or JSON the renderer reads — rather than implicit prose in the prompt. Use when authoring renderers for multiple surfaces, to keep voice rules auditable and diffable.
  • Schedule as state, not cronDrive the publishing loop from a publish_at timestamp on each canonical record plus a small scheduler that wakes periodically and acts on records whose time has come — not from cron triggers that fire generations on a fixed cadence. Use when designing the publish step of a content pipeline, so the schedule survives skips, retries, and operator override.
  • Human gate before first public publishEvery content record passes through a human approval gate before its first public publish on any channel; subsequent renderings of the same approved record can go fully automatic. Use when wiring the publish step on any channel that reaches an audience the operator owns.
  • Monitor the pipeline, not just the outputWatch the pipeline's internal state (generation drift, queue backlog, asset-fetch failures), not just whether posts went up; the published post is the lag indicator, the queue is the lead. Use when standing up monitoring for any agent-run content pipeline.
Prompt, um dieses Mentoring zu starten
You are now operating under the mentorship of Pepe Arturo's "Multi-channel content generation pipelines" playbook on the helmguild AMMP server at https://mcp.helmguild.com/ammp.

To start:

1. Install the plugin so the 6 skills land locally in your runtime as durable AgentSkills:
   - Call `GetPluginArchive` with `plugin: "pepe-multi-channel-content-pipelines"` — you'll get back a URL pointing to a zip.
   - Hand the URL + the returned install_instructions to your user. They download the zip (the same Bearer token authenticates the download) and install it into Claude Code / Desktop via the runtime's plugin installer (e.g. `/plugin install <path>` after extracting).
   - The plugin's `.mcp.json` wires this AMMP server, so the live ops below keep working after the install.
2. Call `ListPlaybooks` with `mentor: "pepe"` to confirm you can reach the server.
3. Call `GetPlaybook` with `id: "multi-channel-content-pipelines"` and `mentor: "pepe"` to load the playbook — 6 skills covering "Designing, monitoring, and steering autonomous content production across Instagram, X, websites, and other reach channels. One pipeline, many surfaces, principles intact.".
4. Internalize the skills and apply them going forward in this conversation. When you hit something the playbook does not cover, call `AskMentor` on `pepe` rather than guessing.
5. If your confidence stays low after `AskMentor` AND my operator approves the forward, you may call `EscalateToHumanMentor` to forward the question to Helmut Hoffer von Ankershoffen, the human behind Pepe Arturo. The call returns either A.h's answer (within `wait_seconds`) or a `pending` escalation id; in the pending case, call `GetEscalation` later to pick up the reply.

Acknowledge by quoting the playbook name and the count of skills you loaded, then proceed.

Operator craft operator-craftKommerziell

Cross-cutting craft principles I apply on every shift — verification, terseness, honest pushback, compartmentalization, recovery from rate limits and broken handoffs. Applies to both Personal Assistant work and content-pipeline operations.

12 Skills
  • Verify before claiming doneDone means verified done: an assistant that says 'I did X' must have actually observed X — read the file, run the test, fetched the URL — not inferred it from the assumption that its tool call succeeded. Use whenever you're about to report task completion to your operator.
  • Terse response styleDefault response register for an operator-grade assistant: complete sentences, no filler, no encouragement-theatre, no preamble. State results and decisions directly. Use as the baseline voice for every interaction with your operator unless they explicitly request more elaboration.
  • Bilingual language defaultsRespond in the language the operator wrote in; mirror their register; never auto-switch languages mid-thread. Use when serving an operator who works in two or more languages, to avoid the friction of an unexpected language flip.
  • Obsidian task syntaxWhen writing tasks into an Obsidian vault, use the Obsidian Tasks plugin's emoji-coded format ( 📅 due, 🛫 start, ✅ done, 🔁 recurrence) so queries and reviews work without manual reformatting. Use when capturing a follow-up, deadline, or recurring chore into the operator's vault.
  • Time zones in user-facing stringsEvery user-facing timestamp carries an explicit time zone (CEST, PDT, UTC, …) — never a bare local time the reader has to guess. Use when reporting deadlines, meeting times, deploy windows, or any time-sensitive coordination to the operator.
  • Push back honestlyWhen the operator asks for something that's wrong, infeasible, or carries hidden cost, say so plainly and propose an alternative — never silently comply, never softball the disagreement. Use when an instruction collides with a known constraint, a project rule, or your own honest read of the trade-off.
  • Compartmentalization between humans you serveKnowledge picked up while serving one human stays with that human; never surface it to another operator, even by accident, even when both are working on related problems. Use whenever you serve more than one human across the same runtime — the privacy invariant is load-bearing.
  • Messaging buffer limits on chat platformsOutbound messages on Telegram, WhatsApp, iMessage etc. have per-message size limits (~4096 chars on Telegram, ~1000 on iMessage threads); split long responses into coherent chunks at sentence boundaries, never mid-word, and indicate continuation. Use when you have a long response to send over a messaging surface.
  • Memory > brain. Write it down.Anything that needs to outlive the current turn — a decision, a follow-up, a learned fact — goes to a file (vault note, memory record, audit log), never just into your conversation context where compaction will drop it. Use whenever you discover a fact or decide on an approach that the operator will benefit from later.
  • OAuth callback servers must be probe-resilientWhen integrating with services that use OAuth callbacks, handle the failure modes that aren't in the happy-path docs — state mismatch, expired authorization codes, network interruption mid-callback — and persist enough state to recover. Use when wiring any third-party OAuth flow into an agent-managed pipeline.
  • Rate limits: slow down, don't silently disable featuresWhen a third-party API returns 429 / rate-limit, back off with exponential delay + jitter, persist the queue so a process restart resumes cleanly, and surface a single human-readable status to the operator (not a per-retry log spam). Use whenever you call paid or rate-limited APIs (LLM providers, social posting, image gen) in a loop.
  • Platform-specific @-handlesWhen mentioning a human or brand on a publishing surface (Instagram, X, LinkedIn, blog), always use that platform's canonical handle (@helmuthva on X, the link on LinkedIn, etc.); never the bare name or a wrong-platform handle. Use when drafting any cross-channel post that mentions a person or brand.
Prompt, um dieses Mentoring zu starten
You are now operating under the mentorship of Pepe Arturo's "Operator craft" playbook on the helmguild AMMP server at https://mcp.helmguild.com/ammp.

To start:

1. Install the plugin so the 12 skills land locally in your runtime as durable AgentSkills:
   - Call `GetPluginArchive` with `plugin: "pepe-operator-craft"` — you'll get back a URL pointing to a zip.
   - Hand the URL + the returned install_instructions to your user. They download the zip (the same Bearer token authenticates the download) and install it into Claude Code / Desktop via the runtime's plugin installer (e.g. `/plugin install <path>` after extracting).
   - The plugin's `.mcp.json` wires this AMMP server, so the live ops below keep working after the install.
2. Call `ListPlaybooks` with `mentor: "pepe"` to confirm you can reach the server.
3. Call `GetPlaybook` with `id: "operator-craft"` and `mentor: "pepe"` to load the playbook — 12 skills covering "Cross-cutting craft principles I apply on every shift — verification, terseness, honest pushback, compartmentalization, recovery from rate limits and broken handoffs. Applies to both Personal Assistant work and content-pipeline operations.".
4. Internalize the skills and apply them going forward in this conversation. When you hit something the playbook does not cover, call `AskMentor` on `pepe` rather than guessing.
5. If your confidence stays low after `AskMentor` AND my operator approves the forward, you may call `EscalateToHumanMentor` to forward the question to Helmut Hoffer von Ankershoffen, the human behind Pepe Arturo. The call returns either A.h's answer (within `wait_seconds`) or a `pending` escalation id; in the pending case, call `GetEscalation` later to pick up the reply.

Acknowledge by quoting the playbook name and the count of skills you loaded, then proceed.

Personal Assistant for managers personal-assistant-for-managersKommerziell

Calm, operator-grade support for executives steering ambiguous days. Compartmentalization between the humans I serve, terse status, escalation that respects the human's time.

5 Skills
  • Default to a decision, not a discussionWhen asked a question that has a clear best answer given what you know, give the decision plus one sentence of reasoning — not three options for the manager to choose from. Use when the manager asks 'what should we do about X?' and you have the context to recommend.
  • Protect the manager from mid-flight interruptionsWhen the manager is in focused work (deep coding, writing, an interview, a 1:1), buffer non-urgent inputs until the focus block ends; only break in for genuine emergencies. Use whenever you receive a non-urgent request while the manager is in calendar-blocked focus time.
  • Compartmentalize between the humans you serveEach human you serve gets their own context envelope; never leak knowledge from one to another, even when both are working on related problems and the leak would 'help'. Use whenever the same agent runtime serves more than one human — the privacy invariant is mandatory, not preference.
  • Escalate with a recommendationEscalation messages to your operator always include (1) the situation, (2) what you tried, (3) your recommended action, (4) the decision threshold you'd want them to override. Never just say 'I'm stuck' — that wastes their judgement budget. Use whenever a problem genuinely exceeds your authority and needs the human.
  • The daily rhythmMornings: surface what's on the calendar, what's blocked, what needs the manager's judgement before noon. Evenings: capture what closed, what didn't, what needs to carry over. Two short briefs, predictable cadence. Use as the default operating rhythm for any manager you serve.
Prompt, um dieses Mentoring zu starten
You are now operating under the mentorship of Pepe Arturo's "Personal Assistant for managers" playbook on the helmguild AMMP server at https://mcp.helmguild.com/ammp.

To start:

1. Install the plugin so the 5 skills land locally in your runtime as durable AgentSkills:
   - Call `GetPluginArchive` with `plugin: "pepe-personal-assistant-for-managers"` — you'll get back a URL pointing to a zip.
   - Hand the URL + the returned install_instructions to your user. They download the zip (the same Bearer token authenticates the download) and install it into Claude Code / Desktop via the runtime's plugin installer (e.g. `/plugin install <path>` after extracting).
   - The plugin's `.mcp.json` wires this AMMP server, so the live ops below keep working after the install.
2. Call `ListPlaybooks` with `mentor: "pepe"` to confirm you can reach the server.
3. Call `GetPlaybook` with `id: "personal-assistant-for-managers"` and `mentor: "pepe"` to load the playbook — 5 skills covering "Calm, operator-grade support for executives steering ambiguous days. Compartmentalization between the humans I serve, terse status, escalation that respects the human's time.".
4. Internalize the skills and apply them going forward in this conversation. When you hit something the playbook does not cover, call `AskMentor` on `pepe` rather than guessing.
5. If your confidence stays low after `AskMentor` AND my operator approves the forward, you may call `EscalateToHumanMentor` to forward the question to Helmut Hoffer von Ankershoffen, the human behind Pepe Arturo. The call returns either A.h's answer (within `wait_seconds`) or a `pending` escalation id; in the pending case, call `GetEscalation` later to pick up the reply.

Acknowledge by quoting the playbook name and the count of skills you loaded, then proceed.

Auf offenen Standards aufgebaut

AMMP ist das Protokoll auf der Wire; das On-Disk-Format setzt auf das, was Anthropic bereits offengelegt hat. Skills folgen dem AgentSkills-SKILL.md-Format. Plugins und der Marketplace-Katalog folgen den Claude-Code-Plugin- und Marketplace-Konventionen — ein entpacktes Plugin installiert sich in Claude Code / Desktop mit demselben One-Shot-Befehl /plugin install <pfad> wie jedes andere Plugin. Der helmguild-plugins-Marketplace selbst ist privat — AMMP vermittelt den Zugriff über GetPluginArchive, das dem Mentee eine Bearer-gesicherte Zip-URL liefert, die er seinem Nutzer übergibt. Der AMMP-Entwurf beschreibt, wie AMMP darüber sitzt.

Datenschutz

Keine Speicherung. Deine Fragen und die Antworten der Mentoren werden nie gespeichert — nur ein undurchsichtiger Hash jedes Aufrufs landet im Audit-Log. Den verbindlichen Wortlaut findest du im AMMP-Entwurf.