multi-tenant-discovery-re

Determine multi-tenant architecture from captured reverse-engineering evidence.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill multi-tenant-discovery-re
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-tenant-discovery-re
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/operacao/multi-tenant-discovery-re
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill multi-tenant-discovery-re

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid false assumptions about multi-tenant architecture during reverse engineering, especially when SaaS systems expose clinic, company, or tenant identifiers in URLs, payloads, and captured page state.

Core Features & Use Cases

  • Tenant model discovery: Distinguishes database-per-tenant, shared database, and schema-per-tenant patterns using captured evidence.
  • Evidence-first analysis: Checks page source, login flow, API payloads, and configuration objects before asking the client questions.
  • Architecture documentation: Turns findings into a clear blueprint for how tenant isolation and clinic-level relationships actually work.
  • Use Case: Use this when analyzing a legacy healthcare or SaaS platform and you need to determine whether clinic IDs are isolation boundaries or organizational foreign keys.

Quick Start

Analyze the captured login pages, payloads, and JavaScript objects for tenant indicators and summarize the most likely multi-tenant model.

Frequently Asked Questions about multi-tenant-discovery-re

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine the multi-tenant architecture of a SaaS system from reverse engineering evidence?

To determine multi-tenant architecture from reverse engineering, analyze captured login flows, API payloads, and JavaScript objects for tenant identifiers. This Skill verifies database isolation patterns by checking configuration artifacts before finalizing architectural decisions.

What is the difference between a tenant identifier and an organizational foreign key in a SaaS database?

A tenant identifier enforces database isolation boundaries in multi-tenant SaaS architectures, while an organizational foreign key merely links data hierarchically. This Skill analyzes captured page state and payloads to distinguish true isolation boundaries from standard relationships.

How do I identify database-per-tenant versus shared database patterns when analyzing a legacy platform?

Identifying database-per-tenant versus shared database patterns requires evidence-first analysis of captured login pages, API payloads, and configuration objects. This Skill checks these artifacts to distinguish schema-per-tenant, database-per-tenant, and shared database isolation models.

Can I use captured API payloads and page source to verify clinic-level tenant isolation in healthcare platforms?

Yes, you can verify clinic-level tenant isolation by analyzing captured API payloads and page source for tenant indicators. This Skill processes reverse-engineering evidence to confirm whether clinic IDs function as true database isolation boundaries or organizational foreign keys.

What evidence do I need to discover tenant models during SaaS system cloning?

Discovering tenant models during SaaS system cloning requires captured login flow cues, API payloads, page source, and configuration artifacts. This Skill synthesizes these reverse-engineering inputs to produce a clear architectural blueprint of tenant isolation.