← ClaudeAtlas

propperlisted

Foundation for every Propper agreement task — authenticate, route to the right tool, read the agreement status model, and triage scope and permission errors. Load this before creating, sending, tracking, voiding or importing anything in Propper, and whenever a Propper tool returns an authentication, scope or state error.
mypropper/skills · ★ 1 · AI & Automation · score 72
Install: claude install-skill mypropper/skills
# Propper Propper is an agreement platform: generate a document, place signature fields, route it to signers, and track it to completion. This skill owns authentication, tool routing, the status model and error triage. Every other Propper skill builds on it. ## Authenticate first Call `get_current_user` before any other Propper tool. It requires no scopes, so it is the cheapest probe for both "is the server connected" and "who am I". Branch on the result: **Authenticated** — the call returns a user with name, email, organization and roles. Report the organization before acting on anything that writes. Proceed. **Server connected, not authenticated** — the call fails with an authentication error. The MCP server is reachable but no valid token is held. Tell the user to complete the OAuth flow in their host, then retry. See [references/auth.md](references/auth.md). **Server not available** — no Propper tools are present in the session at all. Do not guess at Propper state or fabricate agreement data. Say the Propper MCP server is not connected, give the one-line setup from [references/auth.md](references/auth.md), and offer the work that needs no account: `signature-ready-check` to pre-flight a document, `compare-contract-versions` to diff two drafts, `extract-contract-dates` to pull deadlines out of a local file, `embed-signing-in-your-app` for integration work, `migrate-from-docusign` to audit a DocuSign export, `agreement-starter-pack` to draft template content locally