Create, list, rotate, and revoke OmniRoute API keys. Control per-key scopes, spending limits, and expiration. Keys gate access to all proxy and management endpoints.
70%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./skills/omni-api-keys/SKILL.mdDetected a prompt injection in the skill instructions. The skill contains hidden or deceptive instructions that fall outside its stated purpose and attempt to override the agent’s safety guidelines or intended behavior.
The skill is a documented API-key management reference with no pretext, obfuscation, or covert trigger, but line 14 suggests disabling API-key requirements (REQUIRE_API_KEY=false) as an alternative to login, which weakens protection on the user's resources beyond what key management needs.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The required workflow reads the device list from GET /api/keys/{id}/devices, which returns User-Agent fingerprints that any client holding a valid key can set to arbitrary text, so outsider-authored strings reach the agent without a specific item being selected beyond the key ID.
diegosouzapw/OmniRoute
36a4ae0
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.