SKILLEMALL.ai

CC dod-te-guidebook

Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (OUSD R&E, August 2022). Use for DoD test and evaluation (T&E) across the Adaptive Acquisition Framework — the four test communities (contractor testing, developmental DT&E, operational OT&E, live-fire LFT&E); the five operational events (Operational Demonstration, EOA, OA, IOT&E, FOT&E) and the OTRR gate; the T&E Strategy / TEMP and its IDSK, with the upstream documents that feed it and the test plans that decompose it; the T&E organizations and oversight roles (USD(R&E), DOT&E, TRMC, the Service Executives and OTAs, the T&E WIPT, CDT); and pathway-specific T&E for all six acquisition pathways (Urgent Capability, Middle Tier, Major Capability, Software, Defense Business Systems). Statutory anchors include 10 U.S.C. §4171 (IOT&E) and §4172 (LFT&E/FUSL). This is guidance, not policy: it points outward to DoDI 5000.89 and the DoDI 5000-series for binding detail, and is thin on detailed test statistics/design-of-experiments methodology, cost estimating, the Acquisition of Services pathway, and any CUI/CAC-gated companion guides.

jgsystemsconsulting/jgs-se-knowledge-packs Agent Skills author: jgsystemsconsulting 14 files body ≈ 4 066 tokens Open the sourcegithub.com↗ analyzed 29 h ago

Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (OUSD R&E, August 2022).

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

AnalyzerData and analyticsResearchAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Shorten the description to 1024 characters.
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: 14. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • error description-long description is 1108 chars, limit 1024

Process rating: all ten parameters 56/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4066 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place

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)
  • +3Description length 1108: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (0 code blocks)
  • +1License stated

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