بنقرة واحدة
liv-add-item
Add a new vault item (Project, Agent, or Chat) to the LivOS tree
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Add a new vault item (Project, Agent, or Chat) to the LivOS tree
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Computer-use capability for Liv AI agents — click, type, screenshot, key, scroll on the LivOS desktop via the Luse MCP server. Use when the task requires direct interaction with a graphical application on the host.
Guide for assistant-cloud persistence and authorization. Use when setting up thread persistence, file uploads, or authentication.
Build generative UI apps with OpenUI and OpenUI Lang — the token-efficient open standard for LLM-generated interfaces. Use when mentioning OpenUI, @openuidev, generative UI, streaming UI from LLMs, component libraries for AI, or replacing json-render/A2UI. Covers scaffolding, defineComponent, system prompts, the Renderer, and debugging OpenUI Lang output.
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive. Use when customizing chat UI components.
Guide for assistant-ui runtime system and state management. Use when working with runtimes, accessing state, or managing thread/message data.
Setup and configure assistant-ui in a project. Use when installing packages, configuring runtimes, setting up chat UI, or troubleshooting setup issues.
| name | liv-add-item |
| description | Add a new vault item (Project, Agent, or Chat) to the LivOS tree |
Trigger: User says "/liv-add-item …", "add a new project", "create an agent", "add a chat".
This skill is a thin shim. Read the expanded workflow at:
@~/.claude/get-livin/workflows/add-item.md
Quick reference:
liv query item.create-project --name "<name>" [--cwd <path>]liv query item.create-agent --name "<name>" [--schedule "<cron>"]liv query item.create-chat --name "<name>"All commands emit JSON to stdout with {item: <BaseItem>} on success.
Mutations require livinityd to be running (Phase 171 vault-items PubSub).
On failure: stderr contains the error message and exit code is non-zero.