CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/netlify-functions-tests

Wraps Netlify Functions testing patterns: Netlify Dev (`netlify dev`) for local routing emulation, the @netlify/functions handler API testing pattern, Netlify Edge Functions (Deno runtime) vs Background Functions (Lambda under the hood) distinction, and scheduled-function (cron) test patterns. Use when testing Netlify Functions or Edge Functions.

75

Quality

94%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

The body is highly actionable with executable examples, a clear sequenced workflow, and well-organized sections. The only weakness is mild verbosity in repeated doc preamble lines and a trailing catalog/sibling listing that could be trimmed.

Suggestions

Remove the repeated 'Per docs.netlify.com/...' preamble phrases before each flavor section; the consolidated References section already links these docs, so the inline citations are redundant.

Trim or move the 'Sibling tools' and 'Companion catalogs' lists out of SKILL.md — they name skills/files that aren't part of this bundle and add tokens without aiding execution.

Drop the restated Overview that duplicates the frontmatter description, keeping only the three-flavor breakdown that adds new information.

DimensionReasoningScore

Conciseness

Mostly efficient — dominated by executable code with brief framing — but repeated "Per docs.netlify.com/..." preamble lines, a body Overview that restates the frontmatter, and a trailing Sibling/Companion catalog list add tokens that could be tightened. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 3-anchor.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript handlers, a complete Jest test, specific commands (`netlify dev --port 8888`, `curl ...`, `npx jest`), and a CI YAML block — satisfying the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Clear sequenced progression from Install → author function → test handler directly → run netlify dev → CI, with the test step acting as the validation checkpoint and the Anti-patterns table providing explicit 'Why it fails → Fix' feedback loops for error recovery.

3 / 3

Progressive Disclosure

Self-contained, well-organized into clear sections (Authoring per flavor, Running, CI, Anti-patterns, Limitations, References) with one-level-deep references to external Netlify docs; no bundle files exist to evaluate, and the inline structure is appropriately split rather than monolithic.

3 / 3

Total

11

/

12

Passed

Description

100%

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 is specific, trigger-rich, complete, and distinct: it names concrete testing patterns and provides an explicit 'Use when' clause scoped to Netlify Functions and Edge Functions. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Lists multiple concrete testing patterns: "Netlify Dev (`netlify dev`) for local routing emulation", "the @netlify/functions handler API testing pattern", and "scheduled-function (cron) test patterns" — matching the anchor that lists several specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what (wraps Netlify Functions testing patterns) and when via the explicit trigger clause "Use when testing Netlify Functions or Edge Functions."

3 / 3

Trigger Term Quality

Includes natural terms users would actually say — "testing Netlify Functions", "Edge Functions", "netlify dev", "cron" — giving good coverage rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Netlify Functions testing) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Reviewed

Table of Contents