CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/cross-tenant-data-leak-tests

Use when designing or adding tenant isolation tests to a multi-tenant app, adding a CI leak gate, or investigating a leak. Inventories tenant-bearing surfaces, then tests read-by-ID, list leaks, spoofed tenant IDs, JWT replay, storage IDOR, search, jobs and caches, plus Postgres row-level security.

Quality

92%

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

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

An exceptionally actionable skill: executable test code for every pattern, explicit sequencing with validation checkpoints and a failure-diagnosis feedback loop, and clearly signaled references. The minor costs are a slightly long body with a redundant trailing References section and second-level navigation to the per-engine reference files.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, load-bearing specifics (the RLS connection-role matrix, "Foreign key constraint checks, Unique constraint checks... bypass RLS", the PgBouncer transaction-pooling caveat) with no basic-concept padding. Minor trims exist — the References section duplicates links already given inline (the OWASP URL appears twice) and Test 8's stacked comments are slightly chatty — so it is efficient but not perfectly lean.

4 / 5

Actionability

Fully executable guidance throughout: complete copy-paste Python tests for all eleven patterns, a verification query with expected output ("Expect: rolsuper=f, rolbypassrls=f"), a working tenant_tx context manager, concrete policy DDL, and framework-specific config locations for Django, Rails, and Spring Boot.

5 / 5

Workflow Clarity

Sequencing is explicit ("Plan first, then implement" → Steps 1–4), Step 1 embeds a validation checkpoint, and Step 4 is a genuine error-recovery feedback loop ending with "Write the minimal regression test before fixing"; the anti-patterns table doubles as a checklist. Validation is present for risky operations, so the workflow cap does not apply.

5 / 5

Progressive Disclosure

References are well-signaled inline at point of use ("ready-made skeletons are in [references/framework-skeletons.md]", "The full workflow is in [references/ci-workflow.md]") and all referenced files exist, one primary level deep. However, the ~470-line body inlines the entire eleven-test battery, and several bundle files (mysql-mariadb.md, sqlserver.md, vitess.md, cockroachdb.md, models.md, test-surfaces.md) are reachable only second-level through row-level-security.md or other-engines.md rather than from SKILL.md itself — good structure with minor organization gaps.

4 / 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 strong description: explicit 'Use when' triggers, a concrete third-person capability list mirroring the skill's actual test battery, and a distinctive multi-tenant isolation niche. The only weakness is that a few natural synonyms (cross-tenant, RLS, BOLA) are absent, keeping trigger-term coverage just short of comprehensive.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "Inventories tenant-bearing surfaces, then tests read-by-ID, list leaks, spoofed tenant IDs, JWT replay, storage IDOR, search, jobs and caches, plus Postgres row-level security" — giving comprehensive coverage of the skill's capabilities, matching the top anchor rather than the 'several actions with minor gaps' anchor.

5 / 5

Completeness

It explicitly answers both questions: "Use when designing or adding tenant isolation tests to a multi-tenant app, adding a CI leak gate, or investigating a leak" gives concrete 'when' triggers, and the second sentence gives a clear third-person 'what' (inventory surfaces, then test the enumerated patterns).

5 / 5

Trigger Term Quality

Good natural-keyword coverage: "tenant isolation tests", "multi-tenant app", "CI leak gate", "investigating a leak", "JWT replay", "IDOR", "Postgres row-level security" are phrases users would plausibly say. A few natural synonyms are missing (e.g., "cross-tenant", "RLS" abbreviation, "BOLA"), which falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — tenant-isolation leak testing with CI gating — with trigger phrases unlikely to fire for unrelated testing, Postgres, or CI skills, so conflict risk is minimal.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page