mysql-php-fixer
Update and fix remote MySQL for PHP websites
48
50%
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 ./.opencode/skills/mysql-php-fixer/SKILL.mdSecurity
1 high severity finding. You should review these findings carefully before considering using this skill.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
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.
Why it was flagged
The documentation contains several operational script files, reports, and setup files for a MySQL database fixer skill targeting a specific website (`arabclue.com`). While reviewing the files, I identified literal hardcoded database and SSH credentials containing real passwords (e.g., `Mirxa420$`) and sensitive host information used in test scripts and automated report files: 1. `test_connection.php:11`: `$password = 'Mirxa420$';` 2. `test_ssh_connection.sh:10-16`: `SSH_PASSWORD="Mirxa420$"` and `DB_PASSWORD="Mirxa420$"` 3. `test_mysql.php:13`: `$password = 'Mirxa420$';` 4. `SETUP_COMPLETE.md:41-49`: Real database credentials inside code blocks (`'Mirxa420$'`) These are active, high-entropy credentials hardcoded into functional/test scripts and logs rather than abstract placeholders like `YOUR_PASSWORD`, representing a clear credential leakage risk.
- Repository
- Mirxa27/arabclue
- Commit
d9c0ab5
- Audited
- Security analysis
Is this your skill?
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.