Competing

v1.0.0

Improve systematically by analyzing losses, studying winners, and tracking progress against rivals in any competitive domain.

2· 576·0 current·0 all-time
byIván@ivangdavila
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
Name/description (improve by analyzing losses, studying winners, tracking rivals) matches the contents: analysis templates, tracking formats, domain guidance and rivals intelligence. No unrelated credentials, binaries, or external services are requested.
Instruction Scope
Runtime instructions are limited to analysis prompts, templates, and a recommendation to create a ~/competing/ workspace and markdown files. There are no instructions to read system secrets, call external endpoints, or access unrelated system paths.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes on-disk execution risk; nothing is downloaded or installed.
Credentials
The skill declares no environment variables, credentials, or config paths. The guidance to store logs and rival profiles locally is proportional to the claimed tracking purpose.
Persistence & Privilege
always:false and normal model invocation behavior. The skill does not request persistent system privileges or modifications to other skills; suggested local files are self-contained in the user's workspace.
Assessment
This is an instruction-only improvement framework and appears coherent and low-risk. Before installing or enabling: (1) acknowledge the skill recommends creating ~/competing/ and markdown logs — avoid putting sensitive data (passwords, private keys, or confidential competitor data) into those files; (2) confirm your agent/runtime has permission to write to your workspace if you want the files created; (3) note there is no network activity or external installs expected, so risks are limited to local file creation and any data you choose to record. If you want stricter control, keep logs in a private location or avoid storing sensitive details.

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

latestvk9712ghr463041e7b8w3fb6s7s811n08

License

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

Comments