Default code-quality route for broad code review, PR review, maintainability, correctness, and regression-risk checks. Do not use as the primary route for dedicated OWASP/security audits, review-feedback handling, completion verification, AI-code cleanup, or TDD/test-first work.
49
52%
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 ./bundled/skills/code-reviewer/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 looked for high-entropy, literal credentials. I found a hardcoded API key in references/python-style-guide.md line 141: api_key = "sk-1234567890abcdef" This is a realistic API-key format (sk- prefix + hex-like characters), not a placeholder (e.g., YOUR_API_KEY or sk-xxxx) or a redaction, so it meets the definition of a secret and is flagged. No other high-entropy secrets (PEM blocks, live-looking keys) were present; remaining values are documentation examples or simple setup text and were ignored per the rules.
f627ab5
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.