Configure shared credentials and verify runtime setup for the k-skill bundle.
npx skills add https://github.com/NomaDamas/k-skill --skill k-skill-setup
Please help me install this Agent Skill. Skill: k-skill-setup Source: https://github.com/NomaDamas/k-skill/tree/main/k-skill-setup Command: npx skills add https://github.com/NomaDamas/k-skill --skill k-skill-setup
This Skill helps you finish the common, cross-platform setup for the k-skill bundle by creating/locating credentials, validating required environment variables, and optionally enabling update checks and GitHub starring with explicit consent.
~/.config/k-skill/secrets.env) and clearly tells you what’s missing instead of guessing unsafe alternatives.scripts/check-setup.sh) to confirm the environment is ready after installation.Ask your agent to run the setup flow to create the fallback secrets file, verify the runtime environment, and then offer update checks and GitHub starring only after you confirm.
High-intent search queries and answers about installing and using this skill.
To configure environment variables and secret files, this setup resolves credentials using a priority order: environment variables, agent vault, or a secure fallback file at `~/.config/k-skill/secrets.env` with `0600` permissions. It clearly reports missing variables instead of guessing unsafe alternatives.
Runtime verification works by executing `bash scripts/check-setup.sh` to confirm the environment is ready and that dependent skills can authenticate reliably. This validates required environment variables and checks that all shared credentials are correctly configured.
Credential setup fails or reports missing variables because the resolution order prioritizes environment variables, then the agent vault, before creating a fallback secrets file. It avoids guessing unsafe alternatives and requires valid authentication to proceed reliably.
Yes, you can use a fallback secrets file instead of an agent vault. The credential resolution order checks environment variables first, then the agent vault, and finally creates a secure fallback at `~/.config/k-skill/secrets.env` with `0600` permissions when needed.
Yes, explicit consent is required to enable GitHub starring during credential setup. The configuration avoids persistence or running `gh repo star` without direct user approval, ensuring external actions are only applied after agreement.
Lobbi-DocsAutomate HashiCorp Vault secret management and dynamic credential rotation.
tkmh04Provision Vercel Sandbox microVMs to run headless Chrome browser automation.
VincentChong123Configure container agents to use environment-based credentials instead of the OneCLI gateway vault.
tizeeCreate and run standalone Python scripts with inline dependency metadata using uv.