CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-ai-wrapper-product/SKILL.md

The canonical home for this skill is ai-wrapper-product in sickn33/antigravity-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

43%Weight 40%Scale 1-5

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

The body is well-structured for progressive disclosure, cleanly pointing to a real detailed guide, but it is thin on actionability and workflow clarity — it relies almost entirely on the referenced file for executable guidance. Tightening the persona prose and surfacing at least a minimal concrete workflow would raise the score.

Suggestions

Add a brief, concrete starting workflow in the body (e.g., 1. Validate the problem/use case, 2. Choose model + draft prompt, 3. Wire input/output validation, 4. Add metering/rate limits, 5. Test cost vs. UX) so the skill is actionable without loading the guide.

Trim the motivational persona paragraph to one line of role framing to improve token efficiency.

Include one small executable snippet or specific command/pattern inline (e.g., a minimal API-call + output-validation example) to lift actionability.

DimensionReasoningScore

Conciseness

Mostly efficient with concise expertise and section lists, but the persona paragraph ('You know AI wrappers get a bad rap... You build products where AI is the engine, not the gimmick...') is motivational prose that could be trimmed without losing guidance. Not a 4 because that paragraph is noticeable padding rather than a minor instance.

3 / 5

Actionability

The body offers high-level expertise areas and a pointer to the detailed guide but no concrete, executable steps or examples of its own ('AI product strategy', 'Prompt engineering' are labels, not instructions). Minimal concrete guidance with the actual procedure deferred elsewhere.

2 / 5

Workflow Clarity

No sequenced workflow appears in the body; the only step-like instruction is 'Read the detailed guide before executing this skill.' Building an AI wrapper is inherently multi-step, but the body provides only a rough, poorly-defined pointer rather than a sequenced process with checkpoints.

2 / 5

Progressive Disclosure

The body is a clean overview that signals a single one-level-deep reference ([references/detailed-guide.md], a real file) for the full procedure, with well-organized sections (Role, Expertise, Detailed Guide, When to Use, Limitations) and easy navigation. Matches the top anchor for clear overview with well-signaled one-level-deep references.

5 / 5

Total

12

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 clearly communicates a focused niche (AI wrapper products) with good trigger keywords, but lacks an explicit 'Use when' clause, which caps its completeness. It is specific and distinct but could add concrete trigger phrases to reach the top band.

Suggestions

Append an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user wants to build an AI wrapper, GPT/Claude API product, or AI SaaS tool').

Add common synonym triggers like 'AI SaaS', 'GPT product', and 'Claude API product' to the description itself rather than only the body's When-to-Use list.

Tighten 'products that solve specific problems with AI' to concrete action verbs to push specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain ('building products that wrap AI APIs (OpenAI, Anthropic, etc.)') and lists several concrete sub-capabilities ('prompt engineering for products, cost management, rate limiting'), with minor gaps in coverage. Not a 5 because the actions are topic areas rather than fully enumerated concrete actions.

4 / 5

Completeness

Has a clear 'what' (building focused AI-wrapper products people pay for) but no explicit 'Use when...' clause; the 'when' is only weakly implied by the listed API names. Per the guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('wrap AI APIs', 'ChatGPT', 'OpenAI', 'Anthropic'), but misses common variations such as 'AI SaaS', 'GPT product', or 'Claude API product' that appear only in the body. Good coverage, a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

The 'AI wrapper product' niche is fairly distinct from generic coding or pure prompt-engineering skills, with minimal overlap risk. Not a 5 because 'products that solve specific problems with AI' is still broad enough to brush against general AI-product skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
boisenoise/skills-collections
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.