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

tideways

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

Quality

62%

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/tideways/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 content is highly actionable with copy-paste CLI commands and a genuine state-polling feedback loop for connection setup. It loses points to explanatory padding and to being a single monolithic file that inlines reference material rather than progressing to separate files.

Suggestions

Trim the marketing-style intro and 'so you can focus on the integration logic' framing; keep only what tells Claude how to operate the Membrane CLI.

Move the proxy flag table and the clientAction object schema into a references file (e.g. references/proxy-and-states.md) and link to it from the body, so SKILL.md stays a lean overview.

Fix the step numbering ('Step 2', '1b') into a single explicit numbered connection sequence so the READY/BUILDING/CLIENT_ACTION_REQUIRED branches are unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly focused command examples, but the intro ('It helps developers identify and resolve performance bottlenecks... It is used by PHP developers and operations teams...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are explanatory padding Claude does not need.	3 / 5
Actionability	Concrete, executable commands cover the full lifecycle (install, login, connection ensure, action list/run, request proxy) with a complete flag table; the only gaps are unsubstituted placeholders (CONNECTION_ID, QUERY) and no example of parsing the JSON output.	4 / 5
Workflow Clarity	The connection flow has real validation checkpoints and feedback loops (poll with --wait, inspect state, handle CLIENT_ACTION_REQUIRED, then re-poll), but the 'skip to Step 2' and '#### 1b' labels reference steps that are not clearly numbered, slightly muddying the sequence.	4 / 5
Progressive Disclosure	The single ~145-line file is well sectioned, but there are no references at all and reference-style material (the proxy flag table, the detailed clientAction object schema) is inlined rather than split into separate files, so structure could be better organized.	3 / 5
	Total	14 / 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 correctly answers both what the skill does and when to use it, anchored to a distinctive niche tool. Its weakness is generic action language and thin trigger-term coverage that omits the profiling/monitoring synonyms a user would naturally say.

Suggestions

Replace the generic verbs ('Manage data, records, and automate workflows') with concrete Tideways actions, e.g. 'Inspect traces, analyze spans, triage alert groups, and monitor PHP application performance.'

Broaden the 'Use when' clause to cover natural synonyms: 'Use when the user wants to profile a PHP app, investigate traces or spans, review Tideways alerts, or analyze performance bottlenecks.'

Keep the distinctive 'Tideways' trigger but pair it with secondary keywords (profiler, APM, PHP performance monitoring) so it surfaces for users who name the problem rather than the tool.

Dimension	Reasoning	Score
Specificity	The domain is named ('Tideways integration') but the listed actions — 'Manage data, records, and automate workflows' — are generic verbs rather than concrete Tideways-specific capabilities like inspecting traces, analyzing spans, or triaging alerts.	2 / 5
Completeness	Both 'what' (Tideways integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Tideways data') are present, but the trigger guidance is narrow and could name more concrete scenarios.	4 / 5
Trigger Term Quality	The natural keyword 'Tideways' and the phrase 'interact with Tideways data' are present, but common synonyms users would say (PHP profiling, performance monitoring, APM, traces, profiler) are missing.	3 / 5
Distinctiveness Conflict Risk	Tideways is a specific niche PHP-monitoring tool, and the trigger is tied to the distinctive term 'Tideways', giving it a clear niche with minimal risk of firing for unrelated 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/tideways/SKILL.md
Commit: f484c82

Reviewed: 4 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.