CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/tenant-onboarding-test-author

Workflow-driven skill that authors a test suite for tenant provisioning and offboarding: account creation, isolation at creation (no cross-tenant bleed from a new tenant's first API call), default resource quotas, billing record linkage, seed and default data correctness, idempotent re-provisioning, and teardown with full data deletion. Walks through mapping provisioning surfaces, generating test cases per surface, emitting the test suite skeleton (pytest / Jest / JUnit / Go test), and producing a coverage matrix. Use when a new tenant onboarding flow is introduced or changed, when the offboarding pipeline is modified, or when auditing provisioning coverage before a compliance review. Distinct from cross-tenant-data-leak-tests (leak-test planning + runtime CI gate): this skill covers the provisioning lifecycle, not steady-state access control.

69

Quality

87%

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

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

A well-structured, actionable skill body with clear sequencing and excellent progressive disclosure into real reference files. The main weaknesses are mild redundancy across the overview/How-to-use/Step sections and the absence of an explicit validation retry loop.

Suggestions

Collapse the overlap between the Overview 5-step list, the 'How to use' list, and the Step 1-5 sections into a single canonical workflow to trim tokens.

Add an explicit validation feedback loop (run suite -> if failures, diagnose against the Anti-patterns table -> fix -> re-run) to lift workflow clarity toward the top anchor.

Merge the two duplicate 'cross-tenant-data-leak-tests' rows in the Differentiation table into a single row covering both the steady-state and CI-gate roles.

DimensionReasoningScore

Conciseness

Mostly lean and it does not explain basic concepts Claude already knows, but the overview's 5-step list, the 'How to use' 6-step list, and the Step 1-5 sections restate overlapping material, and the Differentiation table duplicates the cross-tenant-data-leak-tests row — minor trim opportunities keep it just under lean.

4 / 5

Actionability

Provides a concrete naming convention ('test_<surface>_<scenario>_<expected>()'), example test names, a fixtures table, framework selection table, a coverage matrix template, and a worked example with a real assertion, but the bulk of executable test code lives in the referenced skeleton file rather than inline.

4 / 5

Workflow Clarity

A clearly sequenced five-step process with real checkpoints (empty matrix cells flagged as gaps to justify, cross-check the Anti-patterns table, run as a non-privileged app role), though it lacks an explicit validate->fix->retry feedback loop.

4 / 5

Progressive Disclosure

The body is an overview that points to three real, well-signaled, one-level-deep references (provisioning-surface-map.md, provisioning-test-scenarios.md, test-skeleton-examples.md) with no nested references, matching the top anchor.

5 / 5

Total

17

/

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 high-quality description that clearly states concrete capabilities, gives explicit 'Use when' trigger guidance, and explicitly differentiates itself from the closely related leak-tests skill. Minor room only in trigger-term synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the lifecycle ('account creation', 'isolation at creation', 'default resource quotas', 'billing record linkage', 'seed and default data correctness', 'idempotent re-provisioning', 'teardown with full data deletion') plus workflow steps ('mapping provisioning surfaces', 'emitting the test suite skeleton (pytest / Jest / JUnit / Go test)', 'producing a coverage matrix'), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what ('authors a test suite for tenant provisioning and offboarding') and when ('Use when a new tenant onboarding flow is introduced or changed...'), with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say are present ('when a new tenant onboarding flow is introduced or changed', 'when the offboarding pipeline is modified', 'auditing provisioning coverage before a compliance review'), but a few common synonyms/variants are missing, so it sits just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

An explicit boundary clause ('Distinct from cross-tenant-data-leak-tests ... this skill covers the provisioning lifecycle, not steady-state access control') carves a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents