CtrlK
BlogDocsLog inGet started
Tessl Logo

zitadel

ZITADEL integration. Manage data, records, and automate workflows. Use when the user wants to interact with ZITADEL data.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/zitadel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is highly actionable with executable CLI commands and a clear connection-state workflow, but it is held back by a padded intro, an inlined reference-style feature list, and a broken 'Step 2' numbering reference.

Suggestions

Fix the workflow numbering: label the steps explicitly (Step 1: connect, Step 2: search/run actions) or remove the dangling 'Step 2' and '1b' references.

Move the ZITADEL Overview feature hierarchy into a separate reference file and link to it, keeping SKILL.md as a lean overview.

Trim the marketing-style intro paragraph about 'simplifying the process of building secure applications' to a one-line factual description.

DimensionReasoningScore

Conciseness

The CLI command sections are efficient, but the marketing-style intro paragraph ('simplifying the process of building secure applications') and the long inlined feature hierarchy are unnecessary or could be tightened.

3 / 5

Actionability

Commands are copy-paste ready with full flags and JSON examples covering install, login, connection ensure, polling, action list/run, and proxy requests across the common cases.

5 / 5

Workflow Clarity

There is a clear install-to-run sequence with explicit state-checking and polling feedback loops, but the body references 'Step 2' and a '1b' subsection with no labeled Step 1/2, leaving a minor structural gap.

4 / 5

Progressive Disclosure

Sections are organized, but the inlined ZITADEL feature/API hierarchy is reference-like content that would sit better in a separate file, and no external references are used to split the material.

3 / 5

Total

15

/

20

Passed

Description

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

The description has an explicit 'Use when' trigger and a distinctive named-product anchor, but its capability statement is generic ('manage data, records, automate workflows') rather than naming concrete ZITADEL actions.

Suggestions

Replace generic actions with concrete ZITADEL operations, e.g. 'manage users, organizations, projects, applications, and authentication policies'.

Add feature-level trigger keywords (users, organizations, projects, OIDC, roles) alongside 'ZITADEL' so the description surfaces for varied user phrasings.

DimensionReasoningScore

Specificity

It names the domain (ZITADEL) but the actions 'Manage data, records, and automate workflows' are minimal and generic rather than concrete ZITADEL-specific operations like users, organizations, projects, or authentication.

2 / 5

Completeness

Both a 'what' (manage data/records/workflows for ZITADEL) and an explicit 'when' ('Use when the user wants to interact with ZITADEL data') are present, though the 'what' is generic.

4 / 5

Trigger Term Quality

'ZITADEL' and 'ZITADEL data' are natural terms a user would say, but coverage is thin with no synonyms or feature-level keywords (users, orgs, auth, projects) to broaden triggering.

3 / 5

Distinctiveness Conflict Risk

ZITADEL is a specific named product and the trigger is tied to it, giving a clear niche with minimal risk of firing for unrelated skills.

5 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.