Protein Docking Configurator

Security checks across static analysis, malware telemetry, and agentic risk

Overview

This appears to be a purpose-aligned local tool for generating molecular docking configuration files, with no evidence of network access, credential use, persistence, or exfiltration.

This skill looks safe for its stated purpose, but it is still local code. Review the script if possible, run it in a project directory, provide only intended receptor/ligand files, and choose output paths carefully to avoid overwriting files.

Static analysis

No static analysis findings were reported for this release.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Users have less external context for who maintains the skill or where to verify it.

Why it was flagged

The skill's provenance is not documented, although no risky install source or remote dependency is shown.

Skill content
Source: unknown; Homepage: none
Recommendation

Review the included code before use and prefer running it in a controlled workspace.

What this means

Running the script allows it to access local files specified in the command.

Why it was flagged

The documented workflow involves executing a local Python script. This is expected for a Tool/Script skill and aligns with its purpose.

Skill content
python scripts/main.py --receptor protein.pdb --active-site-residues "A:120,A:145,A:189" --software vina
Recommendation

Run it only on intended structure files and in a workspace where generated outputs can be safely reviewed.

What this means

If an unintended output path is provided, the script could overwrite a local file accessible to the running user.

Why it was flagged

The script writes to a user-supplied output path. That is normal for a configuration generator, but the visible code does not show path restriction or overwrite protection.

Skill content
with open(output_file, 'w') as f:
            f.write(content)
Recommendation

Use explicit output paths inside the project workspace and check whether a target file already exists before running.