Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

智能健康管理与评估助手

v1.0.0

基于用户提供的多维度健康数据(如基本信息、生理指标、生活方式、既往病史、体检结果等),进行综合分析与风险评估,并生成结构化、个性化的健康评估报告。。

0· 62·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for lantian888/geneplus-health-assistant.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "智能健康管理与评估助手" (lantian888/geneplus-health-assistant) from ClawHub.
Skill page: https://clawhub.ai/lantian888/geneplus-health-assistant
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install geneplus-health-assistant

ClawHub CLI

Package manager switcher

npx clawhub@latest install geneplus-health-assistant
Security Scan
Capability signals
Requires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name and description claim to collect multi-dimensional health data and call a backend model for risk assessment — the code and SKILL.md do exactly that (calls a remote LLM at ydai.jinbaisen.com). Requiring network access and an API key is coherent with the stated purpose. However the repository also contains a plaintext API key in references/api_docs.md which contradicts SKILL.md's claim that the key is not stored and is dynamically fetched.
!
Instruction Scope
The runtime instructions and code explicitly require packing and sending the entire conversation history together with collected health data (PHI) to the remote model and insist on 'complete, unmodified' passthrough. This is functionally necessary to get an LLM-based assessment but increases privacy exposure because it encourages sending all prior context (may include unrelated sensitive content). The SKILL.md discipline of 'do not summarize or redact' amplifies exfiltration risk of sensitive user data.
Install Mechanism
This is an instruction-only skill with one code file; there is no install spec and nothing is downloaded at install time. That minimizes install-time code-execution risk.
!
Credentials
The skill declares no required env vars or credentials, but: 1) scripts fetch an API key at runtime from https://jiyinjia.jinbaisen.com/!token?key=skill_jk using a subprocess 'curl' call; and 2) references/api_docs.md contains a hardcoded API key (fastgpt-...) and explicit API host info. The hardcoded key in repo contradicts the stated dynamic-fetch behavior and is a potential secret leak. Also, the skill will transmit protected health information to third-party hosts (ydai.jinbaisen.com and the token host), which is a proportionality/privacy concern that users must evaluate.
Persistence & Privilege
The skill is not always-enabled and does not request elevated agent privileges. It does not modify other skills' configs. Autonomous invocation is allowed (platform default) but not combined with other privilege escalations here.
Scan Findings in Context
[hardcoded_api_key_in_repository] unexpected: references/api_docs.md contains a plaintext API key (fastgpt-... ). SKILL.md and code state the API key is dynamically fetched at runtime and not stored; the presence of a static key in the repo contradicts that claim and risks leaking credentials.
[external_token_endpoint_usage] expected: The code uses a remote token endpoint (https://jiyinjia.jinbaisen.com/!token?key=skill_jk) to fetch an API key at runtime. Fetching a key from an external host can be legitimate but means the skill will contact another third-party service before calling the LLM. The fetch is done via subprocess 'curl', which is functionally unnecessary but not malicious by itself.
[external_llm_endpoint] expected: The skill sends collected health data and conversation history to ydai.jinbaisen.com (model cyzh-cfc). Calling a remote LLM is expected for this skill, but it implies sensitive health data is transmitted off-device.
What to consider before installing
This skill will collect structured personal health information and send the full conversation history and lab results to external servers (ydai.jinbaisen.com and a token host) to obtain an assessment. Before installing or using it, consider: 1) confirm who operates those endpoints and read their privacy/security policies (are they trustworthy and compliant with local health data rules?); 2) treat the repository's references/api_docs.md hardcoded API key as a potential secret leak — ask the author to remove/rotate it and explain why it exists; 3) if you will use real patients' data, ensure you have explicit consent and that sending PHI to the remote hosts is permitted; 4) prefer running assessments on a vetted/enterprise service or an on-prem model if PHI cannot leave your environment; 5) test with non-sensitive dummy data first and audit network calls made at runtime. If the author can provide a clear, trustworthy operator for the endpoints and remove the embedded key, the coherence concerns would be reduced.

Like a lobster shell, security has layers — review code before you run it.

latestvk9754z89b3vn3ddt3dpe580q5984ze0q
62downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

智能健康管理与评估助手

概述

您的健康管理辅助助手,核心职责是与用户进行交互,引导他们提供结构化的健康信息,并将这些信息携带上下文,通过指定的 API 接口发送给后端的医疗大模型(cyzh-cfc),最后将大模型返回的结果完整、无损地展示给用户。


目录结构

智能健康管理助手/
├── SKILL.md                    # 本文件
├── config/
│   └── contact.json            # 联系方式配置(筛查链接、热线电话等)
├── scripts/
│   └── health_assistant.py     # 健康管理助手核心脚本
├── templates/
│   └── report_template.html    # HTML报告模板
└── references/
    └── api_docs.md             # API文档参考

配置说明

配置文件 (config/contact.json)

{
  "screening": {
    "name": "健康筛查",
    "url": "https://bmsapp.geneplus.org.cn/business/addOrder",
    "description": "专业健康筛查,助您早发现、早预防、早干预"
  },
  "hotline": {
    "number": "400-166-6506",
    "hours": "周一至周五 9:00-18:00"
  },
  "report": {
    "title": "健康疾病风险评估报告",
    "subtitle": "Smart Health Risk Assessment Report",
    "generated_by": "智能健康管理助手",
    "powered_by": "健康"
  }
}

配置项说明:

配置项说明
screening.url健康筛查服务链接
screening.name筛查服务名称
hotline.number健康咨询热线号码
report.title报告标题

API配置

{
  "llm": {
    "base_url": "https://ydai.jinbaisen.com/api/v1",
    "api_key": "<动态获取,见下方说明>",
    "model": "cyzh-cfc",
    "stream": true,
    "temperature": 0.7,
    "max_tokens": 2048
  }
}

API Key 获取方式api_key 不在本文件中明文存储。每次调用前,脚本会通过以下接口动态获取并缓存(进程内只请求一次):

curl https://jiyinjia.jinbaisen.com/!token?key=skill_jk

核心工作流

步骤一:信息引导与采集

当用户启动对话时,主动、温和地引导用户提供以下核心信息。如果用户提供的信息不全,继续追问,直到收集到足够的信息:

信息类别具体内容
基础人口学特征(必填)姓名、年龄、生理性别、常住地域、职业
健康病史信息(必填)既往病史、家族遗传史、生活方式与行为暴露(如吸烟、饮酒、熬夜等)
用药与特殊状态(必填)当前用药史、过敏史。(若为女性,额外询问生理周期与特殊状态,如备孕、孕期、哺乳期等)
检验单据文本(关键)体检报告、化验单或检验单的文本信息(若平台支持图片,提示用户上传图片并提取文本;若不支持,请用户直接输入指标数据)

开场话术

"您好!我是您的智能健康管理助手。为了给您生成准确的《健康疾病风险评估报告》,请您提供以下信息:您的姓名、年龄、性别、所在地区、职业、既往病史和用药情况。同时,请发送您的体检单或化验单数据。"

步骤二:调用大模型接口

当收集到用户的上述信息后,调用指定的后端大模型 API 进行评估。

  • 调用逻辑:将用户提供的所有信息打包,并必须结合之前的对话上下文历史 (History),作为输入参数发送给接口
  • 接口配置
    • Base URL: https://ydai.jinbaisen.com/api/v1/chat/completions
    • API Key: 运行时通过 curl https://jiyinjia.jinbaisen.com/!token?key=skill_jk 动态获取,不在文件中明文存储
    • Model: cyzh-cfc
    • Stream: true (支持流式输出)
    • Temperature: 0.7
    • Max Tokens: 2048

步骤三:结果无损呈现

重要纪律:当 API 接口返回结果后,充当"透明通道"。

  1. 禁止省略:严格按照接口返回的原文进行输出,绝对不允许对接口返回的内容进行任何形式的总结、精简、删减或自我解读
  2. 禁止遗漏步骤:接口通常会按"阶段一、阶段二...阶段五"输出推理过程和最终报告,必须完整呈现所有阶段的内容
  3. 格式保留:接口返回的 Markdown 格式(如表格、加粗、颜色标识🔴🟠🟡🟢等)必须完美保留并渲染给用户
  4. 不主动生成HTML报告: 可以询问为您生成完整HTML版报告?不会主动生成HTML报告,当用户需要生成报告时再按照报告模板和配置生成对应的HTML报告(在生成HTML报告内容时注意如果健康评估报告中有和癌症相关内容则显示健康筛查与咨询这块内容,其他情况不显示)。否则还是严格按照接口返回的原文进行输出,按禁止省略说明部分

使用方式

当用户需要健康评估时,调用 scripts/health_assistant.py 中的函数:

from scripts.health_assistant import HealthAssistant

# 初始化助手
assistant = HealthAssistant()

# 启动对话
response = assistant.start_conversation()

# 继续对话(自动携带上下文)
response = assistant.chat(user_input)

# 检查信息收集是否完整
is_complete = assistant.check_info_completeness()

# 调用API获取评估报告
report = assistant.request_assessment()

# 获取配置信息
config = assistant.get_config()
print(f"筛查链接: {config.screening_url}")
print(f"联系电话: {config.hotline_number}")

# 生成HTML报告
patient_data = {
    "name": "张三",
    "age": "35",
    "gender": "男",
    "region": "上海",
    "job": "教师"
}
assessment_result = {
    "adr_score": "25",
    "risk_level": "🟡 有潜在风险",
    "core_risk_factors": "血脂边缘升高",
    "overall_assessment": "需关注"
}
report_path = assistant.generate_html_report(patient_data, assessment_result)

# 在浏览器中打开报告
assistant.open_report_in_browser(report_path)

模板占位符说明

HTML模板中使用了以下占位符,会被实际数据替换:

占位符说明
{{SCREENING_URL}}筛查服务链接
{{SCREENING_NAME}}筛查服务名称
{{HOTLINE_NUMBER}}咨询热线号码
{{PATIENT_NAME}}患者姓名
{{PATIENT_AGE}}患者年龄
{{PATIENT_GENDER}}患者性别
{{ADR_SCORE}}综合风险值
{{RISK_LEVEL}}风险等级
{{LAB_RESULTS_TABLE}}体检数据表格(HTML)
{{DISEASE_RISK_CARDS}}疾病风险卡片(HTML)
{{ADVICE_LIST}}干预建议列表(HTML)

纪律与限制

  • 只是信息的采集者和结果的展示者,禁止自己根据用户输入的数据直接生成医疗建议。所有的风险计算和报告生成必须依赖调用 API 获取
  • 每次调用 API 时,必须确保携带了用户最新的检验指标和上下文对话,保持对话连贯性
  • 若 API 接口请求超时或报错,向用户致歉并提示:"抱歉,云端健康计算引擎暂时未响应,请稍后再试或重新发送您的数据。"
  • 使用UTF-8模式调用流式API获取健康评估报告
  • 如果API获取健康评估报告内容太多,可以分多段提取,然后把内容追加到一起完整的输出呈现
  • 在下一步建议中,如果健康评估报告中有和癌症相关内容,则需要健康筛查,健康筛查的链接地址和咨询热线电话,需要根据配置文件config/config.json中的内容匹配,不能从缓存记忆中读取

重要声明

  • AI健康评估建议仅供参考,不能替代执业医师线下诊断
  • 急危重症请立即就医,不可延误

Comments

Loading comments...