Turn owner feedback about agent behavior into concrete system changes. Use when the owner says something is off, wants the assistant to improve how it operates, asks for a reflection, or wants a durable fix instead of a one-off apology.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this when the owner wants a real operating change, not just a nicer reply.
Convert vague dissatisfaction into technical updates to prompts, memory, skills, config, tooling, or routines.
Ask at most 2-3 focused questions, only if needed:
If the failure is already clear from context, skip the questions and move to diagnosis.
Read broadly before changing anything.
Check the relevant parts of:
SOUL.mdIDENTITY.mdUSER.mdMEMORY.mdCheck:
Check anything relevant to the issue:
Present a short diagnosis before editing behavior-critical files:
Do not offer fake fixes like "I'll be more careful" unless that is backed by a concrete system change.
Once approved, make the changes concretely:
Prefer the smallest durable fix that prevents repeat failures.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
AI Personal Assistant network skill for multi-agent PA coordination. Use when: contacting another PA, coordinating with peer agents, scheduling meetings between owners, broadcasting messages to PA groups, or looking up contacts from the local PA directory. Reads contact data from data/pa-directory.json in the workspace.
The English summary is being prepared. Showing the original description.
AI Personal Assistant network skill. Use when: contacting another PA, coordinating with peer agents, scheduling meetings between owners, broadcasting messages, looking up contacts from the local PA directory, or performing any cross-PA task. Reads contact data from data/pa-directory.json in the workspace. Does NOT contain hardcoded contact data — each PA maintains their own directory file.
The English summary is being prepared. Showing the original description.
Route and execute inter-PA coordination tasks in the OpenClaw multi-agent PA network. Triggers when: contacting another PA, passing a message between owners, broadcasting to a PA group, handling group lead/silence rules, or adding a new PA to the directory. NOT for: contact lookups (use contact-list skill), calendar invites (use meetings skill), or billing issues (use billing-monitor skill).
The English summary is being prepared. Showing the original description.
OpenClaw API gateway proxy for authenticated SaaS calls (100+ services in references/SERVICES.md). Use ONLY when making an HTTP request to a third-party service that requires the gateway's stored credentials. NOT for direct API calls with bearer tokens already in scope, NOT for monday.com (use monday-for-agents), NOT for WhatsApp (use heleni-whatsapp). Triggers: "call the X API", "fetch from <service>", "send to Slack via gateway", "use the gateway for".
The English summary is being prepared. Showing the original description.
Automatically creates new skills from complex problem-solving sessions. Triggers at the end of multi-step tasks that required novel approaches, debugging sessions, or workflow creation. Use when: a task took 3+ tool calls, involved a non-obvious solution, or established a pattern likely to recur. Also triggers on: "create a skill from this", "save this as a skill", "this should be a skill".
The English summary is being prepared. Showing the original description.
Monitor for API billing errors and alert the owner and admin immediately. Use when: an API billing error is detected, a peer PA reports a billing error, or during routine health checks. Handles detection, notification, and fallback model switching. Model-agnostic: works with any LLM provider (Anthropic, OpenAI, Google, etc.).
The English summary is being prepared. Showing the original description.