Token导航 LogoToken导航

Agent Skill · 研究检索

nih-biosketch-builder(美国国立卫生研究院生物草图生成器)

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

nih-biosketch-builder 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为调用外部服务;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 28,420。

总安装 3,222周安装 137GitHub Stars 公开资料未说明下载 1,129核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:nih-biosketch-builder(美国国立卫生研究院生物草图生成器)
来源仓库:https://github.com/aipoch-ai/nih-biosketch-builder
安装命令:
openclaw skills install nih-biosketch-builder
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install nih-biosketch-builder

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

生成符合 NIH 标准的生物草图(Biosketch)文档。适合科研人员在 OpenClaw 中快速构建合规的学术履历。通过 openclaw skills install 命令安装并使用。输出格式遵循 2022 年 OMB 批准模板,建议人工复核内容准确性。

nih-biosketch-builder 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install nih-biosketch-builder;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

nih-biosketch-builder 怎么安装?

在终端执行 openclaw skills install nih-biosketch-builder。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

nih-biosketch-builder 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

nih-biosketch-builder 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

nih-biosketch-builder 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

nih-biosketch-builder 用的人多吗?

公开数据是累计安装 3,222 次,近一周安装 137 次,下载 1,129 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

nih-biosketch-builder 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
nih-biosketch-builder

美国国立卫生研究院生物草图生成器 · 本页

3,222—调用外部服务MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
nih-biosketch-builder
description
Generate NIH Biosketch documents compliant with the 2022 OMB-approved.
license
MIT
skill-author
AIPOCH

NIH Biosketch Builder

ID: 101 Version: 1.0.0 NIH Format: 2022 OMB-approved version

When to Use

  • Use this skill when the task is to Generate NIH Biosketch documents compliant with the 2022 OMB-approved.
  • Use this skill for academic writing tasks that require explicit assumptions, bounded scope, and a reproducible output format.
  • Use this skill when you need a documented fallback path for missing inputs, execution errors, or partial evidence.

Key Features

  • Scope-focused workflow aligned to: Generate NIH Biosketch documents compliant with the 2022 OMB-approved.
  • Packaged executable path(s): scripts/main.py.
  • Reference material available in references/ for task-specific guidance.
  • Structured execution path designed to keep outputs consistent and reviewable.

Dependencies

  • Python 3.8+
  • python-docx
  • requests (for PubMed API)

Install dependencies:

pip install python-docx requests

Example Usage

See ## Usage above for related details.

cd "20260318/scientific-skills/Academic Writing/nih-biosketch-builder"
python -m py_compile scripts/main.py
python scripts/main.py --help

Example run plan:

  1. Confirm the user input, output path, and any required config values.
  2. Edit the in-file CONFIG block or documented parameters if the script uses fixed settings.
  3. Run python scripts/main.py with the validated inputs.
  4. Review the generated output and return the final artifact with any assumptions called out.

Implementation Details

See ## Workflow above for related details.

  • Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable.
  • Input controls: confirm the source files, scope limits, output format, and acceptance criteria before running any script.
  • Primary implementation surface: scripts/main.py.
  • Reference guidance: references/ contains supporting rules, prompts, or checklists.
  • Parameters to clarify first: input path, output path, scope filters, thresholds, and any domain-specific constraints.
  • Output discipline: keep results reproducible, identify assumptions explicitly, and avoid undocumented side effects.

Quick Check

Use this command to verify that the packaged script entry point can be parsed before deeper execution.

python -m py_compile scripts/main.py

Audit-Ready Commands

Use these concrete commands for validation. They are intentionally self-contained and avoid placeholder paths.

python -m py_compile scripts/main.py
python scripts/main.py --help

Workflow

  1. Confirm the user objective, required inputs, and non-negotiable constraints before doing detailed work.
  2. Validate that the request matches the documented scope and stop early if the task would require unsupported assumptions.
  3. Use the packaged script path or the documented reasoning path with only the inputs that are actually available.
  4. Return a structured result that separates assumptions, deliverables, risks, and unresolved items.
  5. If execution fails or inputs are incomplete, switch to the fallback path and state exactly what blocked full completion.

Functions

Automatically generate NIH Biosketch documents in the 2022 format for NIH grant applications.

NIH Biosketch Format Requirements (2022 Version)

Required Sections

  1. Personal Statement - Personal statement (max 1 page)
  2. Positions and Honors - Positions and honors
  3. Contributions to Science - Scientific contributions (max 4 items)
  4. Research Support - Research support (optional)

Format Specifications

  • Page count: No more than 5 pages
  • Fonts: Arial, Helvetica, Palatino Linotype, or Georgia, ≥11pt
  • Margins: ≥0.5 inches
  • Line spacing: Single or double

Usage

Command Line

python skills/nih-biosketch-builder/scripts/main.py --input data.json --output biosketch.docx

Input Data Format (JSON)

{
  "personal_info": {
    "name": "Zhang San",
    "position": "Associate Professor",
    "department": "Department of Biology",
    "organization": "University of Example",
    "email": "zhang.san@example.edu"
  },
  "personal_statement": "Your personal statement text here...",
  "positions_and_honors": [
    {"year": "2020-present", "position": "Associate Professor", "institution": "University of Example"}
  ],
  "contributions": [
    {
      "title": "Breakthrough in Cancer Research",
      "description": "Detailed description of contribution...",
      "publications": ["PMID:12345678", "DOI:10.1000/example"]
    }
  ],
  "research_support": [
    {"title": "R01 Grant", "agency": "NIH", "period": "2021-2026", "amount": "$1,500,000"}
  ]
}

SCI Paper Auto-import


# Automatically retrieve paper information via PMID
python skills/nih-biosketch-builder/scripts/main.py --import-pubmed "12345678,23456789" --output publications.json

# Auto-fill into biosketch
python skills/nih-biosketch-builder/scripts/main.py --input data.json --auto-import-pubmed --output biosketch.docx

Output Format

Generate DOCX file in NIH official template format, ready to use for grant applications.

References

Risk Assessment

Risk IndicatorAssessmentLevel
Code ExecutionPython scripts with toolsHigh
Network AccessExternal API callsHigh
File System AccessRead/write dataMedium
Instruction TamperingStandard prompt guidelinesLow
Data ExposureData handled securelyMedium

Security Checklist

  • [ ] No hardcoded credentials or API keys
  • [ ] No unauthorized file system access (../)
  • [ ] Output does not expose sensitive information
  • [ ] Prompt injection protections in place
  • [ ] API requests use HTTPS only
  • [ ] Input validated against allowed patterns
  • [ ] API timeout and retry mechanisms implemented
  • [ ] Output directory restricted to workspace
  • [ ] Script execution in sandboxed environment
  • [ ] Error messages sanitized (no internal paths exposed)
  • [ ] Dependencies audited
  • [ ] No exposure of internal service architecture

Prerequisites

No additional Python packages required.

Evaluation Criteria

Success Metrics

  • [ ] Successfully executes main functionality
  • [ ] Output meets quality standards
  • [ ] Handles edge cases gracefully
  • [ ] Performance is acceptable

Test Cases

  1. Basic Functionality: Standard input → Expected output
  2. Edge Case: Invalid input → Graceful error handling
  3. Performance: Large dataset → Acceptable processing time

Lifecycle Status

  • Current Stage: Draft
  • Next Review Date: 2026-03-06
  • Known Issues: None
  • Planned Improvements:

- Performance optimization - Additional feature support

Output Requirements

Every final response should make these items explicit when they are relevant:

  • Objective or requested deliverable
  • Inputs used and assumptions introduced
  • Workflow or decision path
  • Core result, recommendation, or artifact
  • Constraints, risks, caveats, or validation needs
  • Unresolved items and next-step checks

Error Handling

  • If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
  • If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
  • If scripts/main.py fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
  • Do not fabricate files, citations, data, search results, or execution outcomes.

Input Validation

This skill accepts requests that match the documented purpose of nih-biosketch-builder and include enough context to complete the workflow safely.

Do not continue the workflow when the request is out of scope, missing a critical input, or would require unsupported assumptions. Instead respond:

nih-biosketch-builder only handles its documented workflow. Please provide the missing required inputs or switch to a more suitable skill.

References

Response Template

Use the following fixed structure for non-trivial requests:

  1. Objective
  2. Inputs Received
  3. Assumptions
  4. Workflow
  5. Deliverable
  6. Risks and Limits
  7. Next Checks

If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.

平台分布

OpenClaw

86.04%
按下载量换算971

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills