القائمة
Switch off the weekly Caretaker. Use when the user asks to turn off, pause, or get rid of the Caretaker.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/imbue-ai/default-workspace-template --skill disable-caretakerيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Use when you want to create a new app for the user -- a page, dashboard, or tool they can open as a tab. Runs an interactive flow: confirm the look and feel on a cheap throwaway mock first, then build the real app to a usable state, then harden it in the background. Covers scaffolding a new Flask app (canonical path) and the escape hatch for wrapping a pre-existing third-party server.
Run the background harden pass for one creation -- crystallize, update, or heal a skill, an app, a service, or the system interface in an isolated worktree, then report back. Invoke when your task file hands you a creation to harden; it names the operation and creation type to compose.
Diagnose and fix a problem the user is hitting in this workspace, and escalate built-in (non-user) issues to imbue. Invoked as `/assist <description>` by the minds "get help -> have an agent help" flow (also usable directly when the user describes something broken).
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | disable-caretaker |
| description | Switch off the weekly Caretaker. Use when the user asks to turn off, pause, or get rid of the Caretaker. |
| metadata | {"author":"imbue"} |
To switch the Caretaker off, remove its schedule entry -- both the durable copy and the live one:
rm -f /home/user/workspace/data/.state/cron.d/minds-caretaker /etc/cron.d/minds-caretaker
That is the whole switch: cron drops the entry within a minute, nothing runs
anymore, and the agent is never woken again. Its notes and permissions file
(under data/.state/caretaker/) stay put, so re-enabling later (the
enable-caretaker skill) picks up where it left off.
If the user also wants its state gone, additionally remove
data/.state/caretaker/ -- but confirm first, since that deletes the Caretaker's
run history and their recorded permissions.