Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

$pwd:

hcls-get-started

Name: Hcls Get Started
Author: aws-samples

// Use when a developer asks how to get started building healthcare or life sciences agents, wants to understand the HCLS Agents Toolkit, or asks what's available in this repository. Also use when someone asks about genomics, drug discovery, clinical trials, or biomarker agents on AWS.

In Manus ausführen

$ git log --oneline --stat

stars:260

forks:101

updated:19. Mai 2026 um 16:11

Datei-Explorer

3 Dateien

SKILL.md

readonly

name	hcls-get-started
description	Use when a developer asks how to get started building healthcare or life sciences agents, wants to understand the HCLS Agents Toolkit, or asks what's available in this repository. Also use when someone asks about genomics, drug discovery, clinical trials, or biomarker agents on AWS.

Getting Started with the HCLS Agents Toolkit

When to use this skill

Developer asks "how do I build an HCLS agent?"
Developer asks "what agents are available for healthcare/life sciences?"
Developer wants to understand the toolkit's architecture and offerings

Overview

The HCLS Agents Toolkit provides three types of resources:

Skills — Domain workflow knowledge (this directory: skills/)
MCP Servers — Domain tools accessible from any MCP client (mcp-servers/)
Agent Catalog — 36+ production-ready deployed agents (agents_catalog/)

Choosing Your Path

Goal	Start here
Build a new HCLS agent from scratch	Use `hcls-build-agent` skill + `agentcore_template/`
Deploy an existing catalog agent	Pick from `agents_catalog/`, follow its README
Connect domain tools to your IDE	Configure MCP servers from `mcp-servers/`
Run HCLS workflows without deploying	Use skills + MCP servers directly in your assistant

Architecture

Agents are composed from:

Skills (knowledge) — SKILL.md files that teach workflows
MCP tools (actions) — deployed via AgentCore Gateway/Runtime or configured from public servers
Agent reasoning (orchestration) — system prompts + Strands framework + guardrails

Key References

Agent catalog: agents_catalog/ (36+ agents across genomics, drug discovery, clinical trials, etc.)
Deployment templates: agentcore_template/ (backend) or FAST (full-stack)
Framework: Strands Agents
Infrastructure: Amazon Bedrock AgentCore

Next Steps

Browse skills by domain: genomics, drug discovery, clinical trials, biomarker, terminology
Configure MCP servers for immediate tool access (see mcp-servers/aws-public/ and mcp-servers/third-party/)
Use hcls-build-agent skill when ready to build a custom agent
Use hcls-deploy-agent skill when ready to deploy to production

related-skills.json

gleiches Repository

biomarker-database-analysis.md

from "aws-samples/amazon-bedrock-agents-healthcare-lifesciences"

Use when a researcher needs to query biomedical databases for biomarker discovery, build target profiles from UniProt/Open Targets/STRING, rank biomarker candidates by evidence strength, or generate SQL queries against clinical genomic databases.

2026-05-19260

biomarker-multi-agent-discovery.md

from "aws-samples/amazon-bedrock-agents-healthcare-lifesciences"

Use when orchestrating a multi-agent biomarker discovery workflow that requires coordinating database queries, pathway analysis, literature review, statistical modeling, and clinical evidence synthesis to produce ranked biomarker panels.

2026-05-19260

biomarker-pathway-analysis.md

from "aws-samples/amazon-bedrock-agents-healthcare-lifesciences"

Use when a researcher needs to analyze biological pathways for biomarker discovery, map disease mechanisms to druggable targets using Reactome/KEGG, identify pathway enrichment from gene sets, or understand mechanism-of-action for candidate biomarkers.

2026-05-19260

genomics-variant-interpretation.md

from "aws-samples/amazon-bedrock-agents-healthcare-lifesciences"

Use when interpreting genomic variants from VCF files, performing clinical variant classification using ClinVar/VEP annotations, analyzing allele frequencies against population data (1000 Genomes), or generating clinical reports for genetic counseling.

2026-05-19260

hcls-build-agent.md

from "aws-samples/amazon-bedrock-agents-healthcare-lifesciences"

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.

2026-05-19260

hcls-deploy-agent.md

from "aws-samples/amazon-bedrock-agents-healthcare-lifesciences"

Use 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 register an agent in the AgentCore Registry. Also use for deployment troubleshooting.

2026-05-19260

package.json

"author": "aws-samples"

"repository": "aws-samples/amazon-bedrock-agents-healthcare-lifesciences"

GitHub-Repository öffnen Creator-Repositorys ansehen

$ install --global

$ download --local

In Manus ausführen

$ useful --forSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

name	hcls-get-started
description	Use when a developer asks how to get started building healthcare or life sciences agents, wants to understand the HCLS Agents Toolkit, or asks what's available in this repository. Also use when someone asks about genomics, drug discovery, clinical trials, or biomarker agents on AWS.

Getting Started with the HCLS Agents Toolkit

When to use this skill

Developer asks "how do I build an HCLS agent?"
Developer asks "what agents are available for healthcare/life sciences?"
Developer wants to understand the toolkit's architecture and offerings

Overview

The HCLS Agents Toolkit provides three types of resources:

Skills — Domain workflow knowledge (this directory: skills/)
MCP Servers — Domain tools accessible from any MCP client (mcp-servers/)
Agent Catalog — 36+ production-ready deployed agents (agents_catalog/)

Choosing Your Path

Goal	Start here
Build a new HCLS agent from scratch	Use `hcls-build-agent` skill + `agentcore_template/`
Deploy an existing catalog agent	Pick from `agents_catalog/`, follow its README
Connect domain tools to your IDE	Configure MCP servers from `mcp-servers/`
Run HCLS workflows without deploying	Use skills + MCP servers directly in your assistant

Architecture

Agents are composed from:

Skills (knowledge) — SKILL.md files that teach workflows
MCP tools (actions) — deployed via AgentCore Gateway/Runtime or configured from public servers
Agent reasoning (orchestration) — system prompts + Strands framework + guardrails

Key References

Agent catalog: agents_catalog/ (36+ agents across genomics, drug discovery, clinical trials, etc.)
Deployment templates: agentcore_template/ (backend) or FAST (full-stack)
Framework: Strands Agents
Infrastructure: Amazon Bedrock AgentCore

Next Steps

Browse skills by domain: genomics, drug discovery, clinical trials, biomarker, terminology
Configure MCP servers for immediate tool access (see mcp-servers/aws-public/ and mcp-servers/third-party/)
Use hcls-build-agent skill when ready to build a custom agent
Use hcls-deploy-agent skill when ready to deploy to production

hcls-get-started

Getting Started with the HCLS Agents Toolkit

When to use this skill

Overview

Choosing Your Path

Architecture

Key References

Next Steps

Mehr aus diesem Repository

Mehr aus diesem Repository

Getting Started with the HCLS Agents Toolkit

When to use this skill

Overview

Choosing Your Path

Architecture

Key References

Next Steps