preset-embedded-rls
Review embedded analytics row-level security clauses, tenant filters, guest-token RLS rules, and external-viewer isolation for direct API workflows. Use only for direct API workflows; Do not use for MCP-only work.
Install
npx skills add https://github.com/preset-io/agent-skills/tree/master/plugins/preset-api-skills/skills/preset-embedded-rls
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install preset-io-agent-skills@llmmart
git clone https://github.com/preset-io/agent-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole preset-io/agent-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
preset-embedded-rls
Use before guest-token creation when embedded viewers need row-level security.
Always
- Auth and conventions come from
preset-api(JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. Consult metadata skills only when column validation is required. - Do not invent tenant identifiers, filters, dataset columns, or access rules.
- Treat RLS clauses as permission controls that can leak or hide customer data.
- Confirm every clause and intended viewer population before token creation.
- Do not validate with broad data-returning queries unless the user approves target and limit.
Decision Rules
- Classify embedded RLS review as plan-only safety work.
- Identify tenant and user filter safety issues.
- Require approval before clauses are used in token claims.
- Avoid mutating embedded RLS configuration.
Workflow Order
- Inspect embedded RLS clauses.
- Flag unsafe tenant and user filters.
- Summarize approval requirements.
- Stop before using clauses in tokens.
Retrieve
- Embedded RLS rule design and review: references/embedded-rls-rules.md
Files (agent-skills)
-
references
-
embedded-rls-rules.md 1.3 KB
Loading…
-
-
SKILL.md 1.4 KB
--- name: preset-embedded-rls description: Review embedded analytics row-level security clauses, tenant filters, guest-token RLS rules, and external-viewer isolation for direct API workflows. Use only for direct API workflows; Do not use for MCP-only work. --- # preset-embedded-rls Use before guest-token creation when embedded viewers need row-level security. ## Always - Auth and conventions come from `preset-api` (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. Consult metadata skills only when column validation is required. - Do not invent tenant identifiers, filters, dataset columns, or access rules. - Treat RLS clauses as permission controls that can leak or hide customer data. - Confirm every clause and intended viewer population before token creation. - Do not validate with broad data-returning queries unless the user approves target and limit. ## Decision Rules - Classify embedded RLS review as plan-only safety work. - Identify tenant and user filter safety issues. - Require approval before clauses are used in token claims. - Avoid mutating embedded RLS configuration. ## Workflow Order 1. Inspect embedded RLS clauses. 2. Flag unsafe tenant and user filters. 3. Summarize approval requirements. 4. Stop before using clauses in tokens. ## Retrieve - Embedded RLS rule design and review: [references/embedded-rls-rules.md](references/embedded-rls-rules.md)
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.