Plugin Claude Code
Plugin marketplace listing 1 plugin: spicedb-dev.
Plugin Claude Code
Plugin marketplace listing 1 plugin: spicedb-dev.
Agent
Use this agent to analyze codebases and identify where authorization checks should be added. Uses data flow analysis to find authorization boundaries. Examples.
Agent
Use this agent for phase 0 of a migration to SpiceDB - it scans both the source authorization model and the whole application codebase and returns a structured findings report (Class A/B/C) for the pre-flight gate to resolve. Launched by /spicedb-dev:migrate. Examples.
Agent
Use this agent to validate SpiceDB schemas, check best practices, and suggest improvements. Examples.
Command
Audit SpiceDB permission coverage -- reads your schema and scans the codebase to produce a matrix showing which permissions have code checks and which are unprotected.
Command
Interactive permission model design session for SpiceDB schemas.
Command
Convert permission model to SpiceDB schema (.zed file).
Command
Add SpiceDB permission checks and lookup operations to application code (CheckPermission, BulkCheckPermission, LookupResources, LookupSubjects).
Command
Add SpiceDB relationship writes and deletes to application code (WriteRelationships, DeleteRelationships).
Command
Add SpiceDB operations to application code (permission checks, relationship management, bulk operations, lookups).
Command
Rewrite a source system's client call sites into SpiceDB client calls, and add the SpiceDB client to the project.
Command
Migrate a live source system's relationship data into SpiceDB.
Command
Convert a source authorization model to a SpiceDB schema (.zed).
Command
Convert a source system's test/assertion files into SpiceDB validation YAML.
Command
Emit a differential harness that dual-runs SpiceDB beside a live source system, diffs disagreements safely, and turns confirmed agreements into regression tests.
Command
Migrate an application from another authorization system to SpiceDB - analyze, hold the pre-flight gate, and route through the conversion phases.
Command
Plan a SpiceDB authorization implementation -- scopes complexity, identifies the right starting phase, and writes an authorization-plan.md artifact with phased next steps and specific commands to run.
Command
Generate test data fixtures and test scenarios for permission model.
Command
Validate a SpiceDB schema (.zed file) using the schema-validator agent.
Skill Claude CodeCodex
Use when a user wants to plan, scope, or get started with adding authorization to their application - guides brainstorming to produce a phased implementation plan that incorporates the right skills and commands in sequence.
Skill Claude CodeCodex
Use when writing tests for SpiceDB authorization, generating test fixtures, designing positive/negative test scenarios, or verifying permission correctness - provides patterns for fixture generation, integration testing, and negative test coverage.
Skill Claude CodeCodex
Use when migrating an application from another authorization system (OpenFGA, Okta FGA) to SpiceDB - runs the phase pipeline that converts schema, data, application code, and tests, with a pre-flight gate that surfaces every blocking decision before conversion begins.
Skill Claude CodeCodex
Use when converting an OpenFGA, Okta FGA, or Auth0 FGA authorization model and application to SpiceDB - supplies the construct mapping, blocker catalog, identifier normalization, and code mapping needed to convert the schema, data, and application code.
Skill Claude CodeCodex
Use when implementing SpiceDB client calls, choosing a consistency model, handling errors and retries, or optimizing permission check performance - provides language-specific patterns for Go/TypeScript/Python with fail-safe error handling.