request-api-key

Request a missing Upstage API key via Channel.io and write it to .env.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/channel-io/sop-agent --skill request-api-key
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-api-key
Source: https://github.com/channel-io/sop-agent/tree/main/.agents/skills/request-api-key
Command: npx skills add https://github.com/channel-io/sop-agent --skill request-api-key

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When UPSTAGE_API_KEY is missing from .env, this skill automatically requests the key via Channel.io and writes it to the project's .env file.

Core Features & Use Cases

  • Automated key retrieval: detects missing keys and initiates a Channel.io request to obtain Upstage API keys.
  • Language-aware interaction: detects user language (Korean or Japanese) to respond consistently through the process.
  • Key validation & write-back: extracts the key from thread messages, validates the format (starts with up_ and minimum length), and updates .env safely.
  • End-to-end workflow support: handles request, wait-for-reply, retrieval, and verification steps with guardrails and error messages.

Quick Start

Trigger the /request-api-key workflow in Claude Code to begin the Upstage API key retrieval process.

Frequently Asked Questions about request-api-key

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Upstage API key retrieval when it's missing from .env?

When UPSTAGE_API_KEY is missing from .env, this skill automates the retrieval process by requesting the key via Channel.io, waiting for the reply, validating the format, and writing it directly into the .env file.

What's the best way to write an API key to .env without exposing it in the terminal?

The best way to write an API key to .env safely is by using this skill, which extracts the key from Channel.io thread messages, validates it, updates the file, and explicitly prevents displaying the full key in any responses.

Does the API key automation workflow support Korean and Japanese users?

Yes, the API key automation workflow supports Korean and Japanese users by detecting the user's language and consistently guiding the interaction in that language from the initial request through to the final key insertion.

How does the skill validate the .env update after inserting the API key?

The skill validates the .env update by running a Python check that imports the configuration and confirms the key is actually set, ensuring the Upstage API key was written correctly before completing the workflow.

What format does the API key need to be in for the .env write-back to succeed?

The API key format must start with the prefix 'up_' and meet a minimum length requirement for the .env write-back to succeed, ensuring only properly formatted Upstage keys are accepted.