Is tdmcp-test-coverage-707e90 safe to install?

SaferSkills independently audited tdmcp-test-coverage-707e90 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.agents/skills/tdmcp-test-coverage/SKILL.md · 1 file

.agents/skills/tdmcp-test-coverage/SKILL.md2.8 KB · Markdown

name: tdmcp-test-coverage

description: "Orchestrate any tdmcp test-coverage work: run the coverage harness, inspect coverage gaps, plan focused Vitest/msw or bridge tests, delegate coverage writers, verify coverage deltas, and re-run gates. Use whenever the user asks to raise coverage, add broad regression coverage, create a test harness, improve tests, re-run a coverage wave, or fix a coverage gate."

tdmcp-test-coverage

Use this skill for coverage-improvement work in this repository. The goal is more tested behavior, not prettier percentages.

Phase 0 - Context

Read AGENTS.md, package.json, vitest.config.ts, and the nearest tests.
Run npm run coverage:harness unless the user asked for a static-only pass.
Read _workspace/coverage/latest.md.
Treat the actionable scope as src/**/*.ts; src/knowledge/data/** is

generated reference data and is intentionally excluded.

Phase 1 - Select gaps

Choose one to three independent gaps. Prefer seams where a test can lock a real contract:

CLI/config: parsing, defaulting, env precedence, diagnostics, and exit behavior.
Resource/knowledge loaders: URI matching, malformed input, ranking, and stable

result shape.

Tool implementations: Zod defaults, bridge payloads, warnings, and isError

paths using msw.

Server/client boundaries: offline TD behavior, auth forwarding, timeout/retry,

event streaming, and transport setup.

Skip generated data, docs-only files, and import-only tests.

Phase 2 - Build tests

For parallel work, spawn tdmcp-coverage-writer agents with one seam each. Give each writer:

target file(s) and nearest existing test to mirror;
behavior to assert;
expected failure mode or branch to cover;
exact narrow command to run.

The lead is the single writer for shared config, package scripts, and harness docs. Do not let multiple agents edit the same test file.

Phase 3 - Verify

Run narrow tests first. Then run:

npm run typecheck
npm run build
./node_modules/.bin/biome check .
npm run coverage:harness
npm run validate:recipes
npm run test:bridge

If a gate fails, fix forward. Do not lower coverage thresholds, delete assertions, or exclude executable code to pass.

Phase 4 - Report

Write _workspace/coverage/wave-<date>.md with:

starting and ending coverage summary;
tests added and behaviors covered;
commands run;
PASS/FAIL/UNVERIFIED buckets;
next suggested gaps from _workspace/coverage/latest.md.

tdmcp-test-coverage-707e90— agent skill

Is tdmcp-test-coverage-707e90 safe to install?

tdmcp-test-coverage

Phase 0 - Context

Phase 1 - Select gaps

Phase 2 - Build tests

Phase 3 - Verify

Phase 4 - Report

Test scenarios

Audit the pieces. Scan the whole. Decide.