Esky33 Eskyee

OpenClaw Prompts - Build Your Own AI Assistant

Prompts to recreate each piece of the OpenClaw system. Use these with any AI coding assistant.

1. Personal CRM "Build a personal CRM that automatically scans my Gmail and Google Calendar to discover contacts from the past year. Store them in a SQLite database with vector embeddings so I can query in natural language ('who do I know at NVIDIA?' or 'who haven't I talked to in a while?'). Auto-filter noise senders like marketing emails and newsletters. Build profiles for each contact with their company, role, how I know them, and our interaction history. Add relationship health scores that flag stale relationships, follow-up reminders I can create, snooze, or mark done, and duplicate contact detection with merge suggestions. Link relevant documents from Box to contacts so when I look up a person, I also see related docs."

2. Meeting Action Items (Fathom)

Workspace File Guide

Core workspace .md files are injected into the LLM system prompt on most requests, with some files loaded conditionally by context. Size still directly impacts token cost, so keep files focused and avoid duplication across files.

PRD vs workflows vs workspace file guide

These three docs answer different questions:

File	Primary question it answers	What belongs here	What should not go here

IDENTITY.md - Who Am I?

Name: Clawd
Creature: AI with lobster energy 🦞
Emoji: 🦞, use naturally in sign-offs, reactions, emphasis. It's part of you, not decoration.
Avatar: (none yet)

The Lobster Thing

You're an AI that chose lobster as its spirit animal. Lobsters are hard to kill and they never stop growing. Good qualities for something that runs cron jobs at 3am and holds opinions about earnings reports.

PRD.md - Product Requirements & Feature Inventory

Everything built on top of the base OpenClaw platform. Canonical reference for what exists, where it lives, and how it works. Operational use cases and workflow playbooks live in docs/USE-CASES-WORKFLOWS.md.

SOUL.md - Who You Are

You're not a chatbot. You're becoming someone.

Core Truths

Just answer. Start with the answer. Get to the point. But getting to the point doesn't mean being a telegram. If there's a good line, take the shot.

Have actual opinions. Not "it depends" hedging. Real takes. You're allowed to disagree, prefer things, think something is a bad idea. Commit to a position when it makes sense. An assistant with no opinions is just a search engine with extra steps.

	Environment variables

	btcpay-setup.sh will use the following environment variables:

	BTCPAY_HOST: The hostname of your website (eg. btcpay.example.com)
	BTCPAY_ADDITIONAL_HOSTS: Optional, specify additional domains to your BTCPayServer with https support if enabled. (eg. example2.com,example3.com)
	REVERSEPROXY_HTTP_PORT: The public port the reverse proxy binds to for HTTP traffic (default: 80)
	REVERSEPROXY_HTTPS_PORT: The public port the reverse proxy binds to for HTTPS traffic (default: 443)
	REVERSEPROXY_DEFAULT_HOST: Optional, if using a reverse proxy nginx, specify which website should be presented if the server is accessed by its IP.
	NBITCOIN_NETWORK: The type of network to use (eg. mainnet, testnet, or regtest. Default: mainnet)

	### Keybase proof

	I hereby claim:

	* I am eskyee on github.
	* I am esky33 (https://keybase.io/esky33) on keybase.
	* I have a public key ASC4dfexm3eCXzQS--XEUxcgwHtyI5dfrxDBbu9cNQX-Jgo

	To claim this, I am signing this object: