E-Signature Field Placement
Deterministic e-signature field placement via browser automation: numeric coordinates, fixed signature page, per-recipient ownership, hard gate before send.
- What
- Deterministic e-signature field placement via browser automation: numeric coordinates, fixed signature page, per-recipient ownership, hard gate before send.
- Cost
- Free
- Needs
- a web e-signature composer, and a browser session already signed in by a human. The automation never enters credentials.
- Level
- Beginner — a web e-signature composer…
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a deterministic method for placing signature, date and text fields in a web e-signature composer through a browser automation session, written as a workflow contract rather than an executable controller. Uses numeric Location panel coordinates instead of drag for repeatable positions, a fixed signature page layout (your block first: By, Name, Title, Email, Date, then the counterparty block), correct per-recipient ownership, and a hard gate before anything is sent or signed, with save-as-draft as the default. Preconditions: the browser session is already signed in by a human and the automation never enters credentials or one-time codes (a login redirect prints LOGGED OUT and exits non-zero); every sensitive read and mutation is validated against a trusted configuration of exact HTTPS origins and document identity, with no substring or domain-suffix matching. Includes document geometry calibration, screenshot capture and a draft envelope for operator review before send. From the affaan-m/ECC repository (MIT). Honest caveats: pairs with the master-agreement-generator skill for generated agreements; placement reliability depends on the composer's DOM stability. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
E-Signature Field Placement is a free Muse skill and deterministic method for placing signature, date and text fields in a web e-signature composer through a browser automation session, written as a workflow contract rather than an executable controller. It uses numeric Location panel coordinates instead of drag, a fixed signature page layout, per-recipient ownership, and a hard gate before sending.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "E-Signature Field Placement" with your Muse. Prerequisites: a web e-signature composer, and a browser session already signed in by a human. The automation never enters credentials. 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/esign-field-placement/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Prepare an envelope for [agreement] with calibrated field placement" or "Verify field ownership for each recipient before drafting." 3. Calibrate the document geometry first, place fields with numeric coordinates, and stop at the save-as-draft gate for operator review. Tip: put the signature page on its own page with a fixed layout; field drift almost always starts with a reflowed document. Safety: a skill is plain-text instructions; it runs nothing by itself. Never feed it credentials, one-time codes, or signed legal authority it should not have.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.