dod-digital-engineering SKILL.md skillA
dod-digital-engineering from jgsystemsconsulting/jgs-se-knowledge-packs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jgsystemsconsulting/jgs-se-knowledge-packs/dod-digital-engineering@git:20260626.6ede444Pins git:20260626.6ede444 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jgsystemsconsulting/jgs-se-knowledge-packs
- Path
packs/dod-digital-engineering/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260626.6ede444, committed Jun 26, 2026
- First version recorded
- Jun 23, 2026
- Size
- 14,554 bytes
- Repository stars
- 71
- License
- a license file GitHub does not identify
Knowledge base from the DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)). Use for the Department of Defense's five digital engineering goals — (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; (5) transform the culture and workforce — plus their focus areas, the document-to-model and design-build-test→model-analyze-build…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- argument-hint: [digital engineering goal (1-5), focus area, authoritative source of truth, model formalisms, governance, infrastructure, culture/workforce, next steps, chapter number] --> # DoD Digital Engineering Strategy (2018) **Source**: OUSD R&E / ODASD(SE) (US Government work, public domain) | **Chapters**: 7 ## When to use Use this skill when you need to reason about the Department of Defense Digital Engineering Strategy (2018, OUSD/ODASD(SE)) and its five goals: (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; and (5) transform the culture and workforce. This pack also covers model formalisms, provenance, governance and access control of the authoritative source of truth, and the coordinate-plan-pilot-sustain rollout sequence. It is a vision-and-policy source, not a how-to method or tool tutorial. **Prerequisites:** none, plain Markdown; no MCP server, API key, or licence tier needed at runtime. ## How to Use This Skill …
Read the whole file at its exact version.
How to install
mdr add jgsystemsconsulting/jgs-se-knowledge-packs/dod-digital-engineering@sha256:3440b548f5b4034cThe line at the top of this page pins the label git:20260626.6ede444, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_bt4atejwc2neuguk)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 23, 2026 and Jun 26, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260626.6ede444 latest | 2026-06-26 | 6ede444 | 14,554 B | A | view · diff |
| git:20260623.b69a719 | 2026-06-23 | b69a719 | 13,783 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14554 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jgsystemsconsulting/jgs-se-knowledge-packs · 71 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bt4atejwc2neuguk GET https://markdownregistry.com/api/v1/resolve?ref=jgsystemsconsulting/jgs-se-knowledge-packs/dod-digital-engineering GET https://markdownregistry.com/api/v1/blob/3440b548f5b4034c9449b8d9e4ef661aee4a3c5dc1f124f58ebee062ab7fcaf7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.