MCP API Key Authentication
Yourdaylight/stock_datasource
Sets up and troubleshoots MCP API key authentication for a stock data service, covering key creation, client configuration and per-tool usage statistics.
Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries.
Install Deepseek Provider Contract
$ npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config deepseek-provider-contract --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/operational/deepseek-provider-contract .claude/skills/deepseek-provider-contract && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "deepseek-provider-contract" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/deepseek-provider-contract into .claude/skills/deepseek-provider-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deepseek-provider-contract", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/deepseek-provider-contractType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config deepseek-provider-contract --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/operational/deepseek-provider-contract .agents/skills/deepseek-provider-contract && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deepseek-provider-contract" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/deepseek-provider-contract into .agents/skills/deepseek-provider-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deepseek-provider-contract", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config deepseek-provider-contract --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/operational/deepseek-provider-contract .cursor/skills/deepseek-provider-contract && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deepseek-provider-contract" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/deepseek-provider-contract into .cursor/skills/deepseek-provider-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deepseek-provider-contract", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AnastasiyaW/codex-claude-code-config.git --path skills/operational/deepseek-provider-contract--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config deepseek-provider-contract --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/operational/deepseek-provider-contract .gemini/skills/deepseek-provider-contract && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deepseek-provider-contract" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/deepseek-provider-contract into .gemini/skills/deepseek-provider-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deepseek-provider-contract", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AnastasiyaW/codex-claude-code-config deepseek-provider-contractInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/operational/deepseek-provider-contract .github/skills/deepseek-provider-contract && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deepseek-provider-contract" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/deepseek-provider-contract into .github/skills/deepseek-provider-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deepseek-provider-contract", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AnastasiyaW/codex-claude-code-config deepseek-provider-contract --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/operational/deepseek-provider-contract .opencode/skills/deepseek-provider-contract && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deepseek-provider-contract" agent skill from https://github.com/AnastasiyaW/codex-claude-code-config/tree/main/skills/operational/deepseek-provider-contract into .opencode/skills/deepseek-provider-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deepseek-provider-contract", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
deepseek-provider-contract- GitHub stars
- 154
- Token cost
- ~1.2k tokens
- SKILL.md length
- 540 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries.
- Works in 5 steps: Classify the proposed prompt/data.… → Freeze the provider model, endpoint,… → Save a redacted request-history fixture… → …
- Integrating DeepSeek
- SKILL.md covers Use It In This Order, Required Invariants, Adoption Decision and Gotchas, plus 2 more sections
- Runs Python scripts from its folder; needs DEEPSEEK_API_KEY
What it does
Deepseek Provider Contract is an agent skill from AnastasiyaW/codex-claude-code-config. Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries. Use when integrating DeepSeek, adding DeepSeek tool calls or streaming, debugging DeepSeek 400 after a tool call, or evaluating a DeepSeek harness/MCP. Do NOT use for a generic model comparison, ordinary local coding, or to send a repository transcript to a provider by default.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/test_validate_deepseek_history.py` and `scripts/validate_deepseek_history.py`).
It sits in Backend & APIs, covering Third-party API integration. It works with DeepSeek and Model Context Protocol. The repository describes itself as: Claude Code, Codex, and multi-agent configuration system: principles, hooks, skills, and workflow patterns for AI-assisted development. The licence is MIT.
When your agent uses it
- Integrating DeepSeek
- Adding DeepSeek tool calls
- Debugging DeepSeek 400 after a tool call
- Evaluating a DeepSeek harness/MCP
Example prompts
- “/deepseek-provider-contract”
Requirements
- Python 3
- A credential in DEEPSEEK_API_KEY
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Classify the proposed prompt/data. Private archive, credentials, customer
- Freeze the provider model, endpoint, request budget, and fallback in the
- Save a redacted request-history fixture that explicitly declares whether the
- Run the provider only in a bounded, opt-in experiment. Record model, endpoint,
- Compare against the incumbent on the same frozen task before adding any route
What it can do on your machine
Read from SKILL.md and the folder at commit 3601289. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
api-docs.deepseek.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
DEEPSEEK_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Deepseek Provider Contract loads about 1.2k tokens when it runs. Until then it costs about 126 tokens; SKILL.md has 540 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from AnastasiyaW/codex-claude-code-config at commit 3601289, republished under its MIT licence (© AnastasiyaW). 540 words, ~1,161 tokens.
Download SKILL.mdSave it as
.claude/skills/deepseek-provider-contract/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- deepseek-provider-contract
- description
- Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries. Use when integrating DeepSeek, adding DeepSeek tool calls or streaming, debugging DeepSeek 400 after a tool call, or evaluating a DeepSeek harness/MCP. Do NOT use for a generic model comparison, ordinary local coding, or to send a repository transcript to a provider by default.
DeepSeek Provider Contract
This is a local, offline contract check. It neither reads DEEPSEEK_API_KEY nor
sends code, transcripts, or secrets. A third-party harness is an implementation
candidate, not a trusted route.
Use It In This Order
Classify the proposed prompt/data. Private archive, credentials, customer data, and whole transcripts stay local unless the user explicitly authorizes that provider and scope.
Freeze the provider model, endpoint, request budget, and fallback in the integration plan. Do not inherit defaults from a community wrapper.
Save a redacted request-history fixture that explicitly declares whether the outbound request carries tools, then run:
The fixture shape is
{"outbound_request":{"tools":[...]},"messages":[...]}; use"tools": []only for an outbound tools-free request.text python skills/operational/deepseek-provider-contract/scripts/validate_deepseek_history.py fixture.jsonRun the provider only in a bounded, opt-in experiment. Record model, endpoint, max output, cache-usage fields, request digest, and observed result.
Compare against the incumbent on the same frozen task before adding any route to a workflow. A passing history fixture proves message lifecycle only; it does not prove quality, price, availability, or data handling.
Required Invariants
- In thinking mode with tools, preserve the provider's complete assistant
message, including
reasoning_contentandtool_calls. Do not rebuild a reduced assistant message fromcontentalone. - Each tool result has the exact prior
tool_call_id. - While a request carries
tools, retain the documentedreasoning_contentfrom prior assistant turns in its history. Do not reduce this to only the most recent tool-call turn; check the current provider documentation because model and endpoint semantics change. - Use strict schema only with the beta endpoint and only after validating the supported JSON Schema subset. Never call a schema "strict" merely because it looks valid locally.
- Set output bounds explicitly and make cache hits/misses observability, not a correctness promise.
Adoption Decision
Adopt a DeepSeek route only when all are true:
- The offline history validator and its regression tests pass.
- A redacted live canary succeeds with the exact frozen integration.
- The frozen benchmark beats or materially supplements the current route.
- Provider data scope and failure fallback are written down.
Otherwise keep this skill and the fixture only; do not install a global MCP.
Show full SKILL.md (190 more words)Show less
Gotchas
- For a tools-bearing request, the current DeepSeek documentation requires the
prior assistant
reasoning_content; a tools-free request has different context semantics. Treat the offline validator as a narrow fixture check, not a substitute for the live API contract. - A response can say cache-hit while quality or latency still changes; measure those separately.
- A history normalizer that strips
reasoning_contentcan make the next tools-bearing request request fail with HTTP 400 even if the first request succeeded. - Model names, limits, pricing, and beta semantics are provider facts: re-check the official documentation at the integration date.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| HTTP 400 after a tool result | Assistant reasoning was discarded | Preserve the complete assistant tool-call message and rerun the validator |
| Tool JSON is rejected in strict mode | Wrong endpoint or unsupported schema | Use the beta endpoint, validate the schema subset, or turn strict mode off |
| Wrapper works once then loses context | History was normalized too aggressively | Compare its persisted fixture with the provider contract |
| Temptation to add global MCP | Scope and data boundary were skipped | Keep it opt-in until a frozen canary and benchmark pass |
Sources
© AnastasiyaW, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts) in skills/operational/deepseek-provider-contract of AnastasiyaW/codex-claude-code-config.
- SKILL.md
- scripts/test_validate_deepseek_history.py
- scripts/validate_deepseek_history.py
Open the folder on GitHubat commit 3601289
Compare with similar skills
Deepseek Provider Contract next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deepseek Provider Contract this skillAnastasiyaW/codex-claude-code-config | 154 | — | ~1.2k | Automated safety check: Pass | MIT | |
| MCP API Key AuthenticationYourdaylight/stock_datasource | 189 | — | ~1.2k | Automated safety check: Pass | MIT | |
| LangBot EBA Adapter Developmentlangbot-app/LangBot | 18k | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| DisCatSharp Discord DevelopmentAiko-IT-Systems/DisCatSharp | 140 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Cdesktopcdesktop-ai/cdesktop | 158 | — | ~697 | Automated safety check: Pass | Apache-2.0 | |
| Apify Integration Developmentapify/agent-skills | 2.4k | — | ~3.4k | Automated safety check: Pass | None |
Similar skills
LangBot EBA Adapter Development
langbot-app/LangBot
Guides building, migrating and testing LangBot messaging-platform adapters for the Event-Based Agents layout, with unified event and message conversion.
DisCatSharp Discord Development
Aiko-IT-Systems/DisCatSharp
Helps build, explain and troubleshoot C# Discord apps on DisCatSharp, answering from the project's installed version and the library's documentation rather than guesses.
Cdesktop
cdesktop-ai/cdesktop
Operate the cdesktop coding-session environment — agent teams, session management, file conventions.
- Official
Apify Integration Development
apify/agent-skills
Guides designing and building an official Apify integration for a company's product: workflow-automation apps, AI agent plugins, AI framework packages or direct API clients.
Atlassian MCP Expert
Jeffallan/claude-skills
Queries and edits Jira issues and Confluence pages through an MCP server, covering JQL and CQL queries, server setup, authentication and sprint or backlog workflows.
More from AnastasiyaW/codex-claude-code-config
All 50 skills in this repoBug Reproducer
AnastasiyaW/codex-claude-code-config
Find likely software bugs in a codebase, rank concrete bug candidates, and prove or reject them with focused regression tests before proposing a fix.
Motion Framer
AnastasiyaW/codex-claude-code-config
A skill your agent uses when implementing Motion or Framer Motion in React/JavaScript: interactive UI components, micro-interactions, gestures, layout or page transitions, and scroll-based animation.
Proof Verify
AnastasiyaW/codex-claude-code-config
Plan-based verification - freeze acceptance criteria before building, then verify after with an independent fresh-context agent (the builder must not verify their own work).
Workflow Orchestration
AnastasiyaW/codex-claude-code-config
Написание и запуск Claude Code dynamic workflows (JS-оркестратор субагентов).
Notebooklm Grounded Research
AnastasiyaW/codex-claude-code-config
A skill your agent uses when: NotebookLM, notebooklm MCP, large documentation sets, courses, books, papers, or citation-backed research are mentioned.
Desktop Sessions Discovery
AnastasiyaW/codex-claude-code-config
Discover, search, and selectively restore Claude desktop app sessions hidden across multiple accountIds.
Related
Works with
Categories
Questions about Deepseek Provider Contract
What does Deepseek Provider Contract do?
Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries. Deepseek Provider Contract is an agent skill from AnastasiyaW/codex-claude-code-config. Validate a proposed DeepSeek API integration before any key or project context is sent: check thinking-mode tool-call history, strict-schema assumptions, bounded output, and provider data boundaries.
When should I use Deepseek Provider Contract?
Deepseek Provider Contract fits situations like: integrating DeepSeek; adding DeepSeek tool calls; debugging DeepSeek 400 after a tool call; evaluating a DeepSeek harness/MCP.
How do I install Deepseek Provider Contract in Claude Code?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a claude-code`. Or copy the skill folder (skills/operational/deepseek-provider-contract in AnastasiyaW/codex-claude-code-config) into .claude/skills/deepseek-provider-contract in your project. Claude Code loads it when a task matches its description.
How do I install Deepseek Provider Contract in Codex?
Run `npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a codex`. Or copy the skill folder (skills/operational/deepseek-provider-contract in AnastasiyaW/codex-claude-code-config) into .agents/skills/deepseek-provider-contract in your project. Codex loads it when a task matches its description.
Can I use Deepseek Provider Contract in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AnastasiyaW/codex-claude-code-config --skill deepseek-provider-contract -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deepseek-provider-contract, .gemini/skills/deepseek-provider-contract, .github/skills/deepseek-provider-contract and .opencode/skills/deepseek-provider-contract in your project.
What does Deepseek Provider Contract need to run?
Going by SKILL.md and its folder, Deepseek Provider Contract needs Python for the scripts in its folder and credentials named DEEPSEEK_API_KEY. Our summary lists: Python 3; A credential in DEEPSEEK_API_KEY.
Does Deepseek Provider Contract access the network?
SKILL.md names 1 domain. As links in the text: api-docs.deepseek.com. This is read from the text; nothing was executed.
Is Deepseek Provider Contract safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Deepseek Provider Contract use?
Deepseek Provider Contract is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Deepseek Provider Contract use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Deepseek Provider Contract?
Skills that share tags, products or a category with Deepseek Provider Contract: MCP API Key Authentication (Yourdaylight/stock_datasource, 189 stars), LangBot EBA Adapter Development (langbot-app/LangBot, 18k stars), DisCatSharp Discord Development (Aiko-IT-Systems/DisCatSharp, 140 stars) and Cdesktop (cdesktop-ai/cdesktop, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Deepseek Provider Contract?
AnastasiyaW (a GitHub user) maintains it in AnastasiyaW/codex-claude-code-config, which has 154 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 11, 2026.
Source: AnastasiyaW/codex-claude-code-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.