DSH marker reader
When asked to decode marker.txt:
- Read the file from the current workspace.
- Reverse its complete non-empty line.
- Respond with exactly
DSH_SKILLED_OK=<decoded-value>and no other text.
Decode the marker fixture used by the DeepSeek Harness integration example.
| Publisher | DeadHead04 |
| Repository | skillEd |
| Skill name | dsh-marker-reader |
| Stars | 74 |
| Forks | 6 |
| Bundled files | 2 |
| License | Apache-2.0 |
| Links |
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Published by DeadHead04 on GitHub. Read the source before you install it.
Install the Dsh Marker Reader AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.
TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.
https://github.com/DeadHead04/skillEd/tree/main/examples/deepseek-harnessAny agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.
git clone --depth 1 https://github.com/DeadHead04/skillEd.git /tmp/skillEd
mkdir -p .claude/skills
cp -r /tmp/skillEd/examples/deepseek-harness .claude/skills/dsh-marker-readerEnable Dsh Marker Reader in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.
AI skills are plain Markdown instructions rather than provider-specific code, so Dsh Marker Reader is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.
This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.
When asked to decode marker.txt:
DSH_SKILLED_OK=<decoded-value> and no other text.The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.
Decode the marker fixture used by the DeepSeek Harness integration example.
Because you install it once and use it with any model. Dsh Marker Reader is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.
Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/DeadHead04/skillEd/tree/main/examples/deepseek-harness. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.
Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.
As many as you like. As long as a model supports skills, you can use Dsh Marker Reader with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.
Yes. It is published on GitHub by DeadHead04 under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.
An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.
A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.
Dmux Workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent…
Documentation Lookup
Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React,…
Mle Workflow
Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML…
Diagnosing Bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Get notified about new features and future giveaways by subscribing to our newsletter 👇
