Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

env-vars

Estrelas22

Forks5

Atualizado8 de julho de 2026 às 18:58

Load, list, verify, and store API keys. Canonical source is macOS Keychain (service=lazar). Use when you need a credential, to check which providers work, or after rotating keys. Never print secret values.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

jasonkneen

jasonkneen/lazar

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

8 arquivos

SKILL.md

readonly

name	env-vars
description	Load, list, verify, and store API keys. Canonical source is macOS Keychain (service=lazar). Use when you need a credential, to check which providers work, or after rotating keys. Never print secret values.

env-vars — Keychain-backed API keys

Canonical store: macOS Keychain, service lazar, account = env var name (e.g. account MINIMAX_API_KEY).

Plaintext files (.env, provider-env.sh) are loaders/fallbacks only. Never echo, log, or commit secret values — names and char-lengths only.

Scripts (this skill)

All under $LAZAR_HOME/skills/env-vars/ (or seed src/seed-skills/_meta/env-vars/).

Script	Purpose
`keychain-list.sh`	Names + present/missing + length
`keychain-get.sh NAME`	Print one secret to stdout (for capture)
`keychain-get.sh NAME --meta`	Length only
`keychain-export.sh`	`source` or `eval "$(… --print)"` to export all
`keychain-store.sh`	Import from `.env` + `provider-env.sh` into Keychain
`keychain-verify.sh`	Live HTTP probe per key (PASS/FAIL, no secrets)

Everyday use

# What's stored?
bash "$LAZAR_HOME/skills/env-vars/keychain-list.sh"

# Load all keys into this shell
source "$LAZAR_HOME/skills/env-vars/keychain-export.sh"
# or: eval "$(bash "$LAZAR_HOME/skills/env-vars/keychain-export.sh" --print)"

# One key for a command (don't log it)
export MINIMAX_API_KEY="$(bash "$LAZAR_HOME/skills/env-vars/keychain-get.sh" MINIMAX_API_KEY)"

# Prove keys still work
bash "$LAZAR_HOME/skills/env-vars/keychain-verify.sh"

First-time / after rotating a key

# 1. Put the new value in the environment (or temporarily in .env)
export MINIMAX_API_KEY='…'   # paste once; do not commit

# 2. Store into Keychain
bash "$LAZAR_HOME/skills/env-vars/keychain-store.sh" --from-env
# or only one: bash …/keychain-store.sh --one MINIMAX_API_KEY

# 3. Verify
bash "$LAZAR_HOME/skills/env-vars/keychain-verify.sh"

Bulk import from existing files (still works if files have values):

bash "$LAZAR_HOME/skills/env-vars/keychain-store.sh"

Provider proxy / lazar launch

workspace/provider-switch/provider-env.sh loads from Keychain. start-proxy.sh sources that file.

source "$LAZAR_HOME/workspace/provider-switch/provider-env.sh"
# or full export:
source "$LAZAR_HOME/skills/env-vars/keychain-export.sh"

export ANTHROPIC_BASE_URL="https://api.minimax.io/anthropic"
export ANTHROPIC_API_KEY="$MINIMAX_API_KEY"

Non-secret config stays in $LAZAR_HOME/.env (e.g. ANTHROPIC_BASE_URL, LAZAR_MODEL).

Other sources (fallback discovery)

If a key is missing from Keychain, check (names only):

$LAZAR_HOME/.env
~/.env (real home)
workspace/provider-switch/provider-env.sh
Shell profiles (export lines)
1Password CLI: op item get … if installed

Security rules

Never print full key values in agent replies, logs, or git commits.
Prefer Keychain over plaintext files for secrets.
After storing, remove secrets from tracked/plaintext files when possible.
Run secrets-scan before sharing any file that might contain keys.
Keychain may prompt for unlock once per session.

Self-test

bash "$LAZAR_HOME/skills/env-vars/keychain-list.sh"
bash "$LAZAR_HOME/skills/env-vars/keychain-verify.sh"

Launch defaults (lazar / glazar / lazartui)

All three load keys via scripts/lazar-env.sh and default to MiniMax-M3 direct. Switch provider: LAZAR_BACKEND=xai lazar -p "..." or lazar-backend openrouter.

Mais deste repositório

mesmo repositório

self-patch

jasonkneen/lazar

How I notice a recurring failure of my own, root-cause it, fix what I can myself (behavioral rules, config, ignore files), and — for anything needing a kernel change I can't apply — draft a verified proposal for the operator to review. The capstone that turns my mistakes into durable fixes. Use when I hit a repeated mistake, get corrected by the operator, see a failed VERIFY, or notice a pattern worth fixing.

2026-07-1222

subagent

jasonkneen/lazar

The ONLY sanctioned way to delegate work to a lazar sub-agent. Uses locked bin/lazar-spawn (not agent-writable skills logic) — lints the prompt, bounds retries, wall-clock-kills wedged children, and gates success by re-checking declared claims against the filesystem. Raw `lazar -p` is vetoed by a pre-tool hook. Use whenever you need to fan out work, isolate context, or run something as a separate agent. Provider-agnostic.

2026-07-1222

log-harvest

jasonkneen/lazar

Turn raw stream.jsonl logs into durable, readable memory — a work journal of what I built and worked on — so the multi-MB archives stop being the only record of my own history. Run after sessions, before pruning logs, or whenever I can't recall recent work. Pairs with _meta/distill (the learnings layer). Use when logs are large, when I've lost track of what I've done, or when preparing to prune/compress the log archives.

2026-07-0822

health-check

jasonkneen/lazar

Verify lazar is installed correctly and all load-bearing behaviors work end-to-end. Runs static checks (kernel locked, env vars, skills present), boundary tests (sandbox enforcement), live behavior tests (log auto-rotation, memory persistence, recursion), and short end-to-end builds in TypeScript and Python. Runs in a temp directory under workspace/, cleans up after itself, prints PASS/FAIL with a summary at the end. Use after install, after kernel rebuild, after --reset-all, or anytime something feels off.

2026-07-0822

create-tui

jasonkneen/lazar

Scaffold a terminal interface for lazar — a small client project under workspace/<name>/ that consumes `lazar -p --output-format stream-json` and renders the events. Default stack: TypeScript + readline. Optional: Go + Bubble Tea, Python + Textual, or anything else the user wants. Use when the user asks for a "TUI", "chat UI", "interface" for lazar that's richer than `lazar-chat.sh`.

2026-05-0122

name	env-vars
description	Load, list, verify, and store API keys. Canonical source is macOS Keychain (service=lazar). Use when you need a credential, to check which providers work, or after rotating keys. Never print secret values.

env-vars — Keychain-backed API keys

Canonical store: macOS Keychain, service lazar, account = env var name (e.g. account MINIMAX_API_KEY).

Plaintext files (.env, provider-env.sh) are loaders/fallbacks only. Never echo, log, or commit secret values — names and char-lengths only.

Scripts (this skill)

All under $LAZAR_HOME/skills/env-vars/ (or seed src/seed-skills/_meta/env-vars/).

Script	Purpose
`keychain-list.sh`	Names + present/missing + length
`keychain-get.sh NAME`	Print one secret to stdout (for capture)
`keychain-get.sh NAME --meta`	Length only
`keychain-export.sh`	`source` or `eval "$(… --print)"` to export all
`keychain-store.sh`	Import from `.env` + `provider-env.sh` into Keychain
`keychain-verify.sh`	Live HTTP probe per key (PASS/FAIL, no secrets)

Everyday use

# What's stored?
bash "$LAZAR_HOME/skills/env-vars/keychain-list.sh"

# Load all keys into this shell
source "$LAZAR_HOME/skills/env-vars/keychain-export.sh"
# or: eval "$(bash "$LAZAR_HOME/skills/env-vars/keychain-export.sh" --print)"

# One key for a command (don't log it)
export MINIMAX_API_KEY="$(bash "$LAZAR_HOME/skills/env-vars/keychain-get.sh" MINIMAX_API_KEY)"

# Prove keys still work
bash "$LAZAR_HOME/skills/env-vars/keychain-verify.sh"

First-time / after rotating a key

# 1. Put the new value in the environment (or temporarily in .env)
export MINIMAX_API_KEY='…'   # paste once; do not commit

# 2. Store into Keychain
bash "$LAZAR_HOME/skills/env-vars/keychain-store.sh" --from-env
# or only one: bash …/keychain-store.sh --one MINIMAX_API_KEY

# 3. Verify
bash "$LAZAR_HOME/skills/env-vars/keychain-verify.sh"

Bulk import from existing files (still works if files have values):

bash "$LAZAR_HOME/skills/env-vars/keychain-store.sh"

Provider proxy / lazar launch

workspace/provider-switch/provider-env.sh loads from Keychain. start-proxy.sh sources that file.

source "$LAZAR_HOME/workspace/provider-switch/provider-env.sh"
# or full export:
source "$LAZAR_HOME/skills/env-vars/keychain-export.sh"

export ANTHROPIC_BASE_URL="https://api.minimax.io/anthropic"
export ANTHROPIC_API_KEY="$MINIMAX_API_KEY"

Non-secret config stays in $LAZAR_HOME/.env (e.g. ANTHROPIC_BASE_URL, LAZAR_MODEL).

Other sources (fallback discovery)

If a key is missing from Keychain, check (names only):

$LAZAR_HOME/.env
~/.env (real home)
workspace/provider-switch/provider-env.sh
Shell profiles (export lines)
1Password CLI: op item get … if installed

Security rules

Never print full key values in agent replies, logs, or git commits.
Prefer Keychain over plaintext files for secrets.
After storing, remove secrets from tracked/plaintext files when possible.
Run secrets-scan before sharing any file that might contain keys.
Keychain may prompt for unlock once per session.

Self-test

bash "$LAZAR_HOME/skills/env-vars/keychain-list.sh"
bash "$LAZAR_HOME/skills/env-vars/keychain-verify.sh"

Launch defaults (lazar / glazar / lazartui)

All three load keys via scripts/lazar-env.sh and default to MiniMax-M3 direct. Switch provider: LAZAR_BACKEND=xai lazar -p "..." or lazar-backend openrouter.