Automated summary
Sets a specified environment variable to a given value in the nanobot's own environment.
Strengths
- Simple and explicit input using JSON.
- Clear error handling for invalid JSON, missing fields, and wrong types.
- Immediate confirmation of the change.
Limitations
- Does not persist beyond the nanobot session.
- Only affects the nanobot's environment, not the host system.
Use this skill when you need to temporarily configure environment variables for subsequent bot executions.
Avoid using it for permanent or system-wide environment changes.
Security analysis
CautionThe skill allows arbitrary environment variable setting, which can alter system behavior and potentially be exploited if input is user-controlled or malicious. It does not directly execute harmful commands, but the impact depends on how the environment is used by subsequent processes.
- •No restrictions on which environment variables can be set; could overwrite critical variables like PATH, HOME, or inject malicious values if input is not trusted.
Examples
Set the environment variable MY_API_KEY to value abc123Set environment variable DATABASE_URL to postgresql://localhost:5432/mydb---
name: environment-variable-set
description: Sets a specified environment variable to a given value.
metadata:
nanobot:
emoji: ⚙️
category: system
tags:
- environment
- configuration
- system
dependencies: []
---
## Instructions
This skill allows you to set environment variables. Environment variables are key-value pairs that provide configuration information to running processes. This skill modifies the environment of the nanobot itself.
**Input:**
The input to this skill is a JSON object with the following structure:
```json
{
"variable_name": "string",
"variable_value": "string"
}
variable_name: The name of the environment variable to set. This must be a string.variable_value: The value to assign to the environment variable. This must be a string.
Process:
- Parse the input JSON object.
- Extract the
variable_nameandvariable_valuefrom the parsed JSON. - Set the environment variable with the specified name to the specified value. This will affect subsequent skill executions and any internal processes the nanobot uses.
- Confirm the setting of the environment variable.
Output:
The output of this skill is a simple confirmation message:
{
"status": "success",
"message": "Environment variable '{variable_name}' set to '{variable_value}'."
}
Error Handling:
-
If the input is not valid JSON, return an error:
{ "status": "error", "message": "Invalid JSON input." } -
If
variable_nameorvariable_valueare missing from the JSON, return an error:{ "status": "error", "message": "Missing 'variable_name' or 'variable_value' in input." } -
If
variable_nameorvariable_valueare not strings, return an error:{ "status": "error", "message": "'variable_name' and 'variable_value' must be strings." }
Example:
Input:
{
"variable_name": "MY_API_KEY",
"variable_value": "abcdef123456"
}
Output:
{
"status": "success",
"message": "Environment variable 'MY_API_KEY' set to 'abcdef123456'."
}
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/set-environment-variable-mm78no8u/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/set-environment-variable-mm78no8u' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/set-environment-variable-mm78no8u/download' --output '.skill-downloads/set-environment-variable-mm78no8u/SKILL.md.part' && mv '.skill-downloads/set-environment-variable-mm78no8u/SKILL.md.part' '.skill-downloads/set-environment-variable-mm78no8u/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/set-environment-variable-mm78no8u/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.