skills.rest
dmae97
dmae97COMMUNITY
Explore all skills by this author →
GitHub

deepseekset

Store a DeepSeek API key in the user-local OMK secret environment file.

130|14|Updated Apr 30, 2026
Search Tags:#cli#configuration#secrets#api key#deepseek#provider setup#omk
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill deepseekset
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deepseekset
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/deepseekset
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill deepseekset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents accidental leakage of your DeepSeek API key by storing it only in the user-local OMK secret environment file instead of the project repository.

Core Features & Use Cases

  • Secret-safe key storage: Saves the DeepSeek API key into the user-local OMK secret env file so it won’t be committed.
  • User-local configuration for coding workflows: Enables OMK commands that require DeepSeek credentials without exposing the key in logs.
  • Post-setup verification: Encourages confirming the provider is available by running the provider doctor check after setting the key.

Quick Start

Run the command omk deepseek api to store your DeepSeek API key without writing it to the repository.

Frequently Asked Questions about deepseekset

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

FAQPage Schema
How do I safely store my DeepSeek API key for local coding workflows?▼

To safely store your DeepSeek API key, run the command `omk deepseek api` to save it into the user-local OMK secret environment file, preventing accidental commits to your project repository.

Why does my DeepSeek API key need to go into a local OMK secret environment file?▼

Storing the DeepSeek API key in a local OMK secret environment file prevents accidental key leakage by keeping credentials out of the project repository and hidden from logs during agent workflows.

Can I use this OMK provider setup for DeepSeek without exposing my API key in logs?▼

Yes, this OMK provider setup enables DeepSeek-backed agent workflows without exposing your API key in logs or project files by isolating credentials in a user-local secret environment file.

What is the best way to verify my DeepSeek API key is available after setting it?▼

The best way to verify your DeepSeek API key availability is to run the subsequent OMK provider doctor verification command immediately after storing the key to confirm the provider setup.

Does configuring DeepSeek API credentials locally print or summarize the key during setup?▼

No, configuring DeepSeek API credentials requires strict handling rules that never print or summarize the key, ensuring your secret remains completely hidden during the local storage process.

Related Skills

Explore More Software Engineering Skills→
dmae97dmae97
130

deepseek-api

Set the DeepSeek API key in the user-local OMK secret environment file.

Community
Basic
dmae97dmae97
130

deepseek-enable

Enables DeepSeek as a read-only worker pool for OMK coding workflows.

Community
Basic
dingdyandingdyan

1password

Retrieve and inject 1Password secrets via the op CLI in tmux sessions.

Community
Advanced
chiptoe-svgchiptoe-svg

add-opencode

Integrate the OpenCode agent provider into NanoClaw for alternative LLM backends.

Community
Intermediate