Send a single request to DeepSeek for summarization, information extraction, or simple classification. Receive the response and token usage as JSON for further processing, with structured status information when the API is unavailable.
One-shot chat completion against DeepSeek's `deepseek-chat` model via the OpenAI-compatible /v1/chat/completions endpoint. Reads DEEPSEEK_API_KEY from the environment; degrades gracefully (exit 0 with a JSON status:degraded envelope) when the key is missing or the API is unreachable. Use for non-reasoning tasks — summarization, extraction, quick classification — where deepseek-reasoner would be overkill.
Review the instructions the agent will receive before you install.
Wraps DeepSeek's chat/completions endpoint in the same subprocess-invocation
shape as the other ruflo-*-harness skills (see ruflo-metaharness's
harness-score for the reference). No library import on ruflo's boot path.
deepseek-reason instead — same plugin, different model.The prompt and any --system text are sent over the network to api.deepseek.com, a third party. Do not put secrets, credentials, personal data or proprietary code you are not allowed to share into them. The API key is read from DEEPSEEK_API_KEY in your shell only; never paste it into a prompt, a file or a command line.
Implementation: scripts/chat.mjs.
DEEPSEEK_API_KEY from env. If missing, emit
{ status: 'degraded', reason: 'DEEPSEEK_API_KEY is not set', ... }
and exit 0 (ADR-150-style graceful degradation).https://api.deepseek.com/v1/chat/completions with
{ model, messages, temperature?, max_tokens? }. 60s hard timeout.choices[0].message.content and usage counters.--format table prints only the content (for piping); --format json
(default) returns the full envelope.--alert-on-error exits 1 on any degraded/error status (CI-friendly).node plugins/ruflo-deepseek-harness/scripts/chat.mjs \
--prompt "In one sentence: what is HNSW?" \
--temperature 0.2
Sample output:
{
"status": "ok",
"model": "deepseek-chat",
"content": "HNSW is a graph-based approximate nearest neighbor …",
"finishReason": "stop",
"usage": { "promptTokens": 12, "completionTokens": 34, "totalTokens": 46 }
}
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.