Skip to content
TrustedSkillsbeta
Back to all skills

Contract Analyzer

Checked
jmsktm·vlatest·other

This Contract Analyzer swiftly extracts key terms and clauses from contracts, saving time and ensuring accurate understanding for legal review.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Installs under a different name. Its SKILL.md names it Contract Analyzer, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add jmsktm/claude-settings --skill "Contract Analyzer" -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jmsktm

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jmsktm/claude-settings at c113b0d7e1.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
c113b0d7e1
Manifest
skills/contract-analyzer/SKILL.md
Scanned
1 file, 45 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Contract Analyzer skill helps users understand and extract key information from legal contracts. It can identify clauses, summarize terms, and highlight potential risks within contract documents. This allows for faster review and improved comprehension of complex contractual language.

When to use it

  • Reviewing a new vendor agreement before signing.
  • Summarizing the key obligations in an existing service level agreement (SLA).
  • Identifying termination clauses in a lease agreement.
  • Quickly understanding the renewal terms outlined in a software license.

Key capabilities

  • Clause identification
  • Contract summarization
  • Risk highlighting

Example prompts

  • "Summarize this contract and highlight any clauses related to liability."
  • "What are the key obligations of each party in this agreement?"
  • "Identify the termination clause in this document."

Tips & gotchas

The skill's accuracy depends on the clarity and structure of the input contract. Complex or poorly formatted documents may yield less precise results.