SKILLEMALL.ai

CD dsh-find-simplifications

Find evidence-backed simplifications in DeepSeek Harness code, APIs, configuration, tests, and prose; write or consolidate proposals, identify small inline cleanups, or assess simplifications from another branch. Use for removing dead, duplicated, speculative, or unnecessarily maintained behavior and infrastructure.

The skillemall take

This skill hunts for simplifications in DeepSeek Harness code: dead code, duplicates, unnecessary infrastructure. It claims to spot candidates across code, APIs, configs, tests, and docs.

Two files in the package, but broken references suggest it's incomplete. Never run on models. Content scores 67/100—logic is there, but no real-world examples to verify accuracy. Process score 45 indicates missing validation steps. No critical bugs, but no proof of work either. Safety is fine.

Set it up if you already know DeepSeek Harness well and can hand-verify suggestions. Otherwise you'll spend more time fact-checking than you would writing from scratch.

deepseek-ai/deepseek-harness Agent Skills author: deepseek-ai MIT 2 files body ≈ 2 764 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Find evidence-backed simplifications in DeepSeek Harness code, APIs, configuration, tests, and prose; write or consolidate proposals, identify small inline…

As a process D 45/100 · Unfinished process — References files that are not bundled: ../../../docs/architecture.md, ../../../docs/defensive-patterns/README.md, ../../../docs/testing.md

AnalyzerInfrastructureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
D
45/100
Unfinished process
References files that are not bundled: ../../../docs/architecture.md, ../../../docs/defensive-patterns/README.md, ../../../docs/testing.md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../docs/architecture.md
  • warning missing-ref reference to a missing file: ../../../docs/defensive-patterns/README.md
  • warning missing-ref reference to a missing file: ../../../docs/testing.md
  • warning missing-ref reference to a missing file: ../../notes/README.md
  • warning missing-ref reference to a missing file: ../../../docs/defensive-patterns/general.md
  • warning missing-ref reference to a missing file: ../../../docs/development.md
  • warning missing-ref reference to a missing file: ../../notes/implemented/process/2026-07-26-dependencies-over-hand-rolling.md
  • warning missing-ref reference to a missing file: ../dsh-prose-standard/SKILL.md
  • warning missing-ref reference to a missing file: ../../notes/README.md
  • warning missing-ref reference to a missing file: ../dsh-archive-agent-notes/SKILL.md
  • warning missing-ref reference to a missing file: ../dsh-pre-push-checks/SKILL.md

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: ../../../docs/architecture.md, ../../../docs/defensive-patterns/README.md, ../../../docs/testing.md
  • 0Tools and files. 11 referenced file(s) missing: ../../../docs/architecture.md, ../../../docs/defensive-patterns/README.md, ../../../docs/testing.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 15 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2764 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 317: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 9 items
  • +4Reference files are cited in the instructions (1 of 1)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.