SKILLEMALL.ai

AC ai-sdk-core

Build backend AI with Vercel AI SDK v6 stable. Covers Output API (replaces generateObject/streamObject), speech synthesis, transcription, embeddings, MCP tools with security guidance. Includes v4→v5 migration and 15 error solutions with workarounds. Use when: implementing AI SDK v5/v6, migrating versions, troubleshooting AI_APICallError, Workers startup issues, Output API errors, Gemini caching issues, Anthropic tool errors, MCP tools, or stream resumption failures.

modbender/skill-library-mcp Agent Skills author: modbender MIT 24 files · 1 script body ≈ 9 471 tokens Open the sourcegithub.com analyzed 2 d ago

Build backend AI with Vercel AI SDK v6 stable.

As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, execution cost, running it twice

IntegrationCloudflareAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
C
60/100
Has gaps
Inputs and preconditions w 11
0
Running it twice w 4
30
Execution cost w 6
40
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 24. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 9471 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 60/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 10 mutating operations with no state check
  • 40Execution cost. Instruction body is 9471 tokens: crowds the task out of the window
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Steps. 175 steps, 5 vague phrases
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 13 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • -46 reference files, but SKILL.md never points to them: the model will not open them
  • -31 of 1 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +3Description length 471: enough signal without eating the budget
  • +4Structure: 52 headings
  • +3Step-by-step instructions: 175 items
  • +3Output format is stated explicitly
  • +4Has examples (47 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.