CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/ai-spec-coverage-mapper

Build-an-X workflow that uses an LLM to map existing tests to spec sections - given a spec doc + the test suite, the LLM identifies which tests cover which sections, surfaces uncovered sections (gap), and recommends specific tests to add. Output is a coverage matrix per spec ID. Scope is mapping tests that already exist and naming the gaps, not authoring tests for new acceptance criteria. Use when a spec doc and a test suite both exist but nobody can say which requirements are actually covered - before a release sign-off, an audit, or a decision about where to spend the next round of test effort.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Low

Low-risk findings.

1 low severity finding. Worth noting, but not necessarily harmful.

Low

W011: Third-party content exposure detected (indirect prompt injection risk).

What this means

The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.

Why it was flagged

This skill’s required workflow ingests FREE TEXT from outsider-authored sources by reading the spec document and test files at runtime (the spec/tests are not guaranteed to be authored by the operating user), then embeds that prose into the LLM context via `scripts/ai-coverage.py` when it constructs `messages: [{'role':'system',...}, {'role':'user','content': f"Spec:\n{spec_text}\n\nTests:\n{test_files}"}]`.

Report incorrect finding
Audited
Security analysis
Snyk