Name: osticket
Rating: 56.8 (1 reviews)
Author: membranedev

osticket

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/osticket/SKILL.md

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 delivers strong actionable CLI guidance with a well-sequenced connection workflow and explicit state-handling checkpoints, scoring well on actionability and workflow clarity. It is held back mainly by a redundant intro paragraph explaining osTicket and some reference-style material that could be split into bundle files.

Suggestions

Remove or trim the opening paragraph explaining what osTicket is; Claude already knows this and it costs tokens.

Add an explicit 'Step 2: Search for actions' label so the 'skip to Step 2' reference resolves, or restructure the connection flow as a numbered checklist.

Standardize invocation (membrane vs npx @membranehq/cli) and consider moving the proxy flag table into a references/ file for cleaner progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and flag tables, but it opens with an unnecessary paragraph explaining what osTicket is ('an open-source ticketing system used for managing customer support requests...') that Claude already knows, plus some prose padding around Membrane auth.	3 / 5
Actionability	Concrete, copy-paste-ready commands appear throughout (install, login, connection ensure, action list/run, request) with real flags and JSON examples; minor gaps include the membrane vs npx invocation inconsistency and unresolved placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The install→login→connection ensure→poll→handle client action→search→run sequence is clear with explicit state-validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, though the referenced 'Step 2' is never explicitly labeled.	4 / 5
Progressive Disclosure	Content is well-sectioned into Overview, Working with OsTicket, Authentication, Connecting, Searching, Popular actions, Proxy, and Best practices; a single-file CLI reference is appropriate, though the proxy flag table and connection-state reference could be externalized.	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 is third-person and answers both what and when with an explicit 'Use when...' clause, but it leans on generic action verbs and a single trigger keyword rather than concrete OsTicket capabilities and natural synonyms. Stronger distinctiveness and completeness would come from naming specific entities (tickets, users, organizations) and richer trigger phrases.

Suggestions

Replace generic verbs with concrete OsTicket capabilities, e.g. 'Create and manage support tickets, users, and organizations; automate ticket workflows.'

Expand the trigger clause with natural terms users say: 'Use when the user wants to manage support tickets, help desk requests, or OsTicket records.'

Mention file/record types or ticket-thread concepts to improve specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the OsTicket domain and lists several action verbs ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete OsTicket-specific capabilities like creating tickets or managing users.	3 / 5
Completeness	Both 'what' (OsTicket integration, manage data/records/workflows) and 'when' ('Use when the user wants to interact with OsTicket data') are explicitly stated, though the 'when' trigger is somewhat generic rather than enumerating concrete scenarios.	4 / 5
Trigger Term Quality	'OsTicket' is a strong natural keyword and the trigger 'interact with OsTicket data' is present, but common synonyms users would say ('tickets', 'support requests', 'help desk') are missing.	3 / 5
Distinctiveness Conflict Risk	OsTicket is a clearly distinct application niche with a brand-anchored trigger, but the generic 'manage data, records, and automate workflows' action list creates minor overlap risk with other CRM/data skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/osticket/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.