Sequence Alignment
v1.0.0A skill for performing sequence alignment using NCBI BLAST API. Supports nucleotide and protein sequence comparison against major biological databases.
⭐ 0· 30·0 current·0 all-time
byAIpoch@aipoch-ai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (sequence alignment via NCBI BLAST) matches the included files and implementation: scripts/main.py posts to blast.ncbi.nlm.nih.gov and implements BLAST Put/Get flows and XML parsing. No unrelated services, binaries, or secrets are requested.
Instruction Scope
SKILL.md correctly instructs running scripts/main.py and validating with python -m py_compile. One minor inconsistency: the docs mention editing an in-file CONFIG block but the packaged main.py does not contain an obvious CONFIG section in the reviewed portions—this is likely a documentation mismatch, not malicious scope creep. Instructions do not request reading unrelated system files or transmitting data to unexpected endpoints.
Install Mechanism
No install spec; the skill is instruction-first and ships a Python script that uses only standard-library modules (urllib, xml.etree, etc.). No downloads from untrusted URLs or archive extraction are present.
Credentials
The skill declares no required environment variables or credentials and the code does not read secrets or config paths. Network access to NCBI is required and is consistent with the skill's purpose.
Persistence & Privilege
always:false and no code attempts to persist or modify other skills or system-wide agent settings. The skill can be invoked autonomously by the agent platform (disable-model-invocation:false) — this is platform default and not by itself a problem.
Assessment
This package appears coherent for running BLAST queries against NCBI. Before installing or running it, consider: (1) Data sensitivity — BLAST queries are sent to NCBI; do not submit proprietary or patient-identifiable sequences you cannot transmit externally. (2) Rate limits and etiquette — respect NCBI rate limits (sleep/polling delays are present but follow NCBI guidance and include a tool/email if required). (3) Run in an isolated environment (virtualenv/container) and review scripts/main.py yourself to confirm no local changes are needed. (4) The SKILL.md mentions editing a CONFIG block that may not exist; verify parameters via --help and the script code. (5) If you prefer to prevent autonomous runs, restrict the skill to manual invocation at the platform level. Overall the skill is internally consistent with its stated purpose.Like a lobster shell, security has layers — review code before you run it.
latestvk973b0pzgcsrk4aw753ypwtqd5841p77
License
MIT-0
Free to use, modify, and redistribute. No attribution required.