Skip to content

formify-e-sign/formify-skills / plugins/formify-es-real-estate/skills/formify-es-real-estate

formify-es-real-estate

Verified

ES Real Estate Formify: the six documents a Spanish estate agency signs most (nota de encargo, KYC comprador y vendedor, oferta y reserva, contrato de arras, colaboración entre agencias, entrega de llaves), bilingual Spanish plus the client language, region-correct, signed through Formify. Use for a Spanish property sale or letting: encargo, mandato, reserva, arras, señal, KYC, blanqueo, llaves. Every run starts with scripts/start.py, which prints the welcome lines.

FileKindSize
LICENSEother1.0 KB
README.mdmarkdown3.0 KB
SKILL.mdskill md30.4 KB
agents/openai.yamlconfig607 B
assets/base.cssother11.7 KB
assets/samples/data_arras.jsonconfig7.4 KB
assets/samples/data_arras_fn.jsonconfig7.0 KB
assets/samples/data_colab.jsonconfig1.4 KB
assets/samples/data_colab_campos.jsonconfig1.7 KB
assets/samples/data_encargo.jsonconfig4.2 KB
assets/samples/data_example.jsonconfig1.1 KB
assets/samples/data_kyc.jsonconfig1.1 KB
assets/samples/data_kyc_vendedor.jsonconfig1.4 KB
assets/samples/data_llaves.jsonconfig1.8 KB
assets/samples/data_reserva.jsonconfig4.2 KB
assets/samples/documents.jsonconfig2.8 KB
assets/samples/signers_arras.jsonconfig419 B
assets/samples/signers_colab.jsonconfig241 B
assets/samples/signers_encargo.jsonconfig225 B
assets/samples/signers_example.jsonconfig159 B
assets/samples/signers_kyc.jsonconfig106 B
assets/samples/signers_kyc_vendedor.jsonconfig108 B
assets/samples/signers_llaves.jsonconfig226 B
assets/samples/signers_reserva.jsonconfig322 B
assets/templates/01_encargo.guide.mdmarkdown13.8 KB
assets/templates/01_encargo.htmlother25.6 KB
assets/templates/02_kyc.guide.mdmarkdown11.1 KB
assets/templates/02_kyc_comprador.htmlother21.0 KB
assets/templates/02_kyc_vendedor.htmlother21.8 KB
assets/templates/03_reserva.guide.mdmarkdown8.8 KB
assets/templates/03_reserva.htmlother22.9 KB
assets/templates/04_arras.guide.mdmarkdown13.6 KB
assets/templates/04_arras.htmlother27.9 KB
assets/templates/05_colaboracion.guide.mdmarkdown7.6 KB
assets/templates/05_colaboracion.htmlother13.2 KB
assets/templates/06_llaves.guide.mdmarkdown5.7 KB
assets/templates/06_llaves.htmlother11.0 KB
assets/templates/EXAMPLE_receipt.guide.mdmarkdown3.1 KB
assets/templates/EXAMPLE_receipt.htmlother5.8 KB
assets/welcome.txtmarkdown600 B
references/attachments.mdmarkdown3.1 KB
references/controls.jsonconfig16.8 KB
references/first-run.mdmarkdown7.0 KB
references/formify-errors.mdmarkdown1.5 KB
references/formify.mdmarkdown13.2 KB
references/id-scan.mdmarkdown4.0 KB
references/kyc-pattern.mdmarkdown4.3 KB
references/memory.mdmarkdown4.9 KB
references/own-templates.mdmarkdown3.4 KB
references/regions-encargo.mdmarkdown6.0 KB
references/regions-table.mdmarkdown10.7 KB
references/regions.mdmarkdown1.4 KB
references/sample-pack.mdmarkdown3.3 KB
references/signatures.mdmarkdown11.5 KB
references/style-bilingual.mdmarkdown11.3 KB
references/style-drafting.mdmarkdown9.1 KB
references/style-structure.mdmarkdown5.9 KB
references/style.jsonconfig3.4 KB
references/style.mdmarkdown2.2 KB
references/templates-links.mdmarkdown4.7 KB
references/terms.mdmarkdown7.2 KB
references/tink-attributes.mdmarkdown9.0 KB
references/withdrawal.mdmarkdown9.8 KB
scripts/check_law.pyscript3.8 KB
scripts/check_style.pyscript5.4 KB
scripts/fill.pyscript7.4 KB
scripts/handover.pyscript5.2 KB
scripts/render_pdf.pyscript29.8 KB
scripts/sample_pack.pyscript3.2 KB
scripts/start.pyscript3.3 KB
scripts/stdlib_pdf.pyscript17.6 KB
scripts/translate.pyscript5.8 KB
segment.jsonconfig2.1 KB

references/kyc-pattern.md

View on GitHub
<!-- generated from core/references/kyc-pattern.md by build_vertical.py; edit the core file, not this copy -->
# The identification (KYC) form pattern: client scans, organisation assesses

Built and tested in the Spanish real-estate vertical (September 2026, buyer and seller forms) with the AML rules of Ley 10/2010 and RD 304/2014; the structure is the same for every profession that must identify clients (estate agents, financial advisers, lawyers, accountants, letting agents). Only the wording, the legal basis in the data-protection text and the risk factors change per country.

## Structure

1. **Box A, identity.** The ID-scan box of `references/id-scan.md`: MRZ-filled fields on the left (135 pt, not required), the scan field on the right (180 × 120 pt, required, so the form cannot be signed without a scan). Directly under the scan image, in the same column: a label "Back", an upload button `document_back_upload|tink-upload-attachment[1]|tink-style-transparent` (75 × 22 pt, class `pdf-field button`) with the instruction "Press the button and photograph the back" beside it, and a read-only file-name field `document_back_name|tink-uploaded-attachmentname[1]` (180 pt) under it; the component takes a photo, not only a file. Below the identity table, full-width rows for what no document contains: address, tax residence, tax number, telephone, e-mail. Nothing else in the right column.
2. **Box B, activity and transaction** (or ownership and transaction for a seller): occupation, purpose, source of funds, financing, acting on own behalf.
3. **Box C, politically exposed person**: the question and yes/no boxes as the client's declaration.
4. **Optional blocks**: representative (with the represented party's identity document and the power of attorney as upload rows), legal person (directors, beneficial owners).
5. **Declarations** and the client's signature. The declarations say what the client declares and how the organisation processes and keeps the data. They never say how the organisation verifies identity, and never mention video, liveness or any remote procedure.
6. **Box D, verification and assessment by the organisation**, on its own page after the signature (`h2.new-page`, placed after `<!-- SIGNATURES -->`): filled in by hand by the organisation after the client has signed. Checkboxes (`.checkbox`) and blank cells (`.blank`, `.blank.short`), no PDF fields, no question in the chat, nothing the client fills in. Rows, in this order: status (data collected, identity verified, due diligence assessed); identity verification (in person with the original document, or other procedure with a free-text cell; nothing else); date; document verified and its validity; verified by; representation; beneficial owner; purpose and nature of the relationship; politically exposed person (with one sentence naming a public lookup service, no link, no instruction); risk factors; risk class; source of funds; special examination; decision (accepted, accepted with enhanced measures, declined; approved by, date, signature); follow-up and retention.

## Rules

- Signing method for the client on an identification form: `face_liveness` (ID scan plus video selfie in the signing flow), preselected in `signeeDetails` without asking, whatever the memory default is; `digital_ink` only when the account lacks `signatureFaceLiveness`, said in one sentence (David, 2026-09-10). This is a setting of the Formify invitation, not text in the form: rule above still holds, the document never mentions it.
- The scan and the back photo are the evidence the client supplies; the verification is the organisation's. The form and the chat never say how the organisation must verify, which remote procedures count, or that the electronic signature is a verification. The organisation decides (David, 2026-09-09).
- Box D is the organisation's record: it makes the form show which measures were relevant and that a decision was taken. Most rows stay empty for a low-risk private client; that is the point.
- No hyperlinks anywhere in the PDF (David, 2026-09-09). A lookup service is named in plain text at most.
- Fields in box A stay inside their cells (opaque); the right column holds the scan, the back-photo row and the file-name field only, so that everything fits beside ten rows on the left.
- Sample pack: every field empty; the user sees the scan button and the back-photo button on a phone.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall