Propper Skills

Propper skills guide Claude through document checks, generation, signing, and follow-up. The public mypropper/skills repository contains the instructions, starter templates, and plugin configuration. The skills are free to download under the Apache 2.0 license.

The plugin includes both the skills and the connection configuration for https://mcp.propper.ai/mcp. You still sign in to Propper and authorize access before using connected tools. See Use Propper in Claude for prerequisites.

Install in Claude Cowork

1. Open Cowork and select Customize → Plugins.
2. Under Personal plugins, choose + → Add marketplace.
3. Choose the repository option and enter https://github.com/mypropper/skills.
4. Install Propper from the marketplace.
5. Follow the Propper authentication prompt before using connected tools. Confirm the organization and permissions on the consent screen.

If your organization manages plugins, use its approved marketplace instead. Anthropic's plugin guide explains personal installation and access settings.

Install in Claude Code

Run these commands inside Claude Code:

/plugin marketplace add mypropper/skills
/plugin install propper@propper-marketplace

Then run /mcp to check the Propper connection and authenticate. Follow the Claude Code guide for a complete walkthrough, installation scopes, and an MCP-only alternative.

These instructions install directly from the Propper repository; they do not depend on Propper appearing in a directory search.

Make the plugin available to your organization

On Claude Team or Enterprise, an Owner or Primary Owner can distribute the plugin. Enable Cowork and Skills, then select the correct Claude organization.

1. In a terminal with Git installed, prepare a ZIP:

   git clone --depth 1 https://github.com/mypropper/skills.git propper-skills
   git -C propper-skills archive --format=zip --output=../propper-plugin.zip HEAD

   The ZIP contains .claude-plugin/plugin.json, .mcp.json, and skills/ at its root. Do not wrap them in an extra folder.

2. Open Organization settings → Plugins. Select Add plugins → Upload a file.

3. Select Upload to a new marketplace, name it Propper tools, and upload propper-plugin.zip. An existing manual marketplace also works.

4. Set User access for propper so members can install it, or choose Installed by default.

5. Have a member install the plugin if needed and complete Propper authentication. Plugin distribution does not authorize a member's Propper account.

For updates, upload a fresh ZIP with the same plugin name. For Sync from GitHub, Claude requires a private or internal marketplace repository with the Claude GitHub App installed; the public mypropper/skills repository cannot be the organization sync repository. See Anthropic's organization plugin guide for managed distribution and updates.

Choose a skill

Describe the task naturally and provide the document or template to work with. Claude can select the relevant skill. In Claude Code, you can also invoke a skill explicitly, for example:

/propper:signature-ready-check Check ./agreement.pdf before I send it.

Skill	Use it to
signature-ready-check	Find blanks, inconsistent names, missing exhibits, and date mistakes before sending.
compare-contract-versions	Compare two versions clause by clause, including changed amounts, dates, and references.
extract-contract-dates	Extract renewal dates, notice deadlines, milestones, and termination dates.
send-for-signature	Prepare an agreement, recipients, signing order, and fields, then request confirmation to send.
place-signature-fields	Locate signature blocks and prepare signature, initial, and date fields.
track-agreements	Check recipient progress, find outstanding agreements, and retrieve completed copies.
generate-document	Merge supplied data into a generation template.
build-gen-template	Turn a recurring document into a reusable template with merge fields and signature anchors.
migrate-from-docusign	Audit a template export, identify migration gaps, and import supported content.
agreement-starter-pack	Start from nine bundled agreement templates, including NDAs, an MSA, an SOW, and an offer letter.
embed-signing-in-your-app	Work through OAuth, embedded signing, and verified webhooks in your application.
propper	Handle authentication, tool selection, agreement states, and permission errors.
agreement-workflows	Supply shared recipient roles and confirmation rules for the other skills.

The repository catalog includes prompts and the individual skill instructions.

Work without a Propper account

Document checks, version comparisons, and date extraction from local files do not call Propper tools. You can also audit a template export, draft from the starter pack, and use embedded-signing guidance before connecting. Creating templates, storing documents, and sending agreements in Propper require an authorized connection.

Your assistant processes the files you provide under its own data-handling policies. Contract checks identify consistency and completeness issues; they do not determine whether terms are enforceable or appropriate. Have counsel review the generic starter templates before using them.

Review before sending

The skills instruct Claude to show the agreement, documents, recipients, and signing order before requesting explicit approval to send. Voiding a sent agreement notifies its recipients; deleting is limited to drafts. Keep tool approvals enabled and review each proposed action.

Other agents and skills-only installation

The repository also supports installing the Markdown instructions with the skills CLI:

npx skills add mypropper/skills

This installs skills only. Configure an MCP connection separately to use connected tools, using https://mcp.propper.ai/mcp and OAuth. The repository installation guide covers selecting individual skills and agents.

Troubleshooting

• Plugin missing from search: add the repository marketplace directly using the steps above.
• Members cannot see the plugin: check the selected organization, Cowork and Skills settings, and the plugin's member access.
• Skills appear but Propper tools fail: authenticate the MCP connection and check permissions. A skills-only installation needs a separate MCP connection.
• A local check requests Propper access: clarify that the task should use only the supplied local files; connect when you want to create or modify records in Propper.

See Propper Skills for Claude for workflow examples and the organization setup announcement.