oauth2-skill
Implement OAuth2 authentication flows (authorization code, PKCE for SPAs), provider integration (Google, GitHub), callback handling, token exchange, session management, and CSRF protection.
57
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./auth/oauth2-skill/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk)
What this means
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.
Why it was flagged
Third-party content exposure detected (high risk: 0.80). The skill fetches and ingests user profile data from public provider endpoints (e.g., googleConfig.userInfoUrl, githubConfig.userInfoUrl and githubConfig.userEmailsUrl in auth/oauth.service.ts and oauth.controller.ts), which are untrusted/user-generated and are directly used to create/link accounts and issue tokens, so those third-party values can materially influence subsequent actions.
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.