# Draft Markup Of Cross > Cross-border data transfer agreement markups for clinical trial data fail when the agent applies generic negotiation positions rather than integrating the organisation's playbook, the applicable commercial agreement context, the due-diligence summary, and the internal email escalation positions into a coherent redline. - Skill: `finchipaiorg/draft-markup-of-cross` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/draft-markup-of-cross` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/draft-markup-of-cross/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/draft-markup-of-cross --- # Skill: Draft Markup of Cross-Border Data Transfer Agreement for Clinical Trial Data Processing ## 1. Subject-matter triage - Read the playbook before touching the draft so mandatory positions are separated from preferred and fallback positions. - Confirm the transfer mechanism, the data category, and whether the draft is for clinical-trial processing of sensitive personal data. - Identify the governing commercial agreement terms that constrain the DTA, especially liability, governing law, and dispute resolution. - Read the due-diligence summary and internal email chain before marking up any clause so the redline reflects risk posture and pre-agreed positions. - If multiple source documents or counterparties are in play, enumerate them first and treat each separately rather than blending them into one generic pass. ## 2. Failure modes the skill is correcting - Redlining the DTA without first mapping each clause to the playbook hierarchy, which causes mandatory protections to be weakened and negotiable items to be over-litigated. - Marking up provisions in a way that conflicts with the underlying commercial agreement, especially on liability allocation, governing law, or dispute resolution. - Ignoring the due-diligence record and internal email guidance, which leads to proposals that miss known compliance gaps or disregard approved negotiation boundaries. - Returning a markup without margin comments, making the document unusable as a standalone negotiation tool. - Relying only on visual tracked changes that may not survive export, leaving the operative edits ambiguous. ## 3. Legal frameworks / domain conventions that apply - Cross-border transfer rules for sensitive personal data require the agreement to track the applicable transfer mechanism and any required contractual safeguards for the relationship at issue. - Clinical trial data processing may be subject to life-sciences regulatory requirements and health-authority expectations; the drafting must stay consistent with the trial’s approvals and operational protocol. - The playbook controls drafting authority: mandatory positions are non-negotiable, preferred positions should be pushed, and fallback positions are the last acceptable concession. - The commercial agreement remains the governing relationship document, so the DTA must not introduce inconsistent allocation of risk or inconsistent forum language. - Margin comments should state the basis for the edit, whether the position is mandatory or preferred, and the escalation point if the counterparty resists. - For any legal proposition relied on, cite the controlling authority named in the source materials or the generally recognized authority for the topic; do not state a legal conclusion without naming the rule or source that supports it. ## 4. Analytical scaffolds - Start with the playbook and convert each relevant provision into a drafting posture: keep, tighten, soften, or escalate. - Read the commercial agreement excerpts next and align the DTA to any pre-existing governing law, liability, confidentiality, indemnity, or dispute-resolution framework. - Use the due-diligence summary to identify whether any clause needs heightened protection, narrower access, stronger audit rights, or additional operational controls. - Use the internal email chain to preserve approved negotiation limits, business sensitivities, and escalation triggers. - Work clause by clause through the proposed agreement: - compare the clause to the playbook position, - compare it to the commercial agreement, - compare it to the diligence findings, - then decide whether to redline, retain, or escalate. - For each substantive edit, include a plain-text redline marker so the change is visible even outside Word formatting: - [DELETED: …] - [INSERTED: …] - [REPLACED: old → new] - [Rationale: …] - Treat every substantive issue as a completed unit: state its severity, identify the interacting clause or document, and explain the client consequence. - When more than one clause type or issue category is present, keep them separate rather than collapsing them into one blended comment. - End the advisory analysis with concrete next steps tied to the right internal owner and timing. ## 5. Vertical / structural / temporal relationships - The commercial agreement governs the relationship; the DTA must conform to it rather than revising it by implication. - Mandatory playbook positions override counterparty preference and internal convenience. - Preferred positions may be waived only with the appropriate escalation authority. - Diligence findings can justify strengthening protections, but they do not override mandatory commercial constraints. - If the draft contemplates approvals, notice periods, audit windows, incident response, or deletion timelines, check each against the operational sequence and any upstream approval chain before finalizing. - Where obligations depend on a trigger, link the trigger, response window, and downstream consequence in the markup or comment. ## 6. Output structure conventions - Produce the redlined DTA first; the cover memo comes only after the redline file exists and contains operative edits. - Use robust textual change markers in the document itself so the markup remains intelligible if exported or flattened. - Include margin comments on each substantive change; keep them concise but complete. - For comments and memo entries, use a uniform severity scale such as Critical / High / Medium / Low and apply it consistently. - The cover memo should read like a negotiation summary, not a restatement of the draft: identify the most important issues, the drafting decisions made, the items needing client instruction, and the items requiring escalation. - Each memo recommendation should use an imperative verb, name the responsible role, and include a timing anchor tied to the transaction or regulatory process. - Do not use a rigid rubric-shaped section list; use conventional legal memo and markup headings instead. - Confirm before finishing that the redline file is non-empty and that the cover memo is non-empty, each containing operative content rather than a description of the task.