oauth2-flow-helper
Oauth2 Flow Helper - Auto-activating skill for Security Fundamentals. Triggers on: oauth2 flow helper, oauth2 flow helper Part of the Security Fundamentals skill category.
32
0%
Does it follow best practices?
Impact
90%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/03-security-fundamentals/oauth2-flow-helper/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would employ, provides no 'when to use' guidance, and is indistinguishable from any other security-related skill. It needs a complete rewrite.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Guides implementation of OAuth2 authorization code flow, generates token exchange code, configures redirect URIs, and troubleshoots OAuth2 authentication errors.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user mentions OAuth, OAuth2, authorization code flow, access tokens, refresh tokens, PKCE, client credentials, or OAuth redirect configuration.'
Remove the duplicate trigger term ('oauth2 flow helper' is listed twice) and replace with varied, natural language terms users would actually use when seeking help with OAuth2 flows.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only names itself ('Oauth2 Flow Helper') and mentions a category ('Security Fundamentals') without describing what it actually does—no verbs like 'generates', 'validates', 'implements', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'oauth2 flow helper' repeated twice. These are not natural terms a user would say; users would more likely say 'OAuth', 'authorization code flow', 'access token', 'refresh token', 'OAuth redirect', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'Security Fundamentals' is broad, and without specifying what aspect of OAuth2 flows it handles (e.g., authorization code grant, token refresh, PKCE), it could easily conflict with any security-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual content about OAuth2 flows. It contains no executable code, no specific guidance on any OAuth2 grant type (authorization code, client credentials, PKCE, etc.), and no actionable instructions. Every section is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable code examples for at least the most common OAuth2 flows (e.g., Authorization Code with PKCE, Client Credentials) including token request/response examples.
Define a clear step-by-step workflow for implementing an OAuth2 flow, including validation checkpoints such as verifying token signatures, checking scopes, and handling token expiration.
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content: specific grant type selection guidance, security considerations (state parameter, PKCE), and common pitfalls.
Include concrete configuration examples (e.g., OAuth2 provider setup, redirect URI configuration, scope definitions) that are copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the skill name excessively, and provides zero substantive information about OAuth2 flows. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no specific OAuth2 flow details, no token endpoints, no grant types, no examples. It only describes what the skill supposedly does in vague terms. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no meaningful organization of content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
13d35b8
- Reviewed
Table of Contents
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.