zitadel-sdk-solid SKILL.md skillA
zitadel-sdk-solid from zitadel/nextgen is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zitadel/nextgen/zitadel-sdk-solid@git:20261018.decabadPins git:20261018.decabad in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zitadel/nextgen
- Path
packages/sdk-solid/skills/zitadel-sdk-solid/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261018.decabad, committed Oct 18, 2026
- First version recorded
- Oct 5, 2026
- Size
- 8,015 bytes
- Repository stars
- 27
- License
- AGPL-3.0
Integrate Zitadel authentication into a SolidJS app with `@zitadel/sdk-solid`. Use when the user wants to add Zitadel login, registration, logout, or a signed-in session card to an existing or custom Solid SPA (Vite, SolidStart, etc.) — wiring `configureZitadel` and the `<ZitadelLogin>` / `<ZitadelLogout>` / `<ZitadelSession>` components by hand rather than scaffolding from scratch.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# @zitadel/sdk-solid
Solid components that render the Zitadel auth UI inside a client-side SPA.
The package wraps the framework-agnostic `<zitadel-*>` web components as
real Solid components, so login, logout, and the signed-in session card are
JSX you drop into your routes.
## When to use
- **Fresh project:** prefer the CLI. `npx @zitadel/cli@alpha setup --framework solid`
scaffolds a wired Solid app (and the dev proxy) for you — see the
`zitadel-cli` skill. Don't hand-assemble what the CLI generates.
- **This skill:** an app that already exists, or a custom integration the
scaffold doesn't cover — adding auth to a Solid app you already have,
moving the components into your own routes, or wiring the config yourself.
## Install
`solid-js >= 1.6` is a peer dependency, and the published types need
TypeScript >= 5.0.
```sh
npm install @zitadel/sdk-solid@alpha
```
## Integrate
Configure once, then render the components. `configureZitadel` returns a
project handle you pass to each component.
```tsx
import { ZitadelLogin, configureZitadel } from '@zitadel/sdk-solid';
const project = configureZitadel({
projectId: import.meta.env.VITE_ZITADEL_PROJECT_ID,
…Read the whole file at its exact version.
How to install
mdr add zitadel/nextgen/zitadel-sdk-solid@sha256:7f330728f701bce9The line at the top of this page pins the label git:20261018.decabad, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_nkudb6zcyzu63kri)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 5, 2026 and Oct 18, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.decabad latest | 2026-10-18 | decabad | 8,015 B | A | view · diff |
| git:20261018.40470cc | 2026-10-18 | 40470cc | 4,478 B | A | view · diff |
| git:20261018.2f2b873 | 2026-10-18 | 2f2b873 | 4,056 B | A | view · diff |
| git:20261018.bdfca75 | 2026-10-18 | bdfca75 | 4,041 B | A | view · diff |
| git:20261005.46a366f | 2026-10-05 | 46a366f | 4,035 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8015 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zitadel/nextgen · 27 stars · license AGPL-3.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nkudb6zcyzu63kri GET https://markdownregistry.com/api/v1/resolve?ref=zitadel/nextgen/zitadel-sdk-solid GET https://markdownregistry.com/api/v1/blob/7f330728f701bce94c4efc34299161a976cb579e17a8325c0116dc3a9165de45
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.