imbue-ai
- 215 skills
- 0 followers
- 246 repo stars
- 2 days ago last updated
- ▌ Create Message Handling Skill · imbue-aiCreate a new skill to handle a previously-unknown type of event (eg, from an unknown source). Use in order to generate the appropriate skill for the user, and ensure that such messages will be received (by removing the source name from the "ignored_sources.txt" file if it is there).
- ▌ Cut Release · imbue-aiCut a new Sculptor release candidate from main: run `just cut-release` (which creates the release/sculptor-vX.Y.0 branch at X.Y.0rc1, pushes the tag that triggers the RC build, and opens a PR bumping main to the next .dev0), then land the version-bump PR and babysit the RC build up to its manual approval gate. Handles the colocated jj + git working-copy setup and the CI flake/outage/zombie recovery playbook. Stops AT the approval gate — never approves it for you. Use when asked to "cut a release", "cut an RC", or start a new Sculptor release.
- ▌ Update Specs · imbue-aiBring the product specification set under docs/specs/ (SPEC.md, requirements.md, scenarios.md, scenario_coverage.md) up to date with the code that has merged to origin/main since the specs were last refreshed. Reviews the merged PRs since a recorded baseline, filters out non-product churn, and applies the needed edits to each doc — preserving its format and ID scheme — then verifies every existing claim in the docs is still true of the current code. Use periodically to keep the specs from going stale, or when asked to "update the specs" / "refresh docs/specs".
- ▌ Auto QA Iphone · imbue-ai bundleQA the Sculptor mobile web UI on a real iOS Simulator, driven headlessly from a Mac. A single CLI boots a notched iPhone, launches the local frontend server (parsing its port — no hardcoding), opens the app in MobileSafari, taps/swipes via idb, and screenshots each step. Includes the Add-to-Home-Screen standalone flow — the only way to verify notch / status-bar / home-indicator safe-area rendering (env(safe-area-inset-*) is 0 everywhere except real iOS). Use when visually verifying mobile/responsive changes on an iPhone.
- ▌ Auto QA Changes · imbue-aiLaunch Sculptor in a headless browser and interact with the UI via an HTTP API. Send commands via curl, get screenshots back, and visually inspect the result — like a human QA tester. Use when you need visual verification of UI changes, manual testing of features, or end-to-end testing with real Claude.
- ▌ Promote Release · imbue-aiPromote a QA'd Sculptor release candidate to a full production release: verify the RC build is green and has been QA'd, then from the release branch run `just promote-release` (which strips the rcN suffix, commits X.Y.0, and pushes the sculptor-vX.Y.0 tag that triggers the production build) and babysit that build up to its manual approval gate. Handles the colocated jj + git working copy and the CI flake/outage/zombie recovery playbook. Stops AT the approval gate — never approves it for you. Use when asked to "promote a release", "ship the release", or turn an RC into the real release.
- ▌
- ▌
- ▌ Update Help Docs · imbue-ai bundleUpdate the Sculptor help docs (docs/help/ in this repo) to match a specific Sculptor release. Must be run from a Sculptor checkout on the matching release branch. Audits the markdown against that source, rewrites stale text, and recaptures/processes screenshots via the /auto-qa-changes harness. Does NOT commit or push — hands back a dirty working tree for the user to review. Inputs: - Required: Sculptor version to target, e.g. "0.27". The skill verifies the current branch is release/sculptor-v<version>.0 before proceeding.
- ▌ Openhost Sculptor · imbue-ai bundleDeploy, verify, and reset the self-hosted Sculptor app running as an OpenHost app (built from source via openhost.Dockerfile). Covers fresh deploys, updating or switching the deployed branch while keeping data, health-checking the live instance, and a full CLI-only reset to a fresh-onboarding instance. Wraps the `oh` CLI; the app name and repo are hardcoded in the scripts and the only per-machine value (your instance host) lives in .sculptor/.env. The common flows are one-command scripts in this skill's scripts/ folder.
- ▌ Manually QA Branch · imbue-aiTest a pull request by creating a shallow clone at the PR's commit and launching Sculptor. Use when you need to test changes from a specific PR in isolation.
- ▌ Batch Claude Runner · imbue-ai bundleRun Claude programmatically against collections of files in the codebase. Use for batch analysis: scrubbing sensitive data, auditing style violations, security reviews.
- ▌ Update Review Rules · imbue-aiAdd a new issue type to one of Sculptor's review-rule docs. Use when you've encountered a class of bugs, anti-patterns, or flaky test patterns that should be caught in future reviews.
- ▌ Write Release Notes · imbue-aiSummarize commits merged to origin/main as two outputs: internal release notes (categorized into Features, UI Polish, Testing, CI, Cleanup) and user-facing release notes (What's new, Improvements, Reliability). Two input modes: a Sculptor release version (e.g., "0.27") for single-release notes, or a date range (e.g., "Feb 14-23") for ad-hoc weekly notes. Defaults to the last 7 days.
- ▌ Run Integration Test · imbue-aiRun Sculptor integration tests. MUST be used whenever: - Running tests in sculptor/tests/integration/ - User asks to "run integration tests" or "run the tests" for integration test files - Using pytest on integration test files DO NOT run pytest directly for integration tests - use this skill instead. Tests must run as background processes with a Monitor watchdog.
- ▌ Storybook Screenshot · imbue-aiLaunch the Storybook dev server and use Playwright to take screenshots of component stories. Use when you need visual verification of UI component designs or want to iterate on a component's appearance.
- ▌ Code Review Checklist · imbue-aiReview a set of code changes against Sculptor's review categories and produce a markdown findings table. Use when reviewing code (your own or others').
- ▌ Measure React Renders · imbue-ai bundleCompare React component render counts between origin/main and the current branch during a user-defined UI scenario (e.g. panel resize, navigation). Use when verifying that performance changes actually reduced re-renders.
- ▌
- ▌ Debug Integration Test · imbue-aiDebug failing Sculptor frontend integration tests. Use when integration tests fail and you need to diagnose the root cause. Covers common failure modes, how to read test logs, and investigation strategies.
- ▌ Frontend Design Tokens · imbue-aiGuide for using design tokens in the Sculptor frontend. Use when writing or reviewing CSS/SCSS to pick correct token variables.
- ▌ Write Integration Test · imbue-aiInstructions for writing new Sculptor frontend integration tests. Covers how to use FakeClaude for deterministic agent behavior, test file setup, and the available FakeClaude commands. Use when writing new integration tests or adding tests to existing files.
- ▌ Mock · imbue-aiCreate interactive HTML mocks for a feature through guided iteration with the user. Two modes: exploration (generates 3+ end-to-end variants to help the user surface ideas) and confirmation (single coherent mock to visually verify an existing design). Can be invoked standalone or from `/sculptor-workflow:spec` as input to, or output of, a spec.
- ▌ Plan · imbue-aiProduce a detailed implementation plan from a spec and architecture document. Writes a folder of self-contained task files so the build agent can execute one task at a time without holding the full plan in context. Hands off to /build when finalized. Input: a feature slug (or seed message from /architect with paths).
- ▌ Spec · imbue-aiWrite an implementation spec through guided Q&A before writing code. Scaffolds the spec file up front, clarifies the user's goals, then explores the codebase and refines through interactive Q&A so the user watches the spec evolve in the diff viewer. Offers HTML mocks at the start (or mid-Q&A) for UI-heavy features. Input: a description of the feature or change to spec out.
- ▌ Profile Sculptor Backend · imbue-aiCapture Python-level diagnostics from a running Sculptor backend (`sculptor_backend`): instant thread dumps and viztracer/Perfetto traces with no special privileges, or py-spy CPU sampling / flamegraphs / native stacks against the installed signed app (one-time re-sign + sudo). Use when the backend is wedged, slow, pegging a CPU core, or deadlocked, or when you need a CPU profile or a live stack of `sculptor_backend`. Works both INSIDE Sculptor (where privileged steps are delegated to the user so the agent never kills its own backend) and from an EXTERNAL `claude`.
- ▌ Openhost Frontend Preview · imbue-aiLive, hot-reloading preview of the Sculptor WEB frontend from a phone or any browser, served through the OpenHost nginx /proxy front. ONLY relevant when running INSIDE the openhost-deployed Sculptor (the container fronted by nginx on :5050, reachable at https://sculptor.<zone>/) — NOT for local or Electron dev. Frontend-only: it reuses the single shared backend, so it previews UI/frontend changes, not a per-workspace backend. Invoke when iterating on the web UI and wanting to see it live in a browser through the OpenHost SSO front.
- ▌ Review · imbue-aiFinal review pass for a feature implementation. Verifies the diff satisfies the spec's requirements, that tests were written and pass, and invokes the repo's configured code-review skill. Writes review.md alongside the spec, then offers options for handling findings. Input: a feature slug (or seed message from /build with paths).
- ▌
- ▌ Openhost Environment · imbue-aiHow this OpenHost-hosted Sculptor environment works — storage and what survives restarts, where/how to add repositories and authorize gh, and the /proxy/<port>/ capability for previewing loopback web apps from a browser. ONLY relevant when running inside an OpenHost deployment (detect via the OPENHOST_* env vars, e.g. OPENHOST_APP_NAME). Ships with the deploy image and is refreshed every release.
- ▌ Sculpt CLI · imbue-aiInteract with Sculptor programmatically using the sculpt CLI. Use this skill when using `sculpt`, or when designing or planning a workflow that would benefit from understanding the structural capabilities of `sculpt` (workspaces, agents, isolation, and how code flows between them).
- ▌ Stack · imbue-aiStack a new workspace on top of the current branch — a handoff into a NEW workspace whose new branch is based off, and targets, the current branch.
- ▌ Architect · imbue-aiProduce an architecture document from a spec, through deep codebase analysis and guided Q&A. Reads the existing spec (and mocks, if any), explores the codebase, and writes architecture.md alongside the spec. Hands off to /plan when the architecture is finalized. Input: a feature slug (or seed message from /spec with slug + paths).
- ▌ Setup Repo · imbue-aiCreate or update the repo's Sculptor configs (.sculptor/code.md, .sculptor/testing.md, .sculptor/docs.md). These files teach the sculptor-workflow skills how to build, run, test, and where to write docs in this specific codebase. Run this to set up a new repo, or to update the configs when your setup changes.
- ▌ Handoff · imbue-aiHand off the current work to a fresh agent — either a new agent in the SAME workspace, or a new workspace — seeded with a summary of the current context.
- ▌ Restack · imbue-aiPropagate a branch's changes down its stacked children by merging the updated parent into each stacked branch, in order from base to tip.
- ▌ Build Sculptor Extension · imbue-ai bundleBuild or modify a Sculptor extension — a runtime ESM module loaded into the Sculptor UI. Use when asked to write an extension (or "plugin") for Sculptor, add a panel, overlay, workspace widget, home view, or settings UI to Sculptor, or to iterate on an extension with `sculpt extension`. Works from any repo; this file is a self-contained reference (the Sculptor source code is optional).
- ▌ Fetch Process Show · imbue-aiFetch data from somewhere (an external service, an API, a third-party source, uploaded data) validating auth, process it, and show it to the user -- the "go get all this stuff, do something to it, and put it in front of me" task. Use when the ask is to retrieve real data or process real data the user uploaded, transform/summarize/classify it, and surface the result.
- ▌ Show Files In Chat · imbue-aiShow a file to the user in chat. Display an image inline (chart, plot, screenshot, diagram, rendered figure, photo), or offer any other file (PDF, CSV, log, zip, spreadsheet, ...) as a download link. Use whenever you have a file on disk you want the user to see or download, or want to embed an image from a public URL.
- ▌ Use AI Integration · imbue-ai bundleUse when writing or reasoning about code that calls Claude -- an AI-driven app or service, an AI integration, or a skill's scripted model step. Covers the three scenarios (one-shot completion, one-shot agentic task, full agent) and the cost / credentialing model.
- ▌ Crystallize Creation · imbue-ai bundlePromote the just-finished work into a new, reusable, committed, tested skill. Use when that process would recur with new inputs -- especially something you figured out through research or debugging -- or when the user says 'crystallize this'.
- ▌ Agentic Browser Fleet · imbue-aiDrive a fleet of shared Chromium browsers yourself, one command at a time, from your shell. Use when the user wants you to do something on the web (log in somewhere, fill a form, click through a flow, read a page that needs interaction) rather than just fetch a URL. YOU own the browser and YOU drive it -- in this same chat, with your own reasoning.
- ▌ Data Pipeline Builder · imbue-aiBuild a simple, fast ingestion/processing tool that turns batches of raw records (JSON/CSV/Parquet dumps, periodic exports, API pulls) into a processed, queryable store, with incremental loading and backfill. Use when asked to ingest, load, index, ETL or process exported data, especially when batches arrive periodically and overlap.
- ▌ Manage Scheduled Tasks · imbue-aiQuery and edit the recurring scheduled jobs that run on this host. Use when you (or the user, via you) want to see what is scheduled, add a new recurring job, change when something runs, or stop a job from running. Recurring jobs that must not be missed run through the run_job.sh runner (any cadence from minutes to weeks, with catch-up after downtime and retry of failed runs); exact-time fire-and-forget schedules are ordinary cron lines. Also covers how the built-in weekly Caretaker job is wired (off by default) and where all the scheduling configuration lives.
- ▌ Submit Upstream Changes · imbue-ai bundlePush local improvements to shared infrastructure (skills, scripts, CLAUDE.md scaffolding, Dockerfile, system/supervisord.conf) back to the parent template repo so other agents derived from the template benefit. Opens a separate per-feature PR per logical fix; never pushes directly to upstream `main`. Do not push agent-specific content (PURPOSE.md, memory, runtime state). For pulling updates from upstream, use the `update-self` skill instead.
- ▌ Update System Interface · imbue-ai bundleCanonical flow for changing the system interface (the web workspace UI at system/apps/system_interface) -- its frontend (the dockview shell, the sidebar, the New Tab launcher) or backend (Flask server, the inventory over the app registry, layout ops) -- and the shared frontend library at system/libs/workspace_ui. Use whenever the user wants to edit, fix, restyle, or add to the workspace UI / dockview.
- ▌ Update Installed Template · imbue-aiPull a newer version of a template this mind already adopted from its remote repo and merge it in, reconciling it with this mind's own adaptations. Use when the user wants to update, upgrade, or pull the latest version of an adopted template.
- ▌ Update Published Template · imbue-ai bundleCreate a NEW version of a template you already published (v2, v3, ...) -- re-cut the changes made since the last version on top of the published snapshot and advance the published repo by exactly one clean commit, preserving all of the hand-crafted content in the published repo. Use when the user asks to update, re-publish, revise, or ship a new version of a template they previously published.
- ▌ Dealing With The Unexpected · imbue-aiHandle unexpected situations where things are not working as expected. Use when you encounter errors, confusing state, or behavior that contradicts your docs and prompts.
- ▌ Harden Worker · imbue-ai bundleRun 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.
- ▌ Assist · imbue-aiDiagnose 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).
- ▌ Welcome · imbue-aiGreet the user with a short, friendly welcome message when a new project/agent is first started. Invoked automatically as the first message from the minds desktop client.
- ▌ Latchkey · imbue-aiUse whenever you want to use latchkey commands or interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.
- ▌ Build App · imbue-ai bundleUse 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.
- ▌ Caretaker · imbue-aiThe single idempotent Caretaker skill, invoked via /caretaker whenever the deterministic weekly check (system/services/caretaker/caretaker_check.sh) wakes the agent. On the very first run it does one look-only scan (no fixes), then introduces itself with what it found and asks whether (and how often) to keep checking; on every later run it does the weekly routine -- greets the user, scans the workspace's service logs for problems, checks basic system health (disk, memory and swap, CPU load, OOM shedding), and checks for finished-but-uncommitted work, all with permission; reviews the previous run, proposes (or, with permission, applies) fixes and commits, and summarizes, always in plain user-experience terms.
- ▌ Minds API · imbue-aiUse to act on OTHER Minds workspaces on the user's behalf -- list them, create a fresh one, SSH into one, read or export its backups, start/stop/destroy/recover it, or change its settings and service sharing. Reached through the latchkey gateway's minds-api-proxy; most routes need a per-workspace permission grant. For bringing another workspace's content into this one, use the migrate-workspace skill, which drives these routes as part of a much larger flow.
- ▌ Update App · imbue-aiUse immediately whenever the user asks you to update, change, fix, restyle, extend, restart, or otherwise modify an existing app or background service -- load this BEFORE touching its code. Applies to any change to an app's or service's backend or frontend logic, or how it runs. Covers both apps (a tab the user can open) and background services (host-backup, share-gateway, and other supervisord programs with no tab). This is the front door for app and service edits: it owns the live change loop (apply the change so it takes effect, refresh the user's view, verify) and hands the change to the turn-end hardening flow. For creating a brand-new app use build-app; for the workspace UI itself use update-system-interface.
- ▌ Github Sync · imbue-aiEnable, check, or disable GitHub sync for this workspace. Enabling creates a dedicated PRIVATE GitHub repo via latchkey, points origin at it, and auto-pushes every commit from every checkout. Workspace data under data/ is NOT synced to GitHub (the restic host backup covers it). Use when the user asks to back up / sync the workspace to GitHub, enable auto-push, or asks about GitHub sync status.
- ▌ Launch Task · imbue-ai bundleCreate a sub-agent to perform a larger task. Use when work is large enough to warrant a separate context, involves multi-file changes, or benefits from isolation.
- ▌ Update Self · imbue-ai bundleSafely pull updates from the upstream template repo (default target is the latest stable release the running Minds app supports). Use when you want to incorporate upstream skills, script fixes, or config improvements. For pushing local improvements back upstream, use the `submit-upstream-changes` skill instead.
- ▌
- ▌ Use Template · imbue-aiAdapt an existing template (a published snapshot of apps/features from another mind) into this mind, resolving its requirements interactively. Use when the user gives a template's git URL, or asks to adopt/adapt/reuse a published template.
- ▌ Heal Creation · imbue-aiFix an existing creation that errored or delivered a wrong result. This applies to skills, apps, and services. Invoke at turn-end, after you worked around the failure to satisfy the user's request.
- ▌ Manage Layout · imbue-aiUse when you want to rearrange the workspace dock tabs (open, split, move, focus, close, maximize, reload, rename, delete, stop or start an instance) or inspect the live layout.
- ▌ Manage Projects · imbue-aiUse when the user's request is about projects/views themselves -- what a project shows, adding or removing a tab from a project, the project's rail shortcuts, or what happens to an instance when it is deleted. Not for ordinary tab arrangement (split/move/focus within a view) -- see manage-layout for that.
- ▌ Update Creation · imbue-aiChange an existing skill, app, service, or shared script/reference (under .agents/shared/) -- extend it, refactor it, or just verify it still works. Invoke at turn-end when a skill ran but you had to do extra repeatable work by hand, or when you and the user discussed a change to it and applied it live.
- ▌ Check App Errors · imbue-aiSurvey the health of the supervised apps and services on this host and find errors in their logs. Use after building or editing any app/service to confirm it is actually running cleanly, when something seems broken, or when you want a quick read on what (if anything) is currently failing. The Caretaker agent reuses this as its log-scan step.
- ▌ Do Something New · imbue-aiUse immediately when the user asks you to do something net-new -- a task you haven't done before, no existing skill or app applies, and getting it right will require nontrivial research, exploration, or experimentation. Routes the request to the right interactive flow. When doing this, give a very short confirmation message to the user's request, then load this immediately before responding further. Your confirmation message shouldn't mention loading the skill. Skip when an applicable skill or app already exists or for pure dev/code-writing work.
- ▌ Enable Caretaker · imbue-aiTurn on the weekly Caretaker, a BETA feature that is off by default. Use ONLY when the user explicitly asks about the Caretaker or about enabling it -- never suggest, mention, or enable it proactively.
- ▌ Find Transcripts · imbue-aiFind, read, or search through any chat message, transcript, or conversation content from this host -- whether from an active agent, a past session, a deleted agent, a sub-agent, or a worker. Use this skill any time a user asks about chat histories or you otherwise want to access them. NOTE: this skill only covers Minds agents -- not other services (ChatGPT, claude.ai, etc.).
- ▌ Publish Template · imbue-ai bundlePublish a clean, shareable snapshot of the apps/features this mind built to a new GitHub repo (an "template" another mind can adapt). Use when the user asks to publish, share, or export what they built as a reusable template.
- ▌ Disable Caretaker · imbue-aiSwitch off the weekly Caretaker. Use when the user asks to turn off, pause, or get rid of the Caretaker.
- ▌ Migrate Workspace · imbue-ai bundleBring everything from another (older, broken, or replaced) workspace of the user's into this one -- their apps, skills, documents, data, scheduled automations, and every past chat. Use when the user says anything like 'move my stuff over from my old workspace', 'I made a new mind, bring everything across', 'my old workspace is broken, start me fresh', 'import my other mind', or -- asked from the OLD side -- 'I'd like to move to a new workspace'. Requires the other workspace to be startable, since the transfer runs over a live connection to it.
- ▌ Smoke · imbue-aiTrivial skill used to validate the orchestrator + agent runner plumbing without paying for a real research task
- ▌ Swarm · imbue-aiFan out a task to N independent agents with diverse approaches and collect all results
- ▌ Explore · imbue-ai bundleTeam of explorers that investigate a scientific phenomenon from multiple angles simultaneously
- ▌
- ▌
- ▌ Support Idea · imbue-ai bundleRun experiments and derive mathematical proofs to support a pre-existing theory idea supplied as a latex/pdf/markdown file or argument.
- ▌
- ▌
- ▌ Import Theory · imbue-ai bundleImport a pre-existing theory from a latex/pdf/markdown file and store in the context database.
- ▌ Polish Theory · imbue-ai bundlePolish a theory to improve its clarity and make it easier to read. Does not add or remove any content, just rewords and restructures it.
- ▌
- ▌
- ▌ Rank Proposals · imbue-ai bundleCompare and rank multiple proposals (experiments, literature searches, and solution candidates), separating solution candidates from other proposals.
- ▌ Run Experiment · imbue-ai bundleSet up and run a single experiment. Experiments can be arbitrary Python scripts. All experiment execution must go through this skill.
- ▌ Score Theories · imbue-ai bundleScore the quality of the given theories relative to each other and update all population scores.
- ▌ Score Soundness · imbue-aiScore the mathematical soundness of a given theory based on its existing falsification reports.
- ▌ Execute Proposal · imbue-ai bundleDetermine the type of proposal given, execute/delegate accordingly, and return the appropriate resulting ID (experiment ID, literature search ID, or solution ID).
- ▌ Interpret Result · imbue-ai bundleInterpret the results of newly run experiments, literature searches, or solution candidates, and append the findings as new sections to the interpretation log inside the theory folder.
- ▌ Rank Experiments · imbue-ai bundleRank the given experiments based on their importance for evaluating theories.
- ▌ Rank Predictions · imbue-ai bundleRank different predictions based on how well they predict the results of a given experiment. Returns a ranked list of the theory IDs associated with each prediction with their accuracy ranking (1...n).
- ▌ Review Adherence · imbue-ai bundleReview a given theory for adherence to guidance, constraints, and explanatory coverage
- ▌ Write N Theories · imbue-aiSpawn N independent agents that each invoke the write-theory skill, producing N distinct root theories
- ▌
- ▌ Literature Review · imbue-ai bundleSearch arXiv for relevant papers, download papers, and produce a structured literature review
- ▌
- ▌ Search Literature · imbue-ai bundleRun a targeted literature search on specific findings or questions that emerged during theory development
- ▌