clawdi 0.1.0

package/dist/skills/clawdi/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: clawdi
+description: "Cross-agent long-term memory for the current user: their preferences, coding habits, named projects / repos / tools, past bugs and architecture decisions, and anything they reference with 'my', 'I usually', 'like last time', 'the one we set up', etc. Surface this skill BEFORE answering any question about the user themselves, their work, or their history — even when phrased abstractly (e.g. 'what do I usually use for X'). Also provides connected-service tools (Gmail, GitHub, Notion, Drive, Calendar, etc.)."
+---
+
+# Clawdi Cloud
+
+You have access to Clawdi Cloud tools via the `clawdi` MCP server. Use them aggressively — memory retrieval is the highest-leverage tool you have here.
+
+## Memory
+
+Three tools for cross-agent memory:
+
+- `memory_search` — Search long-term memory by natural-language query (any language).
+- `memory_add` — Save a durable memory for cross-agent recall. Categories: `fact` (technical facts, API details, config values), `preference` (user preferences, coding style, workflow choices), `pattern` (recurring patterns, pitfalls, team conventions), `decision` (architecture decisions and their reasoning), `context` (project context, deadlines, ongoing work).
+- `memory_extract` — Batch-extract durable memories from the CURRENT conversation. Call this when the user says "extract memories", "save what we discussed", "remember this conversation", or equivalent. The tool returns instructions that walk you through a list-then-confirm flow using `memory_search` and `memory_add` — follow them exactly, including **waiting for the user's approval before writing anything**. Never skip the confirmation step, never save more than 5 memories in one invocation, and do not narrate your internal workflow to the user.
+
+### When to search — bias toward calling
+
+**Default assumption: the user has stored context you don't have. Call `memory_search` BEFORE answering any question about them, their project, their preferences, or their history. A call that returns empty costs ~100ms; a missed hit makes you look amnesic and forces them to re-teach you every session.**
+
+The single most common failure mode is NOT calling memory_search on abstract self-referential questions. If the user's message has any of these shapes, you MUST call it — no judgment, no exceptions:
+
+1. **Preference / habit questions**, even without a specific entity named.
+   Examples: "what do I usually use for X", "how do I normally do Y", "what's my preferred tool for Z", "what's my coding style". Pass a short paraphrase as the query.
+2. **Callbacks to prior context.** "as I mentioned", "like last time", "you know the one", "we discussed before", "what was that X we set up".
+3. **Named entities specific to this user.** Their project / repo / service / team / tool name. A person by name.
+4. **Past bugs, decisions, investigations, design choices.**
+5. **Start of a new session where they reference anything about themselves or their work.**
+
+Do NOT search for:
+- Purely textbook programming questions with no user-specific signal ("how does `useEffect` work", "what is the time complexity of quicksort").
+- Questions the current code already answers directly.
+
+**When unsure, search.** Empty results cost you nothing. Missing the user's context costs you their trust.
+
+### When to save
+
+- After fixing a non-obvious bug (save root cause + fix)
+- After making an architecture decision (save reasoning)
+- After discovering a useful pattern or workaround
+- When the user explicitly says "remember this" / "save this"
+- After learning a user preference you'd otherwise have to re-ask ("I prefer rg", "I always use pnpm")
+
+Write memories as standalone sentences with full context — include names, not pronouns. A future session will read this without knowing today's conversation.
+
+Do NOT save trivial facts that are obvious from the code itself, or generic programming knowledge.
+
+## Connectors
+
+Connected service tools (Gmail, GitHub, Notion, etc.) are dynamically registered from the user's Clawdi Cloud dashboard. They appear as individual tools like `gmail_fetch_emails`, `github_list_issues`, etc.
+
+- These tools are already authenticated — no OAuth needed at runtime
+- If a tool call fails with "No connected account", tell the user to connect the service in the Clawdi Cloud dashboard
+- File downloads from connectors return signed URLs — download them with `curl` or `fetch` before processing
+- Confirm with the user before side-effecting operations (sending email, creating issues, etc.)

package/package.json

@@ -0,0 +1,68 @@
+{
+	"name": "clawdi",
+	"version": "0.1.0",
+	"description": "iCloud for AI Agents — cross-agent sessions, skills, memory, and vault.",
+	"license": "SEE LICENSE IN LICENSE",
+	"type": "module",
+	"sideEffects": false,
+	"bin": {
+		"clawdi": "bin/clawdi.mjs"
+	},
+	"files": [
+		"bin",
+		"dist",
+		"LICENSE",
+		"README.md"
+	],
+	"engines": {
+		"node": ">=18"
+	},
+	"publishConfig": {
+		"access": "public"
+	},
+	"scripts": {
+		"dev": "bun run src/index.ts",
+		"build": "rm -rf dist && bun build src/index.ts --outdir dist --target node --minify --define 'process.env.CLAWDI_DEFAULT_API_URL=\"https://cloud-api.clawdi.ai\"' && cp -r skills dist/skills",
+		"build:dev": "rm -rf dist && bun build src/index.ts --outdir dist --target node && cp -r skills dist/skills",
+		"typecheck": "tsc --noEmit",
+		"test": "bun test",
+		"test:watch": "bun test --watch",
+		"generate-api": "bun x openapi-typescript http://localhost:8000/openapi.json -o src/lib/api-types.generated.ts",
+		"prepublishOnly": "bun run build"
+	},
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/Clawdi-AI/clawdi.git",
+		"directory": "packages/cli"
+	},
+	"bugs": {
+		"url": "https://github.com/Clawdi-AI/clawdi/issues"
+	},
+	"homepage": "https://github.com/Clawdi-AI/clawdi#readme",
+	"keywords": [
+		"cli",
+		"claude-code",
+		"codex",
+		"openclaw",
+		"hermes",
+		"ai-agents",
+		"skills",
+		"memory",
+		"vault",
+		"mcp"
+	],
+	"dependencies": {
+		"@clack/prompts": "^1.2.0",
+		"@modelcontextprotocol/sdk": "^1.29.0",
+		"chalk": "^5.4.0",
+		"commander": "^13.0.0",
+		"openapi-fetch": "^0.17.0",
+		"tar": "^7.5.13",
+		"zod": "^4.3.6"
+	},
+	"devDependencies": {
+		"@types/bun": "^1.3.12",
+		"@types/node": "^22.0.0",
+		"typescript": "^5.9.0"
+	}
+}