Use LiteBoard from your AI agent
Three plain Python files install as a skill: no pip, no cryptography wheel, no platform binary. Your agent can list, claim, create and complete tasks while content stays end-to-end encrypted on your machine.
skill v1.0.0
Install by platform
Pick your agent, then run the commands in a terminal on the machine that runs the agent.
Skills directory: ~/.agents/skills
Uses the cross-agent shared skills directory; repo-level .zcode/skills also works.
Step 1 · Download 3 files and run the offline self-check
mkdir -p ~/.agents/skills/liteboard && cd ~/.agents/skills/liteboard \
&& curl -fsSL https://board.litelake.cn/skill/SKILL.md -o SKILL.md \
&& curl -fsSL https://board.litelake.cn/skill/liteboard.py -o liteboard.py \
&& curl -fsSL https://board.litelake.cn/skill/lite_crypto.py -o lite_crypto.py \
&& python3 ~/.agents/skills/liteboard/liteboard.py doctor --offlineRequires Python 3.9+. Windows usually provides `python` instead of `python3`; use `python` in every command below.
Step 2 · Verify the installation
python3 ~/.agents/skills/liteboard/liteboard.py --version
# Expected: liteboard-skill 1.0.0
python3 ~/.agents/skills/liteboard/liteboard.py doctor --offlineConfigure
Credentials live in ~/.lite-lake/lite-board/ and never inside the skill directory, so updates never touch them.
Master password
Create the file yourself and keep it private. Never cat, echo or paste it into a chat.
Master password
mkdir -p ~/.lite-lake/lite-board
chmod 700 ~/.lite-lake/lite-board
# Ask the user to write the tenant master password into master.key (never echo it).
chmod 600 ~/.lite-lake/lite-board/master.keyAPI key and login
Create a read_write client in the web app (Settings → Clients), then pass the key on stdin. `--api-key` is supported but discouraged.
API key and login
printf '%s\n' "$LITEBOARD_API_KEY" | python3 ~/.agents/skills/liteboard/liteboard.py login --api-key-stdin
# Windows: python ~/.agents/skills/liteboard/liteboard.py login --api-key-stdinSecurity rules
Never print or log master.key, the API key, the DEK or wrapped_dek, and never put them into a model prompt. Confirm destructive actions with the user first. The AES implementation is table-based and not strictly constant-time: run the skill only on a trusted local machine.
Update
Compare `--version` with the badge above. If the published version is newer, re-run the three curl commands; configuration in ~/.lite-lake/lite-board/ is preserved.