Biomedical Analysis Dispatch
xjtulyc/MedgeClaw
Routes bioinformatics, drug discovery, clinical and multi-omics tasks from a chat interface to Claude Code sessions running K-Dense scientific skills, with a live dashboard per task.
Official agent skill
Hcls Build Agent
by aws-samples in aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when a developer wants to build a new healthcare or life sciences agent, structure tools and system prompts for an HCLS workflow, or create a Strands agent with…
Install Hcls Build Agent
$ npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws-samples/amazon-bedrock-agents-healthcare-lifesciences hcls-build-agent --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hcls-build-agent .claude/skills/hcls-build-agent && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hcls-build-agent" agent skill from https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences/tree/main/skills/hcls-build-agent into .claude/skills/hcls-build-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hcls-build-agent", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences/tree/main/skills/hcls-build-agentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws-samples/amazon-bedrock-agents-healthcare-lifesciences hcls-build-agent --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hcls-build-agent .agents/skills/hcls-build-agent && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hcls-build-agent" agent skill from https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences/tree/main/skills/hcls-build-agent into .agents/skills/hcls-build-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hcls-build-agent", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws-samples/amazon-bedrock-agents-healthcare-lifesciences hcls-build-agent --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hcls-build-agent .cursor/skills/hcls-build-agent && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hcls-build-agent" agent skill from https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences/tree/main/skills/hcls-build-agent into .cursor/skills/hcls-build-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hcls-build-agent", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences.git --path skills/hcls-build-agent--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws-samples/amazon-bedrock-agents-healthcare-lifesciences hcls-build-agent --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hcls-build-agent .gemini/skills/hcls-build-agent && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hcls-build-agent" agent skill from https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences/tree/main/skills/hcls-build-agent into .gemini/skills/hcls-build-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hcls-build-agent", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws-samples/amazon-bedrock-agents-healthcare-lifesciences hcls-build-agentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hcls-build-agent .github/skills/hcls-build-agent && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hcls-build-agent" agent skill from https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences/tree/main/skills/hcls-build-agent into .github/skills/hcls-build-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hcls-build-agent", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws-samples/amazon-bedrock-agents-healthcare-lifesciences hcls-build-agent --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hcls-build-agent .opencode/skills/hcls-build-agent && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hcls-build-agent" agent skill from https://github.com/aws-samples/amazon-bedrock-agents-healthcare-lifesciences/tree/main/skills/hcls-build-agent into .opencode/skills/hcls-build-agent/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hcls-build-agent", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hcls-build-agent- GitHub stars
- 274
- Token cost
- ~885 tokens
- SKILL.md length
- 288 words
- Files
- 3 (incl. scripts, references)
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT-0
At a glance
A skill your agent uses when a developer wants to build a new healthcare or life sciences agent, structure tools and system prompts for an HCLS workflow, or create a Strands agent with…
- Works in 6 steps: Choose a template → Define your agent's domain scope → Create tools → …
- A developer wants to build a new healthcare
- SKILL.md covers When to use this skill, Agent Architecture, Steps and References, plus 1 more section
- Calls python
What it does
Hcls Build Agent is an agent skill from aws-samples/amazon-bedrock-agents-healthcare-lifesciences, published by the product's own GitHub organization. Use when a developer wants to build a new healthcare or life sciences agent, structure tools and system prompts for an HCLS workflow, or create a Strands agent with domain-specific capabilities. Also use when someone asks about agent architecture, tool design, or system prompt patterns for clinical, genomics, or drug discovery use cases.
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts and reference files.
It sits in Research & Science, covering Prompt engineering, Drug discovery and cheminformatics and Bioinformatics. It works with Amazon Web Services and Model Context Protocol. The licence is MIT-0.
When your agent uses it
- A developer wants to build a new healthcare
- Life sciences agent
- Structure tools and system prompts for an HCLS workflow
- Create a Strands agent with domain-specific capabilities
Example prompts
- “/hcls-build-agent”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9960565. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hcls Build Agent loads about 885 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 288 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from aws-samples/amazon-bedrock-agents-healthcare-lifesciences at commit 9960565, republished under its MIT-0 licence (© aws-samples). 288 words, ~885 tokens.
Download SKILL.mdSave it as
.claude/skills/hcls-build-agent/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- hcls-build-agent
- description
- Use when a developer wants to build a new healthcare or life sciences agent, structure tools and system prompts for an HCLS workflow, or create a Strands agent with domain-specific capabilities. Also use when someone asks about agent architecture, tool design, or system prompt patterns for clinical, genomics, or drug discovery use cases.
Building an HCLS Agent
When to use this skill
- Developer asks "how do I create a new HCLS agent?"
- Developer needs to structure tools, prompts, and workflows for a healthcare domain
- Developer is building an agent for genomics, drug discovery, clinical trials, or other HCLS workflows
Agent Architecture
An HCLS agent is composed of:
Agent = System Prompt + Tools (MCP) + Skills (Knowledge) + GuardrailsSteps
1. Choose a template
| Template | When to use |
|---|---|
agentcore_template/ | Backend-focused: agent runtime + Gateway tools + Streamlit UI |
| FAST | Full-stack: React frontend + Cognito auth + CDK deployment |
2. Define your agent's domain scope
- What HCLS workflow does it address?
- What data sources does it need? (databases, ontologies, literature)
- What actions should it perform? (query, analyze, generate, validate)
- What guardrails are needed? (PHI handling, clinical disclaimers, data validation)
3. Create tools
Tools are Python functions exposed via AgentCore Gateway (Lambda targets) or as local Strands tools.
# Local Strands tool
from strands import tool
@tool
def search_variants(gene: str, significance: str = "pathogenic") -> dict:
"""Search for genetic variants by gene name and clinical significance."""
# Implementation
passFor Gateway tools (accessible to any MCP client), create Lambda functions and register as Gateway targets. See agents_catalog/28-Research-agent-biomni-gateway-tools/ for the pattern.
4. Write the system prompt
Include:
- Domain expertise and role definition
- Available tools and when to use each
- Output format expectations
- Clinical/scientific disclaimers
- Guardrails (what NOT to do)
5. Add MCP server connections
Reference existing MCP servers for domain tools the agent needs:
- Biomedical databases: deploy Biomni Gateway (
mcp-servers/agentcore-gateway/biomni-research-tools/) - Ontology lookup: deploy OLS server (
mcp-servers/agentcore-runtime/ontology-lookup-service/) - Literature: configure PubMed (
mcp-servers/third-party/pubmed/) - Genomics workflows: configure HealthOmics (
mcp-servers/aws-public/aws-healthomics/)
6. Test
# Local testing with Strands
python main.py --prompt "Your test query"
# Test Gateway tools independently
python tests/test_gateway.py --prompt "Your test query"References
- Reference implementation (simple):
agents_catalog/24-Deep-Research-agent/ - Reference implementation (full Gateway):
agents_catalog/28-Research-agent-biomni-gateway-tools/ - Reference implementation (FAST template):
agents_catalog/35-Terminology-agent/ - Strands Agents docs: use the
strands-docsMCP server - AgentCore docs: use the
agentcore-docsMCP server
AWS MCP Servers Used
When building infrastructure for the agent, use:
aws-mcp— create IAM roles, Lambda functions, S3 bucketsagentcore-docs— AgentCore API reference for Gateway/Runtime/Memory configurationaws-healthomics— if the agent needs genomics workflow capabilities
© aws-samples, MIT-0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts, references) in skills/hcls-build-agent of aws-samples/amazon-bedrock-agents-healthcare-lifesciences.
- SKILL.md
- references/.gitkeep
- scripts/.gitkeep
Open the folder on GitHubat commit 9960565
Compare with similar skills
Hcls Build Agent next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hcls Build Agent this skillaws-samples/amazon-bedrock-agents-healthcare-lifesciences | 274 | — | ~885 | Automated safety check: Pass | MIT-0 | |
| Biomedical Analysis Dispatchxjtulyc/MedgeClaw | 617 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Chemgraphargonne-lcf/ChemGraph | 162 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Tooluniverseynulihao/AgentSkillOS | 617 | 3 repos | ~2.5k | Automated safety check: Pass | None | |
| Add Promptcyanheads/pubmed-mcp-server | 155 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Genomic IntelligenceK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~6.2k | Automated safety check: Notes | MIT |
Similar skills
Chemgraph
argonne-lcf/ChemGraph
Develop, test, and extend ChemGraph -- an agentic framework for automated molecular simulations using LLMs, LangGraph, ASE, and MCP servers
Tooluniverse
ynulihao/AgentSkillOS
A skill your agent uses when working with scientific research tools and workflows across bioinformatics, cheminformatics, genomics, structural biology, proteomics, and drug discovery.
Add Prompt
cyanheads/pubmed-mcp-server
Scaffold a new MCP prompt template. An agent skill from cyanheads/pubmed-mcp-server.
Genomic Intelligence
K-Dense-AI/scientific-agent-skills
Predicts regulatory features, gene structure, and expression directly from DNA sequence using Genomic Intelligence's hosted transformer DNA language models — no local GPU or model weights.
Mcpmed Bioinformatics Server
FreedomIntelligence/OpenClaw-Medical-Skills
Model Context Protocol (MCP) server for bioinformatics web services like GEO, STRING, and UCSC Cell Browser.
More from aws-samples/amazon-bedrock-agents-healthcare-lifesciences
All 12 skills in this repo- Official
Instrument Data To Allotrope
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV.
- Official
Scientific Problem Selection
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions.
- Official
Biomarker Database Analysis
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when a researcher needs to query biomedical databases for biomarker discovery, build target profiles from UniProt/Open Targets/STRING, rank biomarker candidates by evidence…
- Official
Genomics Variant Interpretation
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when interpreting genomic variants from VCF files, performing clinical variant classification using ClinVar/VEP annotations, analyzing allele frequencies against population…
- Official
Hcls Deploy Agent
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when a developer wants to deploy an HCLS agent to Amazon Bedrock AgentCore, configure Gateway tools as MCP endpoints, set up authentication with Cognito, configure memory, or…
- Official
Biomarker Multi Agent Discovery
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when orchestrating a multi-agent biomarker discovery workflow that requires coordinating database queries, pathway analysis, literature review, statistical modeling, and…
Related
Categories
Questions about Hcls Build Agent
What does Hcls Build Agent do?
A skill your agent uses when a developer wants to build a new healthcare or life sciences agent, structure tools and system prompts for an HCLS workflow, or create a Strands agent with…. Hcls Build Agent is an agent skill from aws-samples/amazon-bedrock-agents-healthcare-lifesciences, published by the product's own GitHub organization. Use when a developer wants to build a new healthcare or life sciences agent, structure tools and system prompts for an HCLS workflow, or create a Strands agent with domain-specific capabilities.
When should I use Hcls Build Agent?
Hcls Build Agent fits situations like: A developer wants to build a new healthcare; life sciences agent; structure tools and system prompts for an HCLS workflow; create a Strands agent with domain-specific capabilities.
How do I install Hcls Build Agent in Claude Code?
Run `npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a claude-code`. Or copy the skill folder (skills/hcls-build-agent in aws-samples/amazon-bedrock-agents-healthcare-lifesciences) into .claude/skills/hcls-build-agent in your project. Claude Code loads it when a task matches its description.
How do I install Hcls Build Agent in Codex?
Run `npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a codex`. Or copy the skill folder (skills/hcls-build-agent in aws-samples/amazon-bedrock-agents-healthcare-lifesciences) into .agents/skills/hcls-build-agent in your project. Codex loads it when a task matches its description.
Can I use Hcls Build Agent in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws-samples/amazon-bedrock-agents-healthcare-lifesciences --skill hcls-build-agent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hcls-build-agent, .gemini/skills/hcls-build-agent, .github/skills/hcls-build-agent and .opencode/skills/hcls-build-agent in your project.
What does Hcls Build Agent need to run?
Going by SKILL.md and its folder, Hcls Build Agent needs the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Hcls Build Agent access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Hcls Build Agent safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Hcls Build Agent use?
Hcls Build Agent is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hcls Build Agent use?
About 885 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hcls Build Agent?
Skills that share tags, products or a category with Hcls Build Agent: Biomedical Analysis Dispatch (xjtulyc/MedgeClaw, 617 stars), Chemgraph (argonne-lcf/ChemGraph, 162 stars), Tooluniverse (ynulihao/AgentSkillOS, 617 stars) and Add Prompt (cyanheads/pubmed-mcp-server, 155 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hcls Build Agent?
aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/amazon-bedrock-agents-healthcare-lifesciences, which has 274 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 1, 2026.
Source: aws-samples/amazon-bedrock-agents-healthcare-lifesciences on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.