CtrlK
BlogDocsLog inGet started
Tessl Logo

ory

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

56

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

67%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 a well-structured, actionable guide to driving ORY through the Membrane CLI, with concrete commands and a clear connection-readiness workflow. It is slightly held back by introductory prose explaining ORY and authentication concepts Claude already knows.

Suggestions

Trim the opening ORY definition paragraph and the 'auth plumbing' justification; assume Claude knows what IAM/CLI tools are.

Add a brief example of parsing the `output` field from `membrane action run` so users know what a successful result looks like.

Add a short table of contents or one-line section pointers at the top so Claude can jump to the relevant workflow step quickly.

DimensionReasoningScore

Conciseness

Mostly efficient with executable commands, but the opening ORY definition paragraph and prose like 'so you can focus on the integration logic rather than auth plumbing' explain context Claude largely already knows.

3 / 5

Actionability

Provides concrete, copy-pasteable membrane commands (login, connection ensure, action list/run, request proxy) with a flags table, with only minor gaps such as minimal guidance on interpreting the output field.

4 / 5

Workflow Clarity

Clear sequence from install -> login -> connect -> poll for readiness -> search -> run, with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to split out; minor gaps are the lack of an explicit TOC or pointers for deeper reference material.

4 / 5

Total

15

/

20

Passed

Description

62%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 answers both 'what' and 'when' in third person and is anchored to a specific product (ORY), but its named actions are generic rather than concrete ORY capabilities. Tightening the action list to ORY-specific terms would lift specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with ORY-specific capabilities (e.g., 'manage identities, OAuth2 clients, sessions, and consent flows').

Add natural user phrasing and synonyms to the trigger clause (e.g., 'Use when the user mentions ORY, Ory Kratos, Keto, Hydra, or OAuth2/identity workflows').

Drop the redundant 'Manage data, records' phrasing, which reads as filler rather than a concrete capability.

DimensionReasoningScore

Specificity

Names the ORY domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and not ORY-specific or comprehensive.

3 / 5

Completeness

Explicitly states what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with ORY data'), though the 'when' is fairly generic.

4 / 5

Trigger Term Quality

Includes the 'ORY' keyword and a 'Use when...' trigger ('interact with ORY data'), but lacks common synonyms or variations a user might naturally say.

3 / 5

Distinctiveness Conflict Risk

The ORY-specific trigger makes it mostly distinct from other skills, with only minor overlap risk against generic data-management skills.

4 / 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.