Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计提醒

arcascience-email阿卡科学电子邮件

Agent Skill

arcascience-email 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

3,057

周安装

116

GitHub Stars

公开资料未说明

下载量

947
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:arcascience-email(阿卡科学电子邮件)
来源仓库:https://github.com/atomus42/arcascience-email
安装命令:
openclaw skills install arcascience-email
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install arcascience-email

简介

ArcaScience 的 Romain 的电子邮件助理可使用药品档案来阅读、分类和起草上下文感知回复,并根据发件人资料调整语气和语言。

SKILL.md

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: romain@arcascience.ai
  • 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 romain@arcascience.ai.

  • 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:

CategoryCriteriaAction
✅ NEEDS REPLYDirect question, meeting request, business inquiry, client request, colleague asking somethingDraft a reply
⚠️ FYI / ACTIONForwarded info, CC'd threads, updates that may need follow-up laterSummarize, flag if action needed
❌ IGNORENewsletters, promos, notifications, auto-sent, spam, self-sentSkip

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 (julie@arcascience.ai), María Lola Álvarez (marialola@arcascience.ai)

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 TypeToneFormalitySignature
Cold prospect / first contactProfessional, value-focusedVous / You, full titlesRomain Germain, ArcaScience
Warm contact / existing relationshipCordial, directTu/first name if they use itRomain
Active clientCollaborative, supportiveMatch their toneRomain
Internal colleagueDirect, efficient, informalTu, no formalitiesR
Regulatory / institutionalHighly formal, preciseVous/You, institutional languageRomain Germain, ArcaScience
Follow-up after meeting/demoWarm, reference specificsMatch prior exchange toneRomain
Investor / boardProfessional, metrics-focusedVous/YouRomain 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

SituationAttachment to suggest
First outreach to a prospectOne-pager (general or clinical landscape)
Follow-up after demo/meetingRelevant proposal or one-pager
Client asking about BRA capabilitiesBenefit-Risk-Evaluation-Platform.pdf
Client asking about clinical landscape / evidenceEvidence-Infrastructure PDF or clinical landscape one-pager
Regulatory discussion / CHMP / EMA topicAnalyse BRA.pdf
Request for partnership termsPartnership contract (blank) or CDA
Sanofi-specific discussionSanofi proposal (V2 or V2B)
Dilon-specific discussionDilon proposal
Asphalion-specific discussionAsphalion proposal
Internal request for sales materialsRelevant PDF from the Sales Package
Prospect asks for case study / proofSanofi case study deck or BRA analysis

Attachment Source Directories

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

FileUse for
2025_01_Arcascience_OnePager_VF.pdfGeneral one-pager — first contact, intro emails
2025_11_Arcascience_OnePager_clinical_landscape_G_VF.pdfClinical landscape study — evidence/data discussions
Benefit-Risk-Evaluation-Platform.pdfPlatform overview deck — detailed capability discussions
Evidence-Infrastructure-for-Proprietary-Asset-scouting-and-Identification.pdfEvidence infra — asset scouting / data discussions
Analyse BRA.pdfDetailed BRA analysis — regulatory / competitive discussions
ArcaScience_Proposal-4-Dilon.pdfDilon-specific proposal
2026_01_Arcascience_Dilon_V2.pdfDilon v2 proposal
2026_01_Arcascience_SANOFI_V2.pdfSanofi proposal
2026_01_Arcascience_SANOFI_V2B.pdfSanofi proposal variant
Benefit-Risk-Intelligence-for-Asphalion.pdfAsphalion-specific proposal
Sales Organisation package.pdfInternal — sales org process
Partnership contract ArcaScience_BLANK.docxBlank partnership contract template
CDA ARCASCIENCE.docxConfidentiality agreement
Contrat - Biocodex - ArcaScience-V1.docxContract 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
────────────────────────────────────────
  1. When sending via Gmail API, attach the file from the Sales Package path
  2. If multiple attachments are relevant, list them all but limit to max 3 per email (keep it focused)
  3. 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

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

81.76%
按下载量换算774

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills