oauth-client-setup
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill oauth-client-setupOauth Client Setup - Auto-activating skill for API Integration. Triggers on: oauth client setup, oauth client setup Part of the API Integration skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks concrete actions, natural user keywords, and explicit usage conditions. The duplicate trigger term suggests a template that wasn't properly filled out.
Suggestions
Add specific actions the skill performs, e.g., 'Configures OAuth 2.0 client credentials, generates access tokens, manages client IDs and secrets for API authentication.'
Include a 'Use when...' clause with natural trigger terms: 'Use when setting up OAuth authentication, configuring API credentials, or when the user mentions client ID, client secret, access tokens, or OAuth flows.'
Expand trigger terms to include variations users naturally say: 'OAuth', 'OAuth2', 'client credentials', 'API auth', 'access token', 'authorization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'oauth client setup' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'configure', 'generate tokens', 'manage credentials', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and has no explicit 'Use when...' clause or equivalent guidance for when Claude should select this skill. The 'Triggers on' section just repeats the title. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'oauth client setup' repeated twice. Missing natural variations users might say like 'OAuth', 'client credentials', 'API authentication', 'access tokens', 'client ID', 'client secret', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'oauth client setup' is somewhat specific to OAuth workflows, the lack of detail means it could conflict with other API or authentication-related skills. The mention of 'API Integration skill category' provides some context but doesn't clearly distinguish it. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is a placeholder template with no actual OAuth client setup guidance. It contains only meta-descriptions of what the skill should do without any concrete implementation details, code examples, or actionable instructions. The content would provide zero value to Claude when attempting to help users with OAuth client setup.
Suggestions
Add concrete code examples for OAuth 2.0 flows (authorization code, client credentials, etc.) with specific library implementations
Include step-by-step workflow for registering OAuth clients with common providers (Google, GitHub, etc.) including required scopes and redirect URI configuration
Provide executable code snippets for token exchange, refresh token handling, and secure credential storage
Add validation steps and common error handling patterns for OAuth failures (expired tokens, invalid scopes, etc.)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no actual OAuth implementation details. It explains what the skill does in abstract terms rather than providing any concrete guidance Claude could use. | 1 / 3 |
Actionability | No executable code, no specific commands, no concrete examples of OAuth client setup. The content describes rather than instructs, with phrases like 'provides step-by-step guidance' without actually providing any steps. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' there are zero actual steps for OAuth client setup, no validation checkpoints, and no process sequence. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no links to OAuth provider-specific guides, and no organization of content by complexity or use case. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.