1. Habit
  2. Skills
  3. Appwrite CLI skill
appwrite · 2K installs

Appwrite CLI skill
Runs by itself, config file changes.

Schema, config and types stay synced.

Install the Appwrite CLI skill and make it a habit: follow https://gethabit.dev/skills/appwrite/appwrite-cli.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

2K installs28 starsBSD-3-Clause licenceSource on GitHub ↗

Appwrite CLI

by appwrite · 2K installs

The skill

Appwrite cli is a skill for developers who use the Appwrite CLI well: config vs client, pull and push, type-safe code with appwrite generate, query flags, CI auth, regional endpoints and function variables.

Only when you ask.

The habit

Schema, config and types stay synced.

↻ Runs by itselfconfig file changes

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

config file changes. Runs in GitHub Actions or Claude Code routine.

  • ↻ config file changes
  • push touching appwrite.config.json

02

It checks its work

push and type check. If a check fails, it stops.

  • ✓the change table shows no remote value against an empty local column
  • ✓appwrite generate finishes
  • ✓the project's type checker passes
  • ✓appwrite.config.json holds no API key

03

It remembers

config commit history. The next run reads it first: the last pushed config and generated output path.

appwrite.config.json

One run, step by step.
Then it stops.

Stop ruleStops after one resource push per run; no retries.

  1. 01

    Read the config

    Read appwrite.config.json and confirm the regional endpoint and project.

  2. 02

    Check the change table

    If local is empty where remote has values, run appwrite pull for that resource first.

  3. 03

    Ask before force

    Ask the user, then push the one changed resource with --force instead of push all.

  4. 04

    Keep variables

    Push functions without --with-variables unless the user means to sync secrets.

  5. 05

    Regenerate types

    Run appwrite generate, or appwrite types for other languages, with the repo's usual output path.

  6. 06

    Type check

    Run the project's formatter and type checker on the generated code.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Appwrite CLI skill helps.

Use it when

  • ✓ You deploy Appwrite functions
  • ✓ You generate types from a table schema
  • ✓ You set up Appwrite in CI

Skip it when

  • – You need a full command list
  • – You do not use Appwrite

Questions

Appwrite CLI skill, answered.

Config or client?

Real projects live in appwrite.config.json; one-off calls use appwrite client.

Should I edit generated code?

No. Fix the config and regenerate instead.

How do I install the Appwrite CLI skill?

Copy the prompt at the top into your agent. It installs the skill from appwrite/skills and sets up the habit. Or run npx skills add appwrite/skills --skill appwrite-cli.

Is the Appwrite CLI skill free?

Yes. It is published under BSD-3-Clause. Habit is free too.

Appwrite CLI. Now as a habit.

Install the Appwrite CLI skill and make it a habit: follow https://gethabit.dev/skills/appwrite/appwrite-cli.md

  • Free
  • No account
  • Undo in one line

All appwrite skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by appwrite, published under BSD-3-Clause. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.