CtrlK
BlogDocsLog inGet started
Tessl Logo

passcreator

Passcreator integration. Manage Users, Organizations. Use when the user wants to interact with Passcreator 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/passcreator/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 content is actionable and well-structured with concrete CLI commands and a clear connection workflow including validation checkpoints, but it carries some introductory padding and a broken step cross-reference.

Suggestions

Trim the opening descriptive paragraph about what Passcreator is and the "auth plumbing" aside to improve token efficiency.

Label "Step 2" explicitly or remove the dangling "Skip to Step 2" references so the workflow sequence is unambiguous.

Provide at least one fully-resolved example command (with a real actionId and connectionId value) to push actionability toward copy-paste-ready.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes unnecessary padding such as the introductory paragraph describing what Passcreator is and phrases like "so you can focus on the integration logic rather than auth plumbing," matching the mostly-efficient-but-could-be-tightened anchor.

3 / 5

Actionability

It provides concrete, executable commands throughout (install, login, connection ensure, action run, request) with flag tables, though placeholders like CONNECTION_ID and actionId leave minor gaps versus fully copy-paste-ready examples.

4 / 5

Workflow Clarity

The install→authenticate→connect→search→run sequence is clear with polling checkpoints and a feedback loop for CLIENT_ACTION_REQUIRED, but a dangling "Skip to Step 2" reference (Step 2 is never labeled) is a minor sequencing gap.

4 / 5

Progressive Disclosure

The single SKILL.md is organized into well-labeled sections with no nested references and all content inline at one level; it is over 50 lines so the simple-skill 5 does not apply, but structure and navigation are good.

4 / 5

Total

15

/

20

Passed

Description

66%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 and is clearly niche-scoped to Passcreator, but the capability verbs are generic and the trigger phrasing lacks natural synonyms or concrete user-language variations.

Suggestions

Replace the generic verb "Manage" with specific actions (e.g., "Create and manage Users, Organizations, Teams, and Passes").

Expand the trigger clause with concrete user phrases (e.g., "Use when the user wants to create or manage Passcreator cards, passes, users, or teams").

List the main entities (Card, Pass, Event, Statistics) covered by the skill to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Manage Users, Organizations" names the Passcreator domain and two concrete entities, but the verb "Manage" is generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the 4-5 anchors.

3 / 5

Completeness

Both what ("Passcreator integration. Manage Users, Organizations.") and when ("Use when the user wants to interact with Passcreator data.") are present and explicit, though the when clause could be more specific with concrete trigger phrases.

4 / 5

Trigger Term Quality

The trigger "Use when the user wants to interact with Passcreator data" surfaces the brand keyword but offers only one generic phrasing, missing natural variations like creating cards, managing passes, or teams that a user would actually say.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to a named niche (Passcreator) with brand-specific triggers, so overlap with other skills is minimal.

5 / 5

Total

15

/

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.