SKILLEMALL.ai
GitHub ↗ RU Sign in

BB nda-review-jamie-tso

Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log with preferred redlines, fallbacks, rationales, owners, and deadlines.

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 8 files body ≈ 2 875 tokens Open the sourcegithub.com↗ analyzed 84 min ago

Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective…

As a process B 78/100 · Nearly there — weak spots: consistency, running it twice

AnalyzerLegalAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
B
78/100
Nearly there
Running it twice w 4
30
Consistency w 8
40
When it triggers w 12
50
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 8. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 78/100

  • 30Running it twice. 5 mutating operations with no state check
  • 40Consistency. Frontmatter name (nda-review-jamie-tso) differs from the folder (nda-reviewer-jamie-tso)
  • 50When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 48 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Execution cost. Instruction body is 2875 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill

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)
  • +2Single-language instructions
  • +3Description length 269: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 48 items
  • +3Output format is stated explicitly
  • +4Has examples (0 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)
  • +1License stated

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