Complexa Target
NVIDIAOfficialCreated by Ohad MosafiDistributed by NVIDIA
- Skill
- Tool integration
- Software development
- Apache-2.0
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The complexa-target skill provides a standardized approach to defining, editing, and validating design targets within the Proteina-Complexa framework. It covers the registration of protein binders, ligand binders, and AME enzyme scaffolding by managing specific YAML configuration files. The skill emphasizes direct file editing for configuration management, offering a reliable way to define target parameters such as chain selectors, hotspot residues, and ligand information, while providing validation steps to ensure target integrity before initiating design campaigns.
What it does
- Adds or updates target definitions in YAML registries for protein and ligand binders.
- Provides a structured schema for defining target inputs, hotspot residues, and ligand properties.
- Supports manual configuration editing for AME enzyme scaffolding tasks.
- Validates target configurations to ensure PDB paths and parameters are correctly resolved.
- Offers CLI commands for listing and inspecting existing target definitions.
- Generates documentation artifacts for registered design targets.
When to use it
- When you need to register a new protein or ligand target for a design pipeline.
- When you need to modify existing target parameters like hotspot residues or binder length ranges.
- When you are preparing a new AME enzyme scaffolding task.
- When you need to verify that a target PDB is correctly referenced and accessible by the pipeline.
Advantages
- Direct YAML editing provides full control and avoids complex CLI flag management.
- Standardized schema ensures consistency across different design pipelines.
- Built-in validation steps prevent runtime errors by checking path resolution early.
- Supports both simple protein surfaces and complex ligand-binding pockets.
Usage examples
- “Add a new protein target named 'Target_Alpha' using PDB 'Alpha_Structure' from the 'custom_targets' source.”
- The agent will append a new entry to configs/targets/targets_dict.yaml with the specified source, filename, and default binder length, then verify the configuration.
- “Validate the configuration for the ligand target '41_7BKC_LIGAND'.”
- The agent will run the validation command against the ligand pipeline to confirm the target exists and the PDB file is correctly resolved.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/nvidia/complexa-target/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip complexa-target.zip -d .agents/skills
Documentation by Ohad Mosafi
complexa-target
Add or edit a design target in Proteina-Complexa. Targets live in three YAML files, one per complexa design pipeline:
configs/targets/targets_dict.yaml— protein binder (default pipeline)configs/targets/ligand_targets_dict.yaml— ligand binderconfigs/design_tasks/ame_dict_v2.yaml— AME / enzyme scaffolding
The complexa target CLI only manages the first two. AME tasks use an extended schema (the same core fields as ligand targets plus contig_atoms for hand-curated per-residue motif atom selections) and are file-edit-only.
Instructions
complexa target add is a thin wrapper around "load YAML → build dict → append a block" (see src/proteinfoundation/cli/target_manager.py:add_target_cli and append_target_to_dict). For agentic use, just edit the targets dict directly — the schema is short, the existing entries are great copy templates, and you skip 14 CLI flags / SMILES shell-escaping. Use the CLI only if you explicitly want its YAML auto-quoter or its overwrite-prompt safety.
For an offline edit, work on the supplied registry or requested output copy. When a copy is requested, create its parent directory and copy into an absent destination. If the destination already exists, inspect and preserve it: reuse it when it is the intended working copy, otherwise report the path conflict. Do not delete the output tree to restart a configuration edit. An installed Complexa runtime, GPU, or target structure is not required to write the configuration. Use the field schema below, preserve unrelated entries, and read back the saved block. Coordinate validation remains pending when the structure is absent; finish the configuration task without installing a runtime. With Read/Edit tools, read the destination copy before editing it; reading the original input path does not satisfy Edit's requirement for the output path.
Use the schema below and the selected registry; the CLI reference is needed
only for CLI use. Finish with the saved entry, its consumer pipeline, the
downstream generation.task_name, and the validation status.
| Step | Direct file edit (preferred) | CLI |
|---|---|---|
| Look at existing targets | Read configs/targets/{,ligand_}targets_dict.yaml (or configs/design_tasks/ame_dict_v2.yaml for AME) | complexa target list (protein/ligand only) |
| Look at one target | Read the dict and grep for the key | complexa target show NAME |
| Add a new target | Append a YAML block (Step 3a) | complexa target add ... (Step 3b) |
| Verify configuration | Parse the saved YAML and compare the changed entry and untouched keys | complexa target show NAME --dict PATH |
| Check runtime PDB-path resolution | Requires the full pipeline and environment | complexa validate target CONFIG --target NAME |
Step 1: Decide the target type
Targets live in three different files, one per complexa design pipeline. Pick the file by working out which pipeline the user will run, then add the entry to that file. Each file is consumed by exactly one pipeline.
| User intent | Pipeline | Targets dict file | This skill? |
|---|---|---|---|
| Bind a protein surface (PD-L1, IFNAR2, TNF-α, …) — default | configs/search_binder_local_pipeline.yaml | configs/targets/targets_dict.yaml | Yes — Step 2 (protein) |
| Bind a small-molecule pocket (FAD, SAM, OQO, …) | configs/search_ligand_binder_local_pipeline.yaml | configs/targets/ligand_targets_dict.yaml | Yes — Step 2 (ligand) |
AME / enzyme scaffolding (motif + ligand, M####_<pdb> names) | configs/search_ame_local_pipeline.yaml | configs/design_tasks/ame_dict_v2.yaml | Partial — see "AME tasks" below |
AME tasks (enzyme pipeline)
AME tasks live under motif_target_dict_cfg: with source, target_filename,
ligand, contig_atoms, binder_length, and use_bonds_from_file. The
contig_atoms string contains curated chain/residue/atom selections. Existing
entries illustrate the field structure, not the selections for a new motif.
If motif atoms, ligand selection, or structure location are missing, list the
missing inputs and write a separate, explicitly incomplete template if useful.
Leave the registry unchanged until those scientific inputs are supplied. A task
name or PDB ID alone does not determine them. In the missing-input handoff,
explain that registration will be a direct edit under motif_target_dict_cfg
once the curated selections are supplied; complexa target add cannot register
AME tasks. Completed entries are selected with ++generation.task_name=<NAME>
and configs/search_ame_local_pipeline.yaml.
Step 2: Gather required info
Use the supplied values and ask only for missing required information. Required fields differ for protein, ligand, and AME definitions.
Protein target
| Field | Question | Example | Required |
|---|---|---|---|
| name | "Target name (used as the dict key and task_name)?" | 02_PDL1, MyTarget_v1 | yes |
| source | "Source directory under $DATA_PATH/target_data/?" | bindcraft_targets, custom_targets | yes (or target_path) |
| target_filename | "PDB filename (no .pdb extension)?" | PD-L1, IFNAR2 | yes (or target_path) |
| target_input | "Chain + residue range — see reference for grammar." | A1-115, A1-50,B1-50 | yes |
| hotspot_residues | "Hotspot residues (interface contact residues)?" | ["A33", "A95", "A102"] | optional, recommended |
| binder_length | "Binder length range [min, max] or single [length]?" | [80, 150], [100] | optional (default [60, 120]) |
| pdb_id | "Reference PDB ID (optional, metadata only)?" | "2lag" | optional |
Hotspot selectors encode chain + residue number, not amino-acid identity.
For example, Tyr42 (Y42) on explicitly specified chain B becomes B42;
already supplied chain/residue selectors stay unchanged. Preserve the user's
residue numbering. Without coordinates, report that residue identities and
membership in the structure are unverified.
Ligand target — protein fields above (minus target_input), plus:
| Field | Question | Example | Required |
|---|---|---|---|
| ligand | "3-letter PDB ligand residue code?" | FAD, OQO, SAM | yes (presence marks target as ligand) |
| SMILES | "SMILES string for the ligand?" | "O=C2C3=Nc1cc(c(...)..." | recommended; uppercase YAML key |
| ligand_only | "Generate pocket around ligand only (no protein-protein interface)?" | true / false | optional (default true) |
| use_bonds_from_file | "Use bond info from the input PDB/CIF?" | true / false | optional (default true) |
| target_input | not required for ligand targets | — | no |
Check whether the proposed key already exists in the selected YAML mapping. Preserve an existing entry unless the user requested that entry's update.
Copy a supplied SMILES exactly. Chain-specific ligand selection belongs to
preparation of the input structure; do not invent a chain field or protein
target_input to represent it in the ligand entry.
Examples
Step 3a: Append the YAML block directly (preferred)
Open configs/targets/targets_dict.yaml (or ligand_targets_dict.yaml for ligand targets), find a similar existing entry as a style template, and append the new block under target_dict_cfg:. Two-space indent, single blank line between entries.
Protein template
02_PDL1:
source: bindcraft_targets
target_filename: PD-L1
target_input: "A1-115"
hotspot_residues: ["A37", "A39", "A49", "A98"]
binder_length: [64, 155]
pdb_id: "4z18"Rules to match the existing file style (mirrors what complexa target add would emit):
Quote chain/residue ranges (
"A1-115","A33") and any SMILES — flow-style strings get tripped up by:and brackets otherwise.Use flow-style lists (
["A33", "A95"],[64, 155]) — that's what the on-disk dump produces.target_input,source,target_filenameare required for protein.target_path(absolute path) can replacesource + target_filenameif the PDB lives outside$DATA_PATH/target_data/.
Ligand template
41_7BKC_LIGAND:
source: ligand_targets
target_filename: 7BKC_ligand_centered
hotspot_residues: [null]
binder_length: [100]
pdb_id: 7BKC
ligand: 'FAD'
ligand_only: True
SMILES: "O=C2C3=Nc1cc(c(cc1N(C3=NC(=O)N2)CC(O)C(O)C(O)COP(=O)(O)OP(=O)(O)OCC6OC(n5cnc4c(ncnc45)N)C(O)C6O)C)C"
use_bonds_from_file: TrueThe presence of the ligand: key flips the target into ligand mode — there is no separate is_ligand flag. target_input is not required for ligands.
After saving, skip to Step 4 to verify.
Step 3b: CLI alternative (complexa target add)
Use the CLI when you want its automatic chain/residue quoting, the overwrite-confirm prompt, or to wire target creation into a non-Python script. Prefer non-interactive mode for agentic use (-i / --editor opens an editor and blocks).
Confirmed flags (from src/proteinfoundation/cli/target_cli.py)
Read target_schema.md for the flag
table and worked CLI examples when this path is needed. Select the intended
dictionary with --dict; --source and --target-filename should be explicit
when they differ from the CLI defaults. AME registration remains a direct edit.
Step 4: Verify
First parse the saved YAML with an available YAML parser and check the selected mapping, field types, requested values, and preservation of other entries. Read back the resulting block. This verifies configuration editing only.
With a prepared Complexa installation, pipeline configs, environment, and target structure, additionally check runtime path resolution from that checkout:
# 1. Select the dictionary that was actually edited.
complexa target show 02_PDL1 --dict configs/targets/targets_dict.yaml
# 2. Resolve the PDB path and validate it exists on disk.
# This traverses Hydra defaults to find the target dict.
complexa validate target configs/search_binder_local_pipeline.yaml --target 02_PDL1complexa validate target (from src/proteinfoundation/cli/validate.py::validate_target) checks:
DATA_PATHis set andtarget_data/exists.The target name resolves in
target_dict_cfg.Either
target_pathexists, or$DATA_PATH/target_data/<source>/<target_filename>.pdbexists.target_input,hotspot_residues,binder_lengthare reported back so a human can sanity-check them.
For ligand targets, use configs/targets/ligand_targets_dict.yaml for show
and configs/search_ligand_binder_local_pipeline.yaml for validation; --target
is the target key, not a config path. This validator does not check residue
identities, ligand chemistry, or AME contig_atoms; do not describe a path check
as coordinate or scientific validation.
Step 5: Emit artifact
Save the edited entry and validation status at the user's requested output
location (otherwise ./target_<name>/). For an offline edit, the saved YAML
block is sufficient; no CLI-generated artifact is required. On a prepared
installation, a target-show record can also be saved:
mkdir -p target_02_PDL1
complexa target show 02_PDL1 > target_02_PDL1/target_show.txtIf a standalone definition is requested, save the actual entry under its
registry key in target_definition.yaml. The handoff should include the saved
path, target key, consumer pipeline from Step 1, and
++generation.task_name=<NAME>, together with what validation actually ran.
For an incomplete AME request, report the separate template, missing inputs,
and the direct registry edit needed after those inputs arrive.
Hardware requirements
None for target definition — this is a YAML edit, not a training/inference step. Disk impact is a few KB appended to the targets dict (plus an automatic .yaml.bak backup written by save_targets_dict).
For the downstream design / evaluate runs that consume the target, defer to complexa-design and references/hardware.md.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
Target PDB file: File not found from validate target | <source>/<target_filename>.pdb does not exist under $DATA_PATH/target_data/ | Confirm the PDB stem and source dir. Use --target-path /full/path.pdb if the file lives outside target_data/. |
| "Target 'X' already exists! Overwrite? (y/N)" | Name collision in dict | Either pick a new name, or pass -f / --force to overwrite. |
| Hotspot residue not in PDB | Wrong chain or residue number | Open the PDB, re-check chain letters (case-sensitive) and residue indices. Hotspots use the format <CHAIN><RESNUM> — see reference. |
| Chain not found | target_input references a chain that does not exist in the PDB | Inspect the PDB with grep "^ATOM" target.pdb | awk '{print $5}' | sort -u. |
| Ligand code missing from PDB | The 3-letter ligand code does not appear as a HETATM residue name in the file | Open the PDB and check HETATM lines; you may need a _ligand_centered variant of the PDB. |
| SMILES parse failure downstream | Bad SMILES string | Validate with rdkit.Chem.MolFromSmiles(smiles) before adding. Quote SMILES in shell to escape brackets and parens. |
| Target name with leading digit breaks Hydra interpolation | YAML treats 02_PDL1 as a string fine; some override syntaxes need quoting | Use ++generation.task_name=02_PDL1; quote if the shell strips characters. |
target_input appears ignored for a ligand target | By design — ligand targets do not use target_input; pocket is defined by the ligand | Leave it unset for ligand targets. |
Reference
references/target_schema.md— every field, chain-spec grammar, AME task-name grammar, three worked examples.configs/targets/targets_dict.yaml— live protein entries (copy a known-good one as a template).configs/targets/ligand_targets_dict.yaml— live ligand entries.configs/design_tasks/ame_dict_v2.yaml— AME task definitions (file-edit only, not exposed viacomplexa targetCLI).src/proteinfoundation/cli/target_cli.py— argparse source of truth.src/proteinfoundation/cli/target_manager.py—add_target_cli,list_targets,show_target, schema inTARGET_FIELDS.src/proteinfoundation/cli/validate.py—validate_targetimplementation.
Files
- ATTRIBUTION.mdAdded by AutoGineer958 B
- BENCHMARK.md7.5 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- SKILL.md14.6 KiB
- evals/evals.json9.0 KiB
- evals/files/campaign_context/README-excerpts.md3.8 KiB
- evals/files/campaign_context/SNAPSHOT.md622 B
- evals/files/campaign_context/configs/pipeline/binder/binder_generate.yaml9.0 KiB
- evals/files/campaign_context/configs/search_binder_local_pipeline.yaml1.5 KiB
- evals/files/campaign_context/source_manifest.json809 B
- evals/files/project/SNAPSHOT.md570 B
- evals/files/project/configs/design_tasks/ame_dict_v2.yaml237 B
- evals/files/project/configs/pipeline/ligand_binder/ligand_binder_generate.yaml5.6 KiB
- evals/files/project/configs/search_ligand_binder_local_pipeline.yaml1.9 KiB
- evals/files/project/configs/targets/ligand_targets_dict.yaml222 B
- evals/files/project/configs/targets/targets_dict.yaml176 B
- evals/files/project/source_manifest.json716 B
- references/hardware.md4.8 KiB
- references/target_schema.md12.0 KiB
- skill-card.md5.0 KiB
- skill.oms.sig8.2 KiB
LICENSE
Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Ohad Mosafi
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/bionemo-complexa-target · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Ohad Mosafi or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download complexa-target.zip