cursor-api-key-management

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-api-key-management

Manage API keys and authentication in Cursor. Triggers on "cursor api key", "cursor openai key", "cursor anthropic key", "own api key cursor". Use when working with APIs or building integrations. Trigger with phrases like "cursor api key management", "cursor management", "cursor".

54%

Overall

Validation — 81%

Implementation — 35%

Activation — 60%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

Criteria	Description	Result
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

	Total	13 / 16 Passed

Implementation

35%

This skill provides a reasonable structure but lacks the concrete, actionable guidance needed for effective execution. The instructions are too vague (no specific UI paths, no commands, no code examples) and defer critical content to external files without providing sufficient inline material. The benefits section wastes tokens on information Claude already knows.

Suggestions

Replace vague instructions with exact UI paths (e.g., 'Cursor Settings > Features > Models > OpenAI API Key') and specific commands for file permissions

Add a concrete code example showing how to test the API key works (e.g., a curl command or simple script)

Include inline troubleshooting for common errors (invalid key, rate limit, billing issues) rather than only referencing external file

Remove the 'Why Use Your Own API Keys?' benefits section - Claude understands these concepts already

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary explanation like the 'Why Use Your Own API Keys?' benefits list that Claude would already understand. The prerequisites section also explains obvious concepts.	2 / 3
Actionability	Instructions are vague and lack concrete guidance - 'Search for Cursor API' and 'Enter your API key in the appropriate field' are not specific. No actual code, commands, or exact UI paths are provided. Step 5 'Set file permissions' gives no concrete command.	1 / 3
Workflow Clarity	Steps are listed in sequence but lack validation checkpoints. Step 7 says 'Test API key by making a request' but doesn't explain how to verify success or handle failures. No feedback loop for troubleshooting.	2 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content lacks the concrete quick-start material that should be inline. The skill defers too much to external files without providing actionable content upfront.	2 / 3
	Total	7 / 12 Passed

Activation

60%

The description has a clear structure with explicit 'what' and 'when' clauses, but suffers from overly broad trigger terms that would cause frequent false matches. The specificity of capabilities is moderate, and the generic triggers like 'cursor' and 'working with APIs' create significant conflict risk with other skills.

Suggestions

Remove overly broad triggers like 'cursor', 'cursor management', and 'working with APIs or building integrations' - keep only the specific API key-related triggers

Add more specific concrete actions such as 'configure API keys', 'set up OpenAI/Anthropic authentication', 'manage provider credentials'

Narrow the 'Use when' clause to focus specifically on API key configuration scenarios rather than general API work

Dimension	Reasoning	Score
Specificity	Names the domain (API keys and authentication in Cursor) and a general action (manage), but lacks specific concrete actions like 'configure', 'rotate', 'validate', or 'store API keys'.	2 / 3
Completeness	Explicitly answers both what ('Manage API keys and authentication in Cursor') and when ('Use when working with APIs or building integrations. Trigger with phrases like...'), providing clear trigger guidance.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'cursor api key', 'cursor openai key', 'cursor anthropic key', but the triggers 'cursor management' and just 'cursor' are overly broad and would match many unrelated requests.	2 / 3
Distinctiveness Conflict Risk	The triggers 'cursor', 'cursor management', and 'working with APIs or building integrations' are extremely broad and would conflict with many other skills. Only the specific 'cursor api key' variants provide distinctiveness.	1 / 3
	Total	8 / 12 Passed

Reviewed

15 days ago

Table of Contents

Validation Implementation Activation

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.