convex-http-actions

External API integration and webhook handling including HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation

Quality

62%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/convex-http-actions/SKILL.md

Quality

Discovery

60%

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 demonstrates strong specificity with concrete technical capabilities but falls short on completeness by lacking explicit trigger guidance. The trigger terms are technically accurate but could benefit from broader coverage of natural user language. Adding a 'Use when...' clause would significantly improve Claude's ability to select this skill appropriately.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when integrating with external services, setting up webhooks, or handling API authentication'

Include additional natural trigger terms users might say: 'REST API', 'third-party service', 'API keys', 'OAuth', 'callback URLs'

Specify the context more clearly to reduce overlap, e.g., 'for backend/server-side integrations' to distinguish from client-side API consumption

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation' - these are all distinct, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance to tell Claude when to select this skill.	2 / 3
Trigger Term Quality	Includes relevant technical terms like 'API', 'webhook', 'HTTP', 'CORS', 'authentication' that developers would use, but missing common variations like 'REST', 'endpoints', 'API calls', 'third-party integrations', or file extensions.	2 / 3
Distinctiveness Conflict Risk	The combination of 'External API' and 'webhook' provides some distinctiveness, but 'authentication' and 'HTTP' are generic enough to potentially overlap with general web development or security-focused skills.	2 / 3
	Total	9 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent executable code examples covering HTTP actions comprehensively. However, it's verbose for its purpose - many examples could be condensed or moved to reference files. The lack of explicit implementation workflow and validation checkpoints slightly reduces its effectiveness for guiding Claude through complex integrations.

Suggestions

Condense similar examples (e.g., combine JSON/form/bytes handling into one annotated example) to reduce token usage

Add an explicit implementation workflow at the top: '1. Create convex/http.ts with router → 2. Add routes → 3. Test with curl examples → 4. Deploy'

Move the complete webhook integration and schema examples to separate reference files (e.g., WEBHOOK_EXAMPLES.md) with clear links from the main skill

Dimension	Reasoning	Score
Conciseness	The content is comprehensive but includes some redundancy - multiple similar examples for request handling, and explanatory comments that Claude doesn't need. The file is quite long (~500 lines) when it could be more condensed.	2 / 3
Actionability	Excellent executable code examples throughout - complete TypeScript implementations for HTTP routing, webhook handling, authentication, CORS, and error handling. All examples are copy-paste ready with proper imports and types.	3 / 3
Workflow Clarity	While individual code examples are clear, there's no explicit workflow for implementing HTTP actions (e.g., 'first set up router, then add routes, then test'). Webhook verification has implicit validation but lacks explicit checkpoint guidance for the overall implementation process.	2 / 3
Progressive Disclosure	The document references external documentation links appropriately, but the main content is monolithic - all examples are inline rather than split into separate reference files. The schema example and complete webhook integration could be in separate files with clear navigation.	2 / 3
	Total	9 / 12 Passed

Validation

68%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (734 lines); consider splitting into references/ and linking	Warning
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')	Warning
metadata_version	'metadata' field is not a dictionary	Warning
license_field	'license' field is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	11 / 16 Passed

Repository: waynesutton/convexskills
Commit: 8ef49c9

Reviewed: about 2 months ago

Table of Contents

Discovery Implementation Validation

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.