ai-wrapper-product
Expert in building products that wrap AI APIs (OpenAI, Anthropic, etc.) into focused tools people will pay for. Not just 'ChatGPT but different' - products that solve specific problems with AI. Cov...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill ai-wrapper-product60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description shows promise with its specific focus on AI API wrapper products and explicit differentiation from generic ChatGPT clones. However, it is critically truncated, lacks a 'Use when...' clause, and doesn't enumerate concrete actions the skill enables. The incomplete text severely limits its effectiveness for skill selection.
Suggestions
Complete the truncated description and add an explicit 'Use when...' clause with trigger terms like 'AI product', 'API wrapper', 'monetize AI', 'LLM-powered tool', 'AI SaaS'
List specific concrete actions such as 'design pricing strategies', 'architect API integrations', 'identify vertical niches', 'calculate unit economics'
Add natural language triggers users would say: 'build an AI product', 'wrap OpenAI API', 'create AI tool business', 'monetize GPT'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AI API wrapper products) and mentions 'focused tools' and 'solve specific problems', but the description is truncated and doesn't list concrete actions like 'design pricing models', 'architect API integrations', or 'validate product-market fit'. | 2 / 3 |
Completeness | The description addresses 'what' (building AI API wrapper products) but is truncated ('Cov...') and contains no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing or implied at best. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'OpenAI', 'Anthropic', 'AI APIs', and 'ChatGPT', but the truncation prevents assessment of full trigger coverage. Missing common variations users might say like 'AI wrapper', 'LLM product', 'API monetization'. | 2 / 3 |
Distinctiveness Conflict Risk | The focus on 'products that wrap AI APIs' and 'not just ChatGPT but different' provides some distinctiveness, but could overlap with general product development, startup, or AI integration skills without clearer boundaries. | 2 / 3 |
Total | 7 / 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 skill provides solid, actionable code examples for building AI wrapper products with good coverage of cost management and prompt engineering. However, it suffers from some organizational issues - the Sharp Edges section references non-existent solution sections, and the workflow lacks explicit validation checkpoints for error recovery. The intro section could be more concise.
Suggestions
Fix the Sharp Edges section to either include the referenced solutions inline or link to actual separate files (e.g., 'See [COST_CONTROL.md](COST_CONTROL.md)')
Add explicit validation and retry workflow: 'If output parsing fails → retry with different prompt → fallback to simpler model → return error to user'
Remove the conversational intro paragraph and capabilities bullet list - start directly with the Patterns section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary verbosity in the intro section ('You know AI wrappers get a bad rap') and the capabilities list could be trimmed. However, the code examples are reasonably efficient and the tables are well-structured. | 2 / 3 |
Actionability | Provides fully executable JavaScript code examples with real API calls, concrete prompt templates, cost calculation functions, and usage tracking implementations. Code is copy-paste ready with proper imports and error handling. | 3 / 3 |
Workflow Clarity | The wrapper stack diagram shows clear sequence, but validation checkpoints are implicit rather than explicit. Missing feedback loops for handling API failures or output validation failures in the main workflow. The Sharp Edges section references solutions that aren't fully detailed. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections with tables and patterns, but it's somewhat monolithic. The Sharp Edges section references solutions (## Controlling AI Costs, etc.) that appear to be internal headers rather than separate files, creating confusion. Related Skills mention other skills but don't provide navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.