SKILLEMALL.ai
GitHub ↗ RU Sign in

BC commercial-legal-pl

Skill do analizy i tworzenia umów według polskiego prawa, ze szczególnym uwzględnieniem umów B2B, IP i IT (body leasing, NDA, wdrożenia, SaaS, przeniesienie praw autorskich, ugody). Powstał w Kancelarii Radców Prawnych Żurawska Piotrowski i Wspólnicy (ktzr.pl). Używaj zawsze gdy użytkownik prosi o przeanalizowanie polskiej umowy, audyt ryzyk umownych, wygenerowanie nowej umowy w stylu KTZR, dodanie/edycję klauzuli, sprawdzenie spójności umowy lub gdy wkleja/załącza polski dokument umowny do oceny. Stosuj również gdy pojawia się pojęcie "Złote Reguły KTZR", "essentialia negotii", "baza klauzul KTZR" lub gdy użytkownik wspomina o kancelarii KTZR / swojej kancelarii.

lawve-ai/awesome-legal-skills Agent Skills author: lawve-ai 68 files · 3 scripts body ≈ 3 780 tokens Open the sourcegithub.com↗ analyzed 70 min ago

Skill do analizy i tworzenia umów według polskiego prawa, ze szczególnym uwzględnieniem umów B2B, IP i IT (body leasing, NDA, wdrożenia, SaaS, przeniesienie…

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

ProcedureAI 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
93/100
safety, quality, tests
Safety 60%
99
Quality 40%
85
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security workflows/ocena-2-strony.md:13
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
    - "red team"
    quoted

Files scanned: 68. 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 57/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 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
  • 40Consistency. Frontmatter name (commercial-legal-pl) differs from the folder (ktzr-polskie-umowy-gospodarcze-adam-piotrowski)
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 23 steps
  • 100Execution cost. Instruction body is 3780 tokens
  • 100Running it twice. No mutating operations
  • low 17 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 672: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 23 items
  • +3Output format is stated explicitly
  • +4Has examples (5 code blocks)
  • +4Reference files are cited in the instructions (8 of 8)
  • +1License stated

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