Name: ngrok
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

ngrok

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

Quality

68%

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/ngrok/SKILL.md

Quality

Content

75%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 copy-paste CLI commands and a clear connection workflow with validation checkpoints, losing points mainly to a redundant Ngrok overview and minor cross-reference/numbering inconsistencies.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph explaining what Ngrok is and the unexplained resource list are unnecessary since Claude already knows Ngrok.	3 / 5
Actionability	Fully executable, copy-paste ready CLI commands throughout (install, login, connection ensure, action run, request) with a flags table covering the common cases.	5 / 5
Workflow Clarity	Clear install→authenticate→connect→poll→search→run sequence with state-check checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but the 'skip to Step 2' reference and '1b' without a '1a' are inconsistent.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no external references needed, though the detailed clientAction state machine and flags table could be split into reference files for a skill of this length.	4 / 5
	Total	16 / 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' clause and a clearly distinct niche (Ngrok), but its capability statement is generic ('manage data, records, automate workflows') rather than naming concrete Ngrok actions.

Suggestions

Replace generic verbs with concrete Ngrok capabilities, e.g. 'Create and manage tunnels, reserved domains, endpoints, and IP restrictions' to lift specificity.

Add natural trigger variations users might say, such as 'tunnels', 'webhooks', 'public URL for local server', or 'ngrok endpoints', to improve trigger-term coverage.

Tighten the 'what' so it lists 2-3 specific Ngrok operations rather than abstract 'manage data' phrasing.

Dimension	Reasoning	Score
Specificity	Names the Ngrok domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete operations.	2 / 5
Completeness	Both a 'what' (manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Ngrok data') are present, though the 'what' is generic.	4 / 5
Trigger Term Quality	Includes the natural term 'Ngrok' and 'Ngrok data', but lacks common variations or synonyms beyond the single service name.	3 / 5
Distinctiveness Conflict Risk	Ngrok is a specific named service with a clear niche, so the trigger is distinct with minimal risk of conflicting with other skills.	5 / 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/ngrok/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.