CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-api

Implements and debugs browser Prompt API integrations in JavaScript or TypeScript web apps. Use when adding LanguageModel availability checks, session creation, prompt or promptStreaming flows, structured output, download progress UX, or iframe permission-policy handling. Don't use for server-side LLM SDKs, REST AI APIs, or non-browser providers.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A well-structured procedural skill with clear sequencing, explicit validation, and clean one-level progressive disclosure into real bundle files. Tightening the duplicated availability/download guidance and offering a small inline runnable snippet would push it higher.

Suggestions

Consolidate the repeated 'availability() downloading before create()' guidance (Step 3.7, Step 4.6, Error Handling) into a single canonical statement referenced from the other locations.

Add a short inline runnable code snippet (e.g. a minimal availability-gated create() call) so the most common case is copy-paste ready without opening the template asset.

In Step 5, make the validation checkpoint a hard gate ('Only proceed when build/typecheck pass') to match the feedback-loop strength of the Error Handling section.

DimensionReasoningScore

Conciseness

The body is directive and assumes Claude's competence without explaining basic concepts, but the 'availability() downloading before create()' guidance is restated across Step 3, Step 4, and Error Handling, which could be consolidated.

4 / 5

Actionability

Concrete commands and named API surfaces ('node scripts/find-frontend-targets.mjs .', 'LanguageModel.availability()', 'responseConstraint', 'allow="language-model"') plus a template asset to adapt give mostly executable guidance, with no inline runnable snippet being the main gap.

4 / 5

Workflow Clarity

Five clearly sequenced steps include explicit stop conditions, a build/typecheck/test validation checkpoint in Step 5, and a dedicated Error Handling section with recovery feedback loops.

5 / 5

Progressive Disclosure

SKILL.md is an overview pointing to five reference files, one script, and one template asset, all clearly signaled inline and exactly one level deep with no nested reference chains; all referenced paths exist in the bundle.

5 / 5

Total

18

/

20

Passed

Description

92%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.

A tight, well-scoped description that states concrete capabilities, gives explicit positive and negative trigger guidance, and sharply delineates the browser-Prompt-API niche. Its only weakness is a slightly technical register that omits plain-language synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full Prompt API surface ('LanguageModel availability checks, session creation, prompt or promptStreaming flows, structured output, download progress UX, or iframe permission-policy handling'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both 'what' ('Implements and debugs browser Prompt API integrations') and 'when' ('Use when adding...') with concrete trigger phrases, plus a negative-scope boundary clause.

5 / 5

Trigger Term Quality

Strong technical keyword coverage ('Prompt API', 'LanguageModel', 'promptStreaming', 'structured output', 'iframe permission-policy') but leans toward jargon with few plain-language synonyms or user-natural variations, so it falls short of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

A clearly defined browser-Prompt-API niche with an explicit 'Don't use for server-side LLM SDKs, REST AI APIs, or non-browser providers' boundary minimizes overlap with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
webmaxru/web-ai-agent-skills
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.