Individual skill

deepseek-provider-contract

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.

skills/operational/deepseek-provider-contract/SKILL.md

Read pinned source

Source commit 849719987d9c0d6ed973bdbce8ed37b266d3b1f3

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
214
Repository last updated
Nov 5, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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

1. Classify the proposed prompt/data. Private archive, credentials, customer
   data, and whole transcripts stay local unless the user explicitly authorizes
   that provider and scope.
2. Freeze the provider model, endpoint, request budget, and fallback in the
   integration plan. Do not inherit defaults from a community wrapper.
3. Save a redacted request-history fixture that explicitly declares whether the