Name: tick
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

tick

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

Quality

66%

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/tick/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 an efficient, actionable integration guide with concrete commands and a solid connection-state feedback loop. Its main weaknesses are minor redundancy, dangling "Step 2" references, and a few unexplained placeholders.

Suggestions

Fix the "skip to Step 2" references by labeling the corresponding section (e.g. "Step 2: Search for actions") or removing the cross-references.

Remove the duplicated `membrane action list` command in "Popular actions" or fold it into the earlier "Searching for actions" section.

Trim the auth-plumbing commentary ("so you can focus on the integration logic rather than auth plumbing") to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, tables, and state-transition bullets, with only minor padding (e.g. "so you can focus on the integration logic rather than auth plumbing") and a duplicated action-list command in the "Popular actions" section.	4 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxy requests with a full flag table; minor gaps remain around resolving placeholders like CONNECTION_ID inline.	4 / 5
Workflow Clarity	The install→auth→connect→search→run sequence is clear and includes a polling feedback loop with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED), but "skip to Step 2" references point to no labeled Step 2.	4 / 5
Progressive Disclosure	Content is organized under clear section headers in a single self-contained file with no external references; structure is good though the proxy/clientAction detail could arguably live in a separate reference.	4 / 5
	Total	16 / 20 Passed

Description

57%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 identifies the Tick product niche and includes an explicit "Use when" trigger, but its capability verbs are generic rather than reflecting Tick's actual time-tracking and project-management actions. Tightening the action list to concrete Tick operations would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Tick actions, e.g. "Log time entries, manage projects and tasks, and pull reports".

Expand the trigger phrase to cover natural variations users say, e.g. "Use when the user wants to track time, log hours, or manage Tick projects and tasks".

Mention key Tick entities (entries, projects, tasks, clients) so the description doubles as a distinctiveness signal.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Tick integration") but its actions are generic ("Manage data, records, and automate workflows") rather than concrete Tick-specific operations like time tracking, entries, tasks, or projects.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and a "when" ("Use when the user wants to interact with Tick data") are present, though the trigger is somewhat generic.	4 / 5
Trigger Term Quality	It includes the natural term "Tick data" in the trigger clause, but coverage is limited to that single phrase with no synonyms or common variations users might say.	3 / 5
Distinctiveness Conflict Risk	The named product "Tick" gives it a clear niche with distinct triggers, but the generic verbs ("manage data, records") create minor overlap risk with other integration skills.	4 / 5
	Total	13 / 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/tick/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.