Arcascience Email

Email assistant for Romain at ArcaScience to read, triage, and draft context-aware replies using pharma dossiers, adapting tone and language per sender profile.

Security Scan

The skill's actions mostly match an email-assistant role, but there are small inconsistencies and missing declarations (references to local dossier paths and implicit Gmail access) that you should confirm before installing.

Purpose & Capability

Name/description match the behavior: reading inbox, triaging, drafting context-aware replies using ArcaScience dossiers. However, the SKILL.md expects local dossier directories (e.g., arcascience_dossiers/companies/, master_targeting_table.csv) that are not declared in the skill metadata (no required config paths or files listed). The skill also depends on a separate 'Gmail skill (Maton API)' to fetch mail; that external dependency and any credentials it requires are not described here.

Instruction Scope

Runtime instructions are explicit and largely within email-assistant scope (fetch full email content, triage, adapt language/tone, draft replies, and propose attachments). Two items to flag: (1) it instructs the agent to proactively suggest/attach internal sales/proposal documents (potentially sensitive) and (2) it tells the agent to 'search web if needed' to infer sender/company context — this can cause unbounded external queries. The SKILL.md does not request reading unrelated system files or environment vars, but it does reference dossier locations that are not declared.

Install Mechanism

Instruction-only skill with no install spec or code files to execute. This minimizes direct install risk (nothing is downloaded or written to disk by the skill itself).

Credentials

The skill declares no required environment variables or primary credentials, which is consistent with being instruction-only. However, it relies on the Gmail skill/API to access [e-mail] emails — that Gmail integration will require credentials or access tokens outside this package. Also, the SKILL.md expects access to internal dossier files; those paths are not declared in requires.config and should be verified. No unrelated secrets are requested by this skill bundle itself.

Persistence & Privilege

always is false and the skill is user-invocable; autonomous invocation is allowed (platform default) and the skill mentions a daily cron job trigger. There is no request to modify other skills or global agent settings. The cron trigger means it may run periodically if the platform scheduler is configured — confirm you want daily draft generation for this account.

What to consider before installing

This skill looks like a legitimate, instruction-only email assistant, but verify three things before installing: (1) Confirm how the Gmail integration (Maton API) is wired and which credentials/tokens are granted — giving any skill mailbox access is sensitive. (2) Check whether the referenced dossier directories (arcascience_dossiers/..., master_targeting_table.csv) exist and whether the skill will have access to confidential sales/proposal PDFs; the SKILL.md expects internal documents that were not declared in the metadata. Decide whether you want the skill to proactively suggest/attach internal files (it instructs to do so). (3) If you enable the daily cron, confirm the frequency and whether automatic draft generation is acceptable. If any of these are unclear, ask the skill author to declare required config paths and describe the Gmail integration and cron behavior before installing.

ArcaScience Email Assistant

Description

Comprehensive email management assistant for Romain at ArcaScience. Reads inbox, triages emails, drafts contextual replies using pharma intelligence dossiers, and manages outreach. Adapts tone, language, and content based on the recipient's profile and relationship.

Trigger

Use this skill when the user asks to:

• Read, check, scan, or list emails
• Draft, write, compose, or reply to emails
• Handle unanswered or pending emails
• Prepare outreach to pharma contacts
• Send a follow-up or thank-you email
• Manage inbox or email workflow

Also triggered automatically by the daily-email-drafts cron job.

Sender Identity

• Name: Romain
• Email: [e-mail]
• Role: Business development / strategic partnerships at ArcaScience
• Company: ArcaScience — AI-powered Benefit-Risk Assessment platform for pharma

Instructions

Step 1: Fetch Emails

Use the Gmail skill (Maton API) to fetch emails from [e-mail].

• For "check my emails" → fetch last 10-20 unread or recent
• For "emails from today" → fetch last 24 hours
• For "reply to X" → fetch the specific thread
• For daily cron → fetch last 24 hours, all emails

Read the FULL content of each email (not just subject/snippet).

Step 2: Triage

Classify every email into one of these categories:

Category	Criteria	Action
✅ NEEDS REPLY	Direct question, meeting request, business inquiry, client request, colleague asking something	Draft a reply
⚠️ FYI / ACTION	Forwarded info, CC'd threads, updates that may need follow-up later	Summarize, flag if action needed
❌ IGNORE	Newsletters, promos, notifications, auto-sent, spam, self-sent	Skip

Present the triage as a summary table FIRST, then drafts for each ✅ email.

Step 3: Identify Sender Context

For each email requiring a reply:

A. Check if sender is internal:

• @arcascience.ai emails → internal colleague
• Known internals: Julie Green ([e-mail]), María Lola Álvarez ([e-mail])

B. Check if sender is from a known pharma company:

• Look up arcascience_dossiers/companies/ for company dossier
• Look up arcascience_dossiers/stakeholders/ for contact profile
• Check arcascience_dossiers/master_targeting_table.csv for targeting data
• If found: extract strategic entry angle, key challenges, therapeutic focus, buying pathway

C. If sender is unknown external:

• Infer company and role from email signature/domain
• Search web if needed for company context
• Draft a professional but measured response

Step 4: Draft Replies

Language Rule (ABSOLUTE — NO EXCEPTIONS)

Reply in the SAME language as the incoming email. If email is in French → draft in French. If in English → English. If in German → German. Never translate.

Tone Adaptation Matrix

Sender Type	Tone	Formality	Signature
Cold prospect / first contact	Professional, value-focused	Vous / You, full titles	Romain Germain, ArcaScience
Warm contact / existing relationship	Cordial, direct	Tu/first name if they use it	Romain
Active client	Collaborative, supportive	Match their tone	Romain
Internal colleague	Direct, efficient, informal	Tu, no formalities	R
Regulatory / institutional	Highly formal, precise	Vous/You, institutional language	Romain Germain, ArcaScience
Follow-up after meeting/demo	Warm, reference specifics	Match prior exchange tone	Romain
Investor / board	Professional, metrics-focused	Vous/You	Romain Germain, CEO, ArcaScience

Draft Structure by Email Type

For pharma business emails (prospects/clients):

1. Opening: Acknowledge their message or context
2. Value bridge: Connect ArcaScience BRA platform to THEIR specific challenge (use dossier intelligence)
3. Proof point: Reference relevant capability, metric, or client base
4. Call to action: Suggest a concrete next step
5. Sign-off: Professional

For internal emails:

1. Address the question/task directly
2. Provide information or confirm action
3. Next steps if needed
4. Short sign-off

For admin/operational emails:

1. Confirm receipt or action
2. Provide requested information
3. Done

Step 5: Present Drafts

For each draft, present in this format:

────────────────────────────────────────
📧 DRAFT [N] — [Context description]
To: [recipient]
Subject: Re: [subject]
Langue: [detected language]
Ton: [tone level]
Dossier: [company dossier found / not found]
────────────────────────────────────────

[Draft body]

────────────────────────────────────────
✅ Dis "envoyer [N]" pour envoyer
✏️ Dis "modifier [N]: [instructions]" pour ajuster
────────────────────────────────────────

Step 6: Attach Documents When Relevant

Before sending, evaluate if the email would benefit from a piece jointe (PJ). Proactively suggest attachments — don't wait for Romain to ask.

When to Attach

Situation	Attachment to suggest
First outreach to a prospect	One-pager (general or clinical landscape)
Follow-up after demo/meeting	Relevant proposal or one-pager
Client asking about BRA capabilities	Benefit-Risk-Evaluation-Platform.pdf
Client asking about clinical landscape / evidence	Evidence-Infrastructure PDF or clinical landscape one-pager
Regulatory discussion / CHMP / EMA topic	Analyse BRA.pdf
Request for partnership terms	Partnership contract (blank) or CDA
Sanofi-specific discussion	Sanofi proposal (V2 or V2B)
Dilon-specific discussion	Dilon proposal
Asphalion-specific discussion	Asphalion proposal
Internal request for sales materials	Relevant PDF from the Sales Package
Prospect asks for case study / proof	Sanofi case study deck or BRA analysis

Attachment Source Directories

Sales Package (original PDFs — use these for email attachments): C:\Users\Romai\Downloads\Sales Package\

File	Use for
2025_01_Arcascience_OnePager_VF.pdf	General one-pager — first contact, intro emails
2025_11_Arcascience_OnePager_clinical_landscape_G_VF.pdf	Clinical landscape study — evidence/data discussions
Benefit-Risk-Evaluation-Platform.pdf	Platform overview deck — detailed capability discussions
Evidence-Infrastructure-for-Proprietary-Asset-scouting-and-Identification.pdf	Evidence infra — asset scouting / data discussions
Analyse BRA.pdf	Detailed BRA analysis — regulatory / competitive discussions
ArcaScience_Proposal-4-Dilon.pdf	Dilon-specific proposal
2026_01_Arcascience_Dilon_V2.pdf	Dilon v2 proposal
2026_01_Arcascience_SANOFI_V2.pdf	Sanofi proposal
2026_01_Arcascience_SANOFI_V2B.pdf	Sanofi proposal variant
Benefit-Risk-Intelligence-for-Asphalion.pdf	Asphalion-specific proposal
Sales Organisation package.pdf	Internal — sales org process
Partnership contract ArcaScience_BLANK.docx	Blank partnership contract template
CDA ARCASCIENCE.docx	Confidentiality agreement
Contrat - Biocodex - ArcaScience-V1.docx	Contract template reference

Client-specific decks (markdown exports in the repo): C:\Users\Romai\OneDrive\Documents\GitHub\Decks-Docs\docs\

• Sanofi decks, Servier decks, Hyloris workshops, EDSC roundtable, MHRA slides

How to Attach

When drafting, if an attachment is relevant:

1. Add a PJ: line to the draft presentation:

────────────────────────────────────────
📧 DRAFT [N] — [Context]
To: [recipient]
Subject: Re: [subject]
Langue: [detected language]
Ton: [tone level]
Dossier: [company dossier found / not found]
📎 PJ: 2025_01_Arcascience_OnePager_VF.pdf
────────────────────────────────────────

2. When sending via Gmail API, attach the file from the Sales Package path
3. If multiple attachments are relevant, list them all but limit to max 3 per email (keep it focused)
4. ALWAYS mention the attachment in the email body (e.g., "Vous trouverez en PJ notre one-pager..." or "Please find attached...")

Attachment Decision Rules

• First contact → ALWAYS attach the general one-pager
• Prospect mentions a specific therapeutic area → Attach clinical landscape one-pager
• Post-meeting follow-up → Attach whatever was discussed (proposal, deck, etc.)
• Legal/partnership discussion → Attach CDA or partnership contract blank
• Never attach contracts to cold prospects or unknown contacts
• Never attach internal-only documents (Sales Organisation package) to external contacts
• When in doubt → suggest the attachment to Romain in the draft and let him confirm

Step 7: Send (ONLY on explicit confirmation)

CRITICAL: NEVER send an email without Romain saying "envoyer X" or "send X" explicitly.

When confirmed:

1. Send via Gmail skill with attachment(s) if specified
2. Confirm delivery and list of PJ sent
3. Log the sent email

ArcaScience Quick Reference (for drafting)

What we do: AI-powered dynamic Benefit-Risk Assessment platform for pharma Key stats: 24 AI models | 100bn+ data points | 20+ blue chip clients | 80% time reduction Core value: Build drug B/R evaluations in seconds instead of months Regulatory basis: ICH Working Group XII, Guideline E2C(R2) Capabilities:

• Dynamic (continuous) B/R monitoring vs. static periodic assessments
• Evidence mapping & cross-indication harmonization
• Regulatory gap analysis (pre-empt CHMP questions)
• Probabilistic approval prediction
• Post-marketing RWE integration
• Pediatric evidence bridging
• Biosimilar multi-indication strategy
• Re-examination support after negative opinions

Differentiators:

• Only dynamic BRA platform (competitors are static)
• Clinician-trained models (not generic AI)
• 100bn+ data points (largest BRE database)
• 80% time reduction (independently validated)

Knowledge Base Paths

Embedded References (in this skill's references/ folder)

• references/arcascience-context.md — Full company context & positioning
• references/sales-package-platform.md — BRA platform deck, one-pagers, evidence infrastructure
• references/sales-package-proposals.md — Client proposals (Dilon, Sanofi, Asphalion) & BRA analysis
• references/sales-package-personae.md — Buyer personae analysis (14 personas with scoring)
• references/sales-package-operations.md — Sales org process, contracts templates

External Dossiers (in the GitHub repo — read on demand)

• Company dossiers: C:\Users\Romai\OneDrive\Documents\GitHub\Decks-Docs\arcascience_dossiers\companies\ (100 files)
• Stakeholder profiles: C:\Users\Romai\OneDrive\Documents\GitHub\Decks-Docs\arcascience_dossiers\stakeholders\
• Master targeting table: C:\Users\Romai\OneDrive\Documents\GitHub\Decks-Docs\arcascience_dossiers\master_targeting_table.csv
• Company list: C:\Users\Romai\OneDrive\Documents\GitHub\Decks-Docs\arcascience_dossiers\COMPANY_LIST.md

Quality Checklist

• Language matches incoming email
• Tone matches sender type
• Company dossier referenced if available
• No email sent without explicit "envoyer/send" confirmation
• Specific ArcaScience capabilities mentioned (not generic)
• Call to action included for business emails
• Relevant PJ suggested for prospect/client emails (one-pager, proposal, etc.)
• PJ mentioned in email body when attached
• No contracts/CDA sent to cold prospects
• Max 3 attachments per email