Monitor and manage your OpenCode tasks using helper scripts.
53
61%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./bot/workspace/skills/opencode/SKILL.mdSecurity
1 high severity finding. You should review these findings carefully before considering using this skill.
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
I inspected all files for high-entropy literal values that could provide access. The only candidates are the many "ses_..." identifiers in status.json: they are long, random-looking session IDs (high entropy) stored as literal keys. These are not placeholders or simple example passwords and could be used to access session data via the service API, so they meet the definition of secrets. Other values (e.g., base_url="http://127.0.0.1:4096") are local endpoints or clearly non-secret and were ignored.
f316d6a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.