k-skill-setup
After installing the full k-skill bundle, configure and verify the shared cross-platform setup, then optionally wire update checks and GitHub starring with explicit user consent.
Security Assessment
Detected risks:
About k-skill-setup
The k-skill-setup skill is designed to handle the shared post-installation configuration process for the full k-skill bundle across multiple platforms. Its primary purpose is to standardize credential management, runtime environment verification, and optional maintenance workflows after installation is complete. The skill enforces a strict credential resolution order, prioritizing existing environment variables and agent-managed secret vaults before falling back to a local dotenv-based secrets file. It also establishes clear safety rules around persistent system modifications and external state changes, ensuring that operations such as scheduled update checks, GitHub starring, or system scheduler integration are never executed without explicit user consent.
The skill provides structured setup workflows for creating and securing a default secrets file, validating runtime environment variables, and guiding users through missing credential collection. It supports integration with external secret storage systems such as 1Password CLI, Bitwarden CLI, and macOS Keychain, while also supporting a fallback configuration file located at `~/.config/k-skill/secrets.env` with restricted permissions. The setup documentation includes detailed guidance for proxy-based hosted services, optional self-hosted proxy usage, and conditions under which specific API keys are required or intentionally unnecessary. The skill also defines consistent behavior for handling authentication-dependent services, proxy routing, and hosted API usage across multiple Korean public data and infrastructure integrations.
This skill is intended for users and agents deploying the complete k-skill ecosystem who need a repeatable, policy-driven setup process after installation. It is particularly useful for AI agents, automation environments, and developers managing credential-heavy workflows across different operating systems. Teams maintaining self-hosted proxy infrastructure, users configuring Korean public service integrations, and operators requiring controlled secret management workflows can all use this skill to reduce setup inconsistencies and avoid unsafe automated system changes.
FAQ
What does k-skill-setup configure after installation?
The skill configures credential storage, validates runtime environment variables, optionally prepares update-check automation, and optionally handles GitHub starring with explicit user consent.
Where are fallback secrets stored if no vault is used?
Fallback secrets are stored in `~/.config/k-skill/secrets.env` with file permissions set to `0600`.
Can this skill work with external secret vaults?
Yes. The documented credential resolution order supports agent-managed vault systems such as 1Password CLI, Bitwarden CLI, and macOS Keychain before falling back to a local secrets file.
Does the skill automatically modify system schedulers or external services?
No. Operations involving persistent system changes or external state changes, such as cron jobs, launchd, schtasks, GitHub CLI actions, or GitHub starring, require explicit user consent before execution.
Are all API keys required for hosted proxy usage?
No. Several services routed through the default hosted proxy do not require user-side API keys because the proxy server injects and manages those credentials internally.
Install k-skill-setup
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
nomadamas/k-skill