CtrlK
BlogDocsLog inGet started
Tessl Logo

saas-msa-review

Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable legal-review skill with concrete checklists, a handoff schema, and well-sequenced validation checkpoints. Its main weaknesses are length/commentary padding and a monolithic single-file structure with no progressive disclosure into bundle references.

Suggestions

Trim editorial commentary (e.g. the "airlines negotiate ticket terms" line, "When (not if) we leave this vendor") to reduce token cost without losing the substantive guidance.

Move the detailed AI/ML 7-point procedure and the jurisdiction-delta table into a references/ file (e.g. SAAS-DEEP-DIVE.md) and link to it from SKILL.md to achieve one-level-deep progressive disclosure.

The "Reference: " prefix on the description frontmatter looks like a templating artifact; confirm whether it is intentional or should be removed.

DimensionReasoningScore

Conciseness

The body is mostly efficient, opinion-laden, playbook-specific guidance Claude would not already know (e.g. the 7-point AI/ML procedure, liability-cap decision procedure), but at ~246 lines it carries commentary padding such as "SaaS vendors, especially large ones, negotiate their paper about as willingly as airlines negotiate ticket terms" and "When (not if) we leave this vendor" that could be tightened.

2 / 3

Actionability

Despite being instruction-only with no code, the guidance is highly concrete and copy-paste ready: per-term bullet checklists (renewal term length, notice-to-cancel window, notice method, price on renewal), a verbatim YAML handoff schema with exact fields, and a full markdown output memo template.

3 / 3

Workflow Clarity

A clear end-to-end sequence (matter context → side determination → playbook → SaaS overlay 1-6 → AI/ML 7 steps → liability cap 4 steps → jurisdiction delta → output → handoffs) with explicit validation/stop checkpoints such as "If the matching side is [Not configured], stop and tell the user" and the "No silent supplement" stop-and-report block.

3 / 3

Progressive Disclosure

The file is well-organized with clear headers, but it is a monolithic ~246-line SKILL.md with no bundle reference files (references/scripts/assets absent) and no one-level-deep "See X.md" splits — content like the AI/ML checklist and jurisdiction delta table that could live in separate files is all inline, so it is not a 3.

2 / 3

Total

10

/

12

Passed

Description

85%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A clear, specific description with an explicit when-trigger and a well-scoped niche. Its only real weakness is trigger-term coverage, which leans on system-load phrasing and omits common user variations like "SaaS contract" or "MSA".

Suggestions

Add common natural variations users would say — e.g. "SaaS contract", "MSA", "software subscription", "renewal review" — to broaden trigger coverage.

Drop or clarify the leading "Reference: " prefix, which reads as a templating artifact rather than part of the description.

Reframe the trigger from a system condition ("Loaded by /commercial-legal:review when...") toward user-natural phrasing to improve trigger-term quality.

DimensionReasoningScore

Specificity

It lists multiple concrete review areas — "auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights" — applied to a named domain ("SaaS subscription agreements"), matching the anchor for listing multiple specific concrete actions; it is not a 2 because it goes beyond naming a domain and a few actions to enumerate five specific terms.

3 / 3

Completeness

It answers both what ("review of SaaS subscription agreements with attention to...") and when with an explicit trigger ("Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected"), satisfying the explicit-when requirement that would otherwise cap completeness at 2.

3 / 3

Trigger Term Quality

It includes some natural terms ("SaaS subscription agreements", "subscription deals", "SaaS or subscription agreement") but misses common variations users would say ("SaaS contract", "MSA", "software subscription", "renewal") and frames the trigger as a system load condition rather than user-natural keywords, so it is not a 3.

2 / 3

Distinctiveness Conflict Risk

The niche is clear and specific to SaaS/subscription deals with five distinct term axes, making it unlikely to trigger for a non-SaaS vendor agreement; it is not a 2 because the five enumerated SaaS terms carve out a distinct trigger surface beyond a generic "works with document files" overlap.

3 / 3

Total

11

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/claude-for-legal
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.