小五子 - 基因优化

v1.0.0

专注于压缩提示词Token、调整指令权重及语义对齐,提升本地模型执行效率和指令精准度。

0· 76·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (prompt token compression, weight adjustment, semantic alignment) matches the SKILL.md content. The skill makes no unexpected requests (no env vars, no binaries, no installs), which is proportionate for a prompt-optimization/instruction-tuning helper.
Instruction Scope
SKILL.md is high-level/descriptive rather than a runbook: it describes token compression, adaptive weight tuning, and semantic alignment but gives no concrete steps. This is not unsafe by itself, but the wording '根据历史任务的成功率反馈' implies it would use historical success/feedback data — the skill doesn't say where that data comes from or whether it will read logs or user files. Recommend clarifying the data sources and any read/write actions before use.
Install Mechanism
No install spec and no code files are present, so nothing is written to disk or fetched during install. This is the lowest-risk install profile.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no disproportionate credential requests relative to its purpose.
Persistence & Privilege
Flags show default behavior (not always:true) and autonomous invocation is allowed by platform default. The skill does not request permanent presence or system-wide config changes in its metadata or instructions.
Assessment
This skill appears coherent and low-risk: it's a descriptive prompt/weight-tuning helper with no installers or credential needs. Before enabling it widely, ask the author (or your integrator) to clarify: (1) what concrete data sources it will read for 'historical success' feedback (agent logs, task history, user files?), (2) whether it will persist or overwrite any prompts/weights and how rollbacks/audits are handled, and (3) any evaluation/testing you can run on non-sensitive tasks (and on a small scale) to confirm behavior. If those answers are acceptable, using it is reasonable; if it needs access to logs or files, restrict that access or review what is being read first.

Like a lobster shell, security has layers — review code before you run it.

evolvervk974d8t23wcf1tb3zj2xg1bs8n83rbjygenevk974d8t23wcf1tb3zj2xg1bs8n83rbjygepvk974d8t23wcf1tb3zj2xg1bs8n83rbjylatestvk974d8t23wcf1tb3zj2xg1bs8n83rbjyxiaowuzivk974d8t23wcf1tb3zj2xg1bs8n83rbjy

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments