agentleFS
AgriciDanielAgriciDaniel/deepseek-harness-brain/SKILL.md

deepseek-harness-brain

Skill9 starsChanged 3 months agoMITView on GitHub

Scaffold and operate DeepSeek Harness Brain, a source-cited Obsidian brain for DeepSeek Harness architecture, operations, extension development, security, testing, and debugging. Use when the user says "deepseek-harness-brain", "DeepSeek Harness Brain", "create a DeepSeek Harness architecture, operations, extension development, security, testing, and debugging brain", "import sources", "synthesize plan", "render report", or wants a persistent vault-backed operating system for DeepSeek Harness architecture, operations, extension development, security, testing, and debugging.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never store credentials in the vault.

    line 56
  2. Distinctive:

    Never make domain-specific claims without dated trustworthy sources.

    line 57
  3. Very specific:

    Keep hot, index, overview, and log current.

    line 58
  4. Distinctive:

    No claim that a keyless, static, build, snapshot, browser, or real-API check proves a stronger tier than it actually ran

    line 82
  5. Distinctive:

    No invented package behavior, event semantics, defaults, compatibility promise, vulnerability, benchmark, or release status

    line 83
  6. Distinctive:

    No credentials, tokens, cookies, private settings, or local secret values in brain artifacts

    line 84
  7. Distinctive:

    No instruction to weaken sandbox, approval, host-trust, or credential boundaries merely to make a command pass

    line 85
  8. Distinctive:

    No mutation, publication, deployment, account change, or production action from this advisory brain

    line 86
  9. Distinctive:

    No reliance on archived Agent Notes as current authority when source or current documentation disagrees

    line 87
  10. Very specific:

    Do not call this brain market-ready unless scripts/audit_brain.py --require market-ready passes and references/release-status.json records …

    line 89

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DeepSeek Harness Brain

Operate the deployed vault first. Treat CODEX.md, wiki/hot.md, and wiki/index.md as vault-root-relative paths, where the vault root is the directory passed to --vault or opened in Obsidian. In this repo, the template vault root is assets/template-brain/ and the demo vault root is examples/sample-vault/.

Secretary: use agents/deepseek-harness-secretary.md for grounded answers, claim review, and vault maintenance. That secretary reads the brain first, cites a vault note and an official URL, and stays advisory and read-only.

Commands

/deepseek-harness-brain new <client-slug> --owner <name>
/deepseek-harness-brain ingest --vault <path> --file <source>
/deepseek-harness-brain import-checkout --checkout <path> --vault <path> --expected-commit <sha> --as-of <date>
/deepseek-harness-brain synthesize --vault <path>
/deepseek-harness-brain portability --inventory <json> --json-out <json> --markdown-out <md>
/deepseek-harness-brain portability-html --markdown <md> --out <html>
/deepseek-harness-brain report --vault <path>
/deepseek-harness-brain visuals --vault <path>
/deepseek-harness-brain lint --vault <path>
/deepseek-harness-brain hash --vault <path> --check <fixture>
/deepseek-harness-brain next --vault <path>

Source checkout equivalent:

deepseek-harness-brain new <client-slug> --owner <name>
deepseek-harness-brain ingest --vault <path> --file <source>
deepseek-harness-brain import-checkout --checkout <path> --vault <path> --expected-commit <sha> --as-of <date>
deepseek-harness-brain synthesize --vault <path>
deepseek-harness-brain report --vault <path> --html-only

Required Operating Rules

  1. Read <vault>/CODEX.md.
  2. Read <vault>/wiki/hot.md.
  3. Read <vault>/wiki/index.md.
  4. Preserve .raw/ as immutable source material.
  5. Never store credentials in the vault.
  6. Never make domain-specific claims without dated trustworthy sources.
  7. Keep hot, index, overview, and log current.
  8. Record research evidence in references/source-ledger.json.
  9. Record domain adapter completion in references/adapter-manifest.json.

Script Mapping

The plugin tool allowlist is intentionally read-only. These commands document bounded repository scripts for the user or an explicitly authorized shell workflow. Loading the skill alone does not grant an agent write authority.

  • new -> python scripts/scaffold_vault.py
  • ingest -> python scripts/ingest_source.py
  • import-checkout -> python scripts/import_deepseek_harness.py
  • synthesize -> python scripts/synthesize_brain.py
  • portability -> python scripts/synthesize_deepseek_harness.py
  • portability-html -> python scripts/render_portability_report.py
  • report -> python scripts/render_brain_report.py
  • visuals -> python scripts/generate_vault_visuals.py
  • lint -> python scripts/lint_vault.py
  • hash -> python scripts/hash_vault.py
  • next -> python scripts/guide_next_action.py

Quality Gates

  • No claim that a keyless, static, build, snapshot, browser, or real-API check proves a stronger tier than it actually ran
  • No invented package behavior, event semantics, defaults, compatibility promise, vulnerability, benchmark, or release status
  • No credentials, tokens, cookies, private settings, or local secret values in brain artifacts
  • No instruction to weaken sandbox, approval, host-trust, or credential boundaries merely to make a command pass
  • No mutation, publication, deployment, account change, or production action from this advisory brain
  • No reliance on archived Agent Notes as current authority when source or current documentation disagrees

Do not call this brain market-ready unless scripts/audit_brain.py --require market-ready passes and references/release-status.json records an explicit human-reviewed market-ready decision. Demo verification is not market readiness. Community readiness covers safe distribution of this knowledge base. It does not claim browser, live-provider, native, cross-platform, security-audit, or production-scale runtime evidence.

Research Refresh

on every DeepSeek Harness release or architecture change; monthly while the project remains in developer preview

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.