signature-request

Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.

설치로 이동

저장소: anthropics/knowledge-work-plugins
최근 소스 활동: 2026년 3월 13일 15:57
감지된 SKILL.md 언어: 영어
스타: 25,304
포크: 3,008

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/anthropics/knowledge-work-plugins --skill signature-request

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

name: signature-request
description: Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. Use when a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers.
argument-hint: <document or contract to send>

# /signature-request -- E-Signature Routing > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Prepare a document for electronic signature — verify completeness, set signing order, and route for execution. **Important**: This command assists with legal workflows but does not provide legal advice. Verify documents are in final form before sending for signature. ## Usage ``` /signature-request $ARGUMENTS ``` Prepare for signature: @$1 ## Workflow ### Step 1: Accept the Document Accept the document in any format: - **File upload**: PDF, DOCX - **URL**: Link to a document in ~~cloud storage or ~~CLM - **Reference**: "The Acme Corp MSA we finalized yesterday" ### Step 2: Pre-Signature Checklist Before routing for signature, verify: ```markdown ## Pre-Signature Checklist - [ ] Document is in final, agreed form (no open redlines) - [ ] All exhibits and schedules are attached - [ ] Correct legal entity names on signature blocks - [ ] Dates are correct or left blank for execution date - [ ] Signature blocks match the authorized signers - [ ] Any required internal approvals have been obtained - [ ] Document has been reviewed by appropriate counsel ``` ### Step 3: Configure Signing Gather signing details: - **Signers**: Who needs to sign? (names, emails, titles) - **Signing order**: Sequential or parallel? - **Internal approval**: Does anyone need to approve before the counterparty signs? - **CC recipients**: Who should receive a copy of the executed document? ### Step 4: Route for Signature **If ~~e-signature is connected:** - Create the signature envelope/request - Set signing fields and order - Add any required initials or date fields - Send for signature **If not connected:** - Generate a signing instruction document - Provide the document formatted for wet signature or manual e-sign - List all signers with contact information ## Output ```markdown ## Signature Request: [Document Title] ### Document Details - **Type**: [MSA / NDA / SOW / Amendment / etc.] - **Parties**: [Party A] and [Party B] - **Pages**: [X] ### Pre-Signature Check: [PASS / ISSUES FOUND] [List any issues that need attention before sending] ### Signing Configuration | Order | Signer | Email | Role | |-------|--------|-------|------| | 1 | [Name] | [email] | [Party A Authorized Signatory] | | 2 | [Name] | [email] | [Party B Authorized Signatory] | ### CC Recipients - [Name] — [email] ### Status [Sent for signature / Ready to send / Issues to resolve first] ### Next Steps - [What to expect after sending] - [Expected turnaround time] - [Follow-up if not signed within X days] ``` ## Tips 1. **Check entity names carefully** — The most common signing error is incorrect legal entity names. 2. **Verify authority** — Make sure each signer is authorized to bind their organization. 3. **Keep a copy** — Executed copies should be filed in ~~cloud storage or ~~CLM immediately after execution.

GitHub에서 보기

검색으로 돌아가기 설치로 돌아가기

ad-manager

The ads consultant that becomes an ads agent. Reads paid-ad performance natively through the TikTok Ads connector, or via a build-connector Zapier connection for other ad platforms, explains in plain English what is working and what is burning money, recommends budget, targeting, and creative changes with the dollar impact of each, drafts new ad copy in the owner's voice plus Canva creative briefs, and — only after an explicit yes — executes the approved changes in the ad account. Works from exported CSV reports when nothing is connected, the normal starting point. Use this whenever the owner talks about ads or ad spend at all, including "are my ads working," "what's my ROI on ads," "I'm spending money on Facebook and I don't know what I'm getting," "should I turn this campaign off," "my cost per lead is going up," "write me a new ad," "who should I be targeting," or "the ad guy quit."

2026-09-15

ap-processor

Works the bill pile end to end: reads bills and vendor statements out of the AP inbox or from uploaded PDFs and phone photos, pulls out vendor, amount, due date, and line detail, codes each one to the right account and job, matches it against the purchase order and the receiving ticket, then stages the entries and a proposed payment run in QuickBooks, Xero, or NetSuite for the owner to approve in one pass. Nothing is entered and nothing is paid without an explicit yes. Reach for this whenever bills, vendor invoices, or paying people comes up — including "what do I owe," "the bills are piling up," "pull the invoices out of my email and into QuickBooks," "code these for me," "who needs to get paid this week," "did we get billed twice," or when the owner forwards a supplier invoice with no message at all. Use it before cash-flow-snapshot or month-end-prep so those run on real payables instead of a guess.

2026-09-15

brand-style

Sets and updates the owner's brand look and output preferences, which every page and document the plugin produces then follows automatically. Captures the brand from a pasted website link or a plain-words description — never a hex code, color picker, or upload — previews it on a sample page, asks how they want their outputs delivered (visual artifacts, Word docs, markdown, Notion pages, Canva Docs, or best-for-the-skill), and saves both to the business profile. Runs inside smb-onboard on first setup and stands alone forever after. Use when the owner says "update my brand," "we rebranded," "change my colors," "make the reports match our new look," "change how you give me reports," "I want Word docs instead," or anything about the look or format of what the plugin hands them.

2026-09-15

이 저장소의 모든 Skills 보기

signature-request

소스 정보

설치 방법

소스 파일 검토

이 저장소의 다른 Skills

이 저장소의 다른 Skills