Azzist init
Generate azzist config files for a project: a committed azzist.yaml skeleton and a gitignored azzist.local.yaml for secrets (Cloudflare token, SSH credentials). Use when the user starts an azzist deployment, says "azzist init", "set up azzist config", or before any azzist scaffold/deploy step when no azzist.yaml exists yet.From its SKILL.md
npx -y skills add ghulammuzz/azzist-skills --skill azzist-initAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.8 KB, as published. Nobody here has run it
azzist-init
Create the two-file config split so secrets never land in a public repo.
This skill is idempotent and only concerns config files — it creates or updates
azzist.yaml + azzist.local.yaml, nothing else.
- If azzist-analyze ran just before this, REUSE its proposed yaml fields to populate
azzist.yaml(project name, stack, port, db/cache, repo, branch). Don't re-ask for things analyze already figured out — just confirm with the user once. - If
azzist.yamlalready exists ANDazzist.local.yamlalready exists with the expected keys filled in, STOP and tell the user: "already initialized —azzist.yamlat <path> andazzist.local.yaml(gitignored) are in place. Re-run azzist-analyze to refresh detection, or edit the files directly." Don't overwrite them silently. - If only one of the two exists, create the missing one. If both exist but fields drifted (e.g. analyze detected a new stack), offer to UPDATE specific fields rather than regenerating from scratch.
Security first (do this BEFORE writing any secret file)
- Ensure the project
.gitignoreexcludes the secrets file. If.gitignoredoes not already containazzist.local.yaml, append these lines:
Verify withazzist.local.yaml **/azzist.local.yamlgit check-ignore azzist.local.yaml(should print the path) before continuing. If the project is not a git repo, still create.gitignoreso it is safe the moment it becomes one.
Steps
- Copy the skeleton to the project root as
azzist.yaml:- Source:
${CLAUDE_PLUGIN_ROOT}/templates/config/azzist.yaml - Fill in what you already know from the conversation (project name, stack, domain).
- Source:
- Copy the secrets template to the project root as
azzist.local.yaml:- Source:
${CLAUDE_PLUGIN_ROOT}/templates/config/azzist.local.yaml.example - Do NOT invent secrets. Leave placeholders and ask the user to fill:
Cloudflare
api_token+zone_id, and per-serverhost,ssh_user,authmode.
- Source:
- Recommend SSH auth order:
ssh_configalias >key>password. Only usepasswordif the user insists, and warn it needssshpasslocally. - Confirm to the user:
azzist.yamlis committed (no secrets).azzist.local.yamlis gitignored (holds secrets) — never commit it.
Output
Report which files were created and exactly which fields the user still needs to fill in
azzist.local.yaml before deploy can run.