CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/tenant-isolation-models-reference

Pure-reference catalog of tenant-isolation models for B2B SaaS. Defines the isolation continuum from full-isolation (separate compute + data + network per tenant) to fully-shared (one deployment, tenant_id discriminator), names the canonical models (Microsoft's automated-single-tenant / fully-multitenant / vertically-partitioned / horizontally-partitioned; AWS Well-Architected's silo / pool / bridge framing; deployment-stamps / supertenants terminology), enumerates the trade-offs (cost, blast radius, noisy neighbor, compliance, scale limits), and lists the test surfaces each model creates (cross-tenant data leak, tenant-id propagation, deployment-routing). Use as the model-selection reference when designing or auditing tenant isolation. Consumed by tenant-leak-test-author, cross-tenant-data-leak-tests.

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.

A well-structured pure-reference skill: dense tables, concrete anti-pattern fixes, and clean one-level-deep references to real bundle files. Its only weakness is mild verbosity in the Overview, where sourced-but-editorial framing and a clause redundant with the description could be trimmed.

Suggestions

Trim the Overview's opening framing ('the foundational concern of every B2B SaaS architecture... potentially unrecoverable event') to the sourced continuum thesis, since the importance of tenant isolation is already known to Claude.

Drop or fold 'it executes nothing' — the description already establishes this is a pure-reference catalog, so the body need not restate it.

DimensionReasoningScore

Conciseness

The body is mostly dense reference material (compact tables, concrete anti-pattern/fix pairs), but the Overview opens with sourced-yet-editorial framing about tenant isolation being 'the foundational concern of every B2B SaaS architecture' — a concept Claude already knows — and the clause 'it executes nothing' duplicates the description's 'Pure-reference catalog', so it could be tightened.

2 / 3

Actionability

As an instruction-only reference it carries no code, but the guidance is concrete and specific: the anti-patterns table gives explicit fixes ('Push the filter to the database (RLS) or row-attribute IAM'; 'Always derive tenant_id from authenticated JWT/session, never from request payload') and the enforcement primitives name exact mechanisms (auth.jwt() claims, ABAC tags tenant-id=<x>, per-tenant KMS keys).

3 / 3

Workflow Clarity

There is no multi-step destructive workflow to sequence (the skill 'executes nothing' and is consumed by other skills), so the simple-skill exemption applies: the single reference purpose is unambiguous and the body is organized into clearly labeled, logically ordered sections.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview that offloads per-model when-to-choose detail and the test-surface mapping to two real, one-level-deep, well-signaled bundle files ([references/models.md], [references/test-surfaces.md]), both of which exist and are appropriately split from the overview.

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.

A strong description: third-person voice, concrete enumerated actions, explicit 'Use when...' trigger guidance, natural domain keywords, and a distinct niche clarified by its named consumer skills. No notable weaknesses against the rubric.

DimensionReasoningScore

Specificity

It lists multiple specific concrete actions — 'Defines the isolation continuum', 'names the canonical models', 'enumerates the trade-offs (cost, blast radius, noisy neighbor, compliance, scale limits)', 'lists the test surfaces each model creates' — rather than vague language.

3 / 3

Completeness

It explicitly answers both what ('Pure-reference catalog... Defines... names... enumerates... lists...') and when ('Use as the model-selection reference when designing or auditing tenant isolation'), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Natural terms a SaaS architect would actually say are well covered — 'tenant-isolation models', 'B2B SaaS', 'designing or auditing tenant isolation', 'cross-tenant data leak', 'tenant-id propagation' — matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (the model-selection reference for tenant isolation) and disambiguates from sibling skills by naming its consumers ('Consumed by tenant-leak-test-author, cross-tenant-data-leak-tests'), so it is unlikely to trigger for the wrong skill.

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