oauth-client-setup
Oauth Client Setup - Auto-activating skill for API Integration. Triggers on: oauth client setup, oauth client setup Part of the API Integration skill category.
33
Quality
3%
Does it follow best practices?
Impact
85%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/16-api-integration/oauth-client-setup/SKILL.mdQuality
Discovery
7%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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The redundant trigger terms and lack of concrete actions make this description nearly useless for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Creates OAuth 2.0 client credentials, configures redirect URIs, generates client ID and secret pairs'
Include a 'Use when...' clause with natural trigger terms like 'API authentication', 'client credentials', 'OAuth setup', 'connect third-party service', 'API keys'
Specify which OAuth providers or platforms are supported to distinguish from other potential authentication skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Oauth Client Setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'configure', 'create credentials', 'manage tokens', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('oauth client setup' repeated twice) and overly technical. Missing natural variations users might say like 'OAuth credentials', 'client ID', 'client secret', 'API authentication', 'connect to API'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'OAuth client setup' is somewhat specific to authentication workflows, the lack of detail about what kind of OAuth (OAuth 2.0, specific providers) or what actions are performed could cause overlap with other API or authentication skills. | 2 / 3 |
Total | 5 / 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 content is a placeholder template that describes what a skill should do rather than actually teaching OAuth client setup. It contains zero actionable content - no code examples, no configuration steps, no OAuth flow explanations, and no concrete guidance. The entire file is meta-description that provides no value to Claude for performing OAuth client setup tasks.
Suggestions
Add concrete OAuth 2.0 flow examples with executable code (authorization code flow, client credentials flow) including actual HTTP requests or SDK usage
Include specific configuration steps: registering clients, setting redirect URIs, handling tokens, and storing credentials securely
Provide a clear workflow sequence: 1) Register app, 2) Configure scopes, 3) Implement token exchange, 4) Handle refresh tokens - with validation checkpoints
Replace meta-descriptions ('Provides step-by-step guidance') with actual step-by-step guidance and code snippets
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely meta-description with no actual OAuth implementation details. It explains what the skill does rather than providing actionable OAuth client setup instructions, wasting tokens on boilerplate. | 1 / 3 |
Actionability | No concrete code, commands, or specific OAuth setup steps are provided. The content only describes capabilities abstractly ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' there are no actual steps for OAuth client setup, no validation checkpoints, and no process sequence. | 1 / 3 |
Progressive Disclosure | No structure for actual content exists. The file contains only meta-information about the skill with no references to detailed materials, examples, or related documentation for OAuth implementation. | 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
0c08951
- 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.