CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

53%

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/ai-wrapper-product/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%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 a well-structured pointer document: lean, organized into clear sections, and correctly delegating detail to a real one-level-deep reference file. Its weakness is that it contains no actionable procedure of its own — only role, persona, and triggers — so the skill's executable value is entirely outsourced to the guide, and the persona paragraph adds padding without content.

Suggestions

Add a brief 'Quick start' to the body (e.g., the wrapper-stack skeleton or a hard-cost-limits checklist) so the root file has at least one concrete, executable element.

Cut the second-person persona paragraph ('You know AI wrappers get a bad rap...') — it states nothing Claude does not already assume and violates the efficient-overview pattern.

Deduplicate the Expertise bullet list against the guide's Capabilities section, keeping a single source of truth.

DimensionReasoningScore

Conciseness

Mostly efficient at 49 lines, but the persona paragraph is motivational padding ("You know AI wrappers get a bad rap... You create AI products people actually pay for and use daily") and the Expertise bullet list duplicates the guide's Capabilities section. Not score 4 because the persona paragraph and duplication are unnecessary tokens that could be trimmed.

3 / 5

Actionability

The body contains no executable guidance for the skill's actual work — no code, commands, or specific steps — only a navigation instruction ("Read [the detailed guide](references/detailed-guide.md) before executing this skill") and abstract role framing ("You are... AI Product Architect" metaphorically via 'Role'). Not score 3 because there is no partial concrete procedure at all in the body; not score 1 because the pointer instruction and When to Use triggers are concrete, actionable directives.

2 / 5

Workflow Clarity

No sequence of steps appears in the body itself; the only procedural content is the single directive to read the guide first, with all sequencing and validation offloaded to the referenced file. Not score 3 because even a rough step list is absent; not score 1 because the delegation instruction is coherent and mandatory-sounding ("Treat its safety, prerequisites, and validation requirements as mandatory").

2 / 5

Progressive Disclosure

Good structure: a lean 49-line overview with one clearly signaled, one-level-deep reference to references/detailed-guide.md (which exists on disk, 664 lines) including load guidance ("For focused work, load the relevant sections; for end-to-end work, read the guide completely"). Not score 5 because the body's Expertise list duplicates the guide's Capabilities section and the guide itself contains duplicated headings (e.g., '### AI Product Architecture' and '## AI Product Architecture' both appear), leaving minor organization gaps.

4 / 5

Total

11

/

20

Passed

Description

45%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 names its domain clearly but reads as a persona claim rather than a capability statement: it lists no concrete actions and includes no 'Use when' trigger guidance, capping completeness at 3. Trigger-term coverage is partial, and the broad 'solve specific problems with AI' framing creates real overlap risk with adjacent AI-development skills.

Suggestions

Add a 'Use when...' clause with concrete triggers (e.g., 'Use when the user wants to build an AI wrapper, AI SaaS, GPT product, or tool on top of the OpenAI/Anthropic APIs').

Replace the persona framing with concrete capabilities (e.g., 'Designs prompt templates, manages API costs and rate limits, and meters usage for AI-powered products').

Trim the 'Not just ChatGPT but different' editorializing in favor of synonyms users actually type (AI wrapper, AI tool, GPT product).

DimensionReasoningScore

Specificity

Names the domain ("building products that wrap AI APIs (OpenAI, Anthropic, etc.)") but gives only an identity claim ("Expert in building products") — no concrete actions such as prompt engineering, cost management, or rate limiting are stated in the description. Not score 1 because the domain and vendors are explicit; not score 3 because no 1-2 concrete capabilities are listed.

2 / 5

Completeness

A clear 'what' is present ("building products that wrap AI APIs into focused tools people will pay for") but the description has no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3. Not score 4 because the 'when' is entirely missing rather than just under-specified.

3 / 5

Trigger Term Quality

Contains some natural terms users would say ("wrap AI APIs", "OpenAI", "Anthropic", "ChatGPT") but misses common variations like "AI wrapper", "AI SaaS", "GPT product", and "AI tool". Not score 4 because several natural phrases users would actually type are absent.

3 / 5

Distinctiveness Conflict Risk

The AI-wrapper niche with named vendors is somewhat specific, but the broad framing ("products that solve specific problems with AI") risks overlap with general AI-development, prompt-engineering, and SaaS-building skills. Not score 4 because overlap risk with closely related AI product skills is more than minor.

3 / 5

Total

11

/

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.

Validation — 15 / 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

sickn33/agentic-awesome-skills

Path

skills/ai-wrapper-product/SKILL.md

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.