CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/cross-tenant-data-leak-tests

Workflow-driven skill that emits the runtime CI gate of cross-tenant leak tests - the actual battery a multi-tenant codebase must pass on every PR. Defines the canonical test patterns (read-other-tenant-by-id, list-leak, spoofed-tenant-id-in-body, JWT-replay, FK-cross-tenant, unique-collision side channel, object-storage IDOR, search-index-direct-query, async-job-context-reload, cache-key-collision), the expected response codes per pattern (404 vs 403 disclosure trade-off), the Postgres-RLS-direct test patterns, and the CI integration (run with non-superuser non-BYPASSRLS role, fail the build on any leak). Use when implementing the actual leak-test suite (after tenant-leak-test-author produces the plan), when adding the CI gate to an existing project, or when investigating a leak finding.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

92%

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

An actionable, well-sequenced runtime test-suite skill with executable code, clear validation feedback loops, and a useful anti-patterns table. Its main weakness is that all content lives inline in a single large file with no bundle references for the sizable test battery.

Suggestions

Move the 10 canonical test templates and/or the CI integration YAML into referenced files (e.g. references/canonical-tests.md, references/ci-gate.yml) and keep SKILL.md as a concise overview pointing to them.

Link the named sibling skills (row-level-security-postgres-reference, tenant-leak-test-author) as navigable references or a short 'Related skills' subsection rather than only inline mentions.

Tighten the Overview and per-test convention prose slightly so the overview reads as a true summary rather than restating content detailed in Step 2.

DimensionReasoningScore

Conciseness

Dense, technical content that assumes Claude's competence — it never explains basic RLS or testing concepts — and each section earns its place, with minimal padding.

3 / 3

Actionability

Provides fully executable Python test functions, concrete SQL with explicit expected results, and a copy-paste-ready CI workflow YAML with exact role-setup commands.

3 / 3

Workflow Clarity

Steps 1-4 are clearly sequenced and Step 4 is an explicit diagnose-feedback loop with checkpoints (read assertion, check connection role, reproduce, check policy); the role-verification SQL and anti-patterns table reinforce error recovery.

3 / 3

Progressive Disclosure

No bundle files exist and the body is a large (~360 line) monolith; it is well sectioned but the extensive test battery and CI config could be split into referenced files rather than kept entirely inline.

2 / 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.

A highly specific, third-person description that clearly states what the skill produces and when to invoke it, with concrete pattern names and natural trigger terms. It is detailed without resorting to fluff or buzzwords.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and enumerates ten specific test patterns (read-other-tenant-by-id, list-leak, JWT-replay, etc.) plus expected response codes and CI role requirements.

3 / 3

Completeness

Explicitly answers both what (emits the leak-test battery, defines patterns, response codes, CI integration) and when ('Use when implementing...', 'when adding the CI gate...', 'when investigating a leak finding').

3 / 3

Trigger Term Quality

Uses natural phrases a user would actually say — 'leak test', 'CI gate', 'cross-tenant', 'investigating a leak finding', 'adding the CI gate' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (runtime cross-tenant leak tests) with distinct triggers and explicit handoff to sibling skill tenant-leak-test-author for planning, making conflicts unlikely.

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