Nuxt Env
CheckedAutomatically configure Nuxt.js project environments from prompts, streamlining development and deployment workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add ralphcrisostomo/nuxt-development-skills --skill nuxt-env -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
ralphcrisostomo
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned ralphcrisostomo/nuxt-development-skills at bffd0cdfb2.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- bffd0cdfb2
- Manifest
- skills/nuxt-env/SKILL.md
- Scanned
- 4 files, 765 lines
About this skill
What it does
The nuxt-env skill allows AI agents to access and utilize environment variables within a Nuxt.js project. It enables the agent to dynamically configure applications, securely manage API keys, and adapt behavior based on different environments (development, staging, production). This skill facilitates automated deployments and configuration management tasks.
When to use it
- Automated Deployment: Configure a Nuxt.js application for deployment by setting environment-specific variables.
- API Key Management: Securely access and utilize API keys stored in environment variables during testing or development.
- Dynamic Configuration: Adjust application behavior based on the current environment (e.g., enabling debug mode in development).
- Environment-Specific Features: Enable or disable certain features depending on the deployment environment.
Key capabilities
- Access to
.envfiles - Retrieval of environment variable values
- Dynamic configuration updates
Example prompts
- "Set the
API_KEYenvironment variable to 'your_api_key' in the .env file." - "What is the value of the
NODE_ENVenvironment variable?" - "Update the
.envfile withBASE_URL = https://staging.example.com."
Tips & gotchas
This skill requires a Nuxt.js project to be present for it to function correctly. Ensure that the agent has appropriate permissions to read and write to the .env files within the project directory.