Dynamic Temperature
v1.0.2Dynamic LLM temperature selection based on task type. Use when deciding what temperature to apply for a given task — scheduling, communication, creative writ...
⭐ 0· 50·1 current·1 all-time
byNetanel Abergel@netanel-abergel
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the content: the SKILL.md contains temperature rules and per-skill recommendations. Nothing in the files requires access to unrelated services or secrets.
Instruction Scope
The instructions stay on-topic (classify task type and choose a temperature). Implementation notes suggest updating agents.defaults.models or passing temperature to subagents — this touches agent configuration and runtime behavior but is reasonable for the stated goal. The guide also mandates confirmations for irreversible actions; users should verify that confirmation steps are actually implemented by the agent platform.
Install Mechanism
No install spec and no code files—this is instruction-only, so nothing is downloaded or written to disk by the skill itself.
Credentials
No required environment variables, credentials, or config paths are requested. The skill only recommends configuration changes and temperature values; it does not ask for secrets or external endpoints.
Persistence & Privilege
always is false and model invocation is allowed (default). The skill does not request permanent presence or modification of other skills' configurations. Note: DEPRECATED.md states this logic may be more appropriate in a core identity file (SOUL.md) if the user wants the rule applied universally.
Assessment
This skill is an advisory guideline for choosing temperature and appears safe: it asks for nothing sensitive and installs nothing. Before relying on it, consider: (1) the skill is instruction-only and will only take effect when invoked—if you want these rules applied to every model call, put them in your agent core identity (SOUL.md) or implement them in platform configuration; (2) the guide recommends confirming irreversible actions at temperature 0.0 — ensure your agent actually enforces a confirmation step rather than auto-sending; and (3) verify the per-skill names in the table match your deployed skills so recommendations are applied where intended.Like a lobster shell, security has layers — review code before you run it.
latestvk971htn2xdpcrpyh8zh1tmszy5846ds3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.