Name: myotpapp
Rating: 55.2 (1 reviews)
Author: membranedev

myotpapp

MyOTP.App integration. Manage Users, Organizations, Roles, Goals, Filters, Projects. Use when the user wants to interact with MyOTP.App data.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 highly actionable CLI commands with a well-sequenced, checkpoint-driven connection workflow, but is somewhat padded with inferable prose and keeps all detail inline rather than splitting reference material into bundle files.

Suggestions

Trim inferable explanations (e.g., the auth-plumbing sentence and the MFA product blurb) so every line earns its tokens.

Move the proxy-flags reference table and the popular-actions discovery detail into a references/ file linked one level deep from SKILL.md.

Add an explicit validation/retry checkpoint after `membrane action run` for error cases (non-READY states, failed action output).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes prose that restates CLI behavior Claude can infer (e.g., "so you can focus on the integration logic rather than auth plumbing") and a product blurb that adds mild padding.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure/get, action list/run, request) with real flags and a JSON-input example, leaving only minor gaps such as placeholder CONNECTION_ID/actionId resolution.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop, with only minor validation gaps around action-result handling.	4 / 5
Progressive Disclosure	Sections are well organized with headers, but all content is inlined in SKILL.md with no bundle files or one-level-deep references; the proxy-flag table and popular-actions detail could live in separate reference files.	3 / 5
	Total	14 / 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 explicitly and targets a distinct product niche, but relies on a single generic action verb and a somewhat generic trigger phrase rather than concrete natural-language triggers.

Suggestions

Replace the single verb "Manage" with several concrete actions (e.g., "Create, update, and list Users, Organizations, Roles...") to raise specificity.

Expand the trigger clause with natural user phrasings such as "when the user wants to create or look up a MyOTP.App user, organization, role, or goal".

Add file-extension or entity-synonym keywords (e.g., MFA codes, OTP tokens) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The single generic verb "Manage" is applied to six named resources (Users, Organizations, Roles, Goals, Filters, Projects), naming the domain and several concrete targets but only one action rather than multiple specific actions.	3 / 5
Completeness	It has both a clear "what" ("Manage Users, Organizations, Roles, Goals, Filters, Projects") and an explicit "when" ("Use when the user wants to interact with MyOTP.App data"), though the trigger could be more specific.	4 / 5
Trigger Term Quality	The "Use when the user wants to interact with MyOTP.App data" clause and the enumerated entity names provide some relevant keywords, but lack common natural variations or synonyms a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The product name MyOTP.App plus the specific resource list carves out a distinct niche with low overlap risk, though the generic "interact with data" phrasing leaves minor ambiguity.	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/myotpapp/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.