Non Tumor Ml Research Planner
v0.1.0Generates structured research designs for non-tumor biomedical machine learning studies, focusing on diagnostic models, biomarker discovery, and mechanism an...
⭐ 0· 216·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
The skill's name and description match the requested artifacts: generating non‑tumor bioinformatics+ML study plans. It requires no binaries, env vars, or installs and its reference files (study patterns, modules, configurations) align with that purpose.
Instruction Scope
SKILL.md contains prescriptive, domain-specific runtime instructions (input validation, decision points, study patterns, multi-tier output). It does not instruct the agent to read unrelated files, access environment variables, call external endpoints, or exfiltrate data. Triggers are broad (many natural phrasings) but the instructions remain within the stated planning scope.
Install Mechanism
No install specification or code files—instruction-only. There is nothing to download or write to disk, minimizing install-related risk.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The planned workflows reference commonly used public data sources and R packages conceptually (in documentation only), which is proportionate to the stated purpose.
Persistence & Privilege
Skill is not always-enabled and is user-invocable; model invocation is allowed (platform default). It does not request elevated persistence or modify other skills or system configurations.
Assessment
This skill appears coherent and low-risk because it is instruction-only and asks for no credentials or installs. Before installing or relying on its outputs, consider: (1) the skill produces study designs and recommended analyses but not executable code—have an experienced bioinformatician/statistician review plans and parameter choices; (2) verify dataset availability and legal/ethical permissions before using any patient data (do not paste PHI into prompts); (3) treat wet‑lab and clinical recommendations as suggestions requiring laboratory/clinical validation and IRB approval where relevant; (4) check that the suggested external packages/tools match your local environment and that you or your institution vet any code you run that implements the plan. Overall, the skill is internally consistent with its description.Like a lobster shell, security has layers — review code before you run it.
latestvk97b01cjh46314x7gxxv3hpytd82vnej
License
MIT-0
Free to use, modify, and redistribute. No attribution required.