Name: chaser
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

chaser

Chaser integration. Manage Organizations, Users, Projects. Use when the user wants to interact with Chaser data.

Quality

71%

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

Quality

Content

81%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 a strong, highly actionable CLI integration guide with a clear validated workflow and feedback loops. Its main weakness is mild verbosity in the intro and best-practices prose, plus bulk reference tables kept inline.

Suggestions

Trim the introductory paragraph defining what Chaser is and tighten the best-practices bullets to remove explanatory filler.

Move the full "Popular actions" table and the proxy flag reference into a separate reference file, keeping only key examples inline.

Resolve the dangling "skip to Step 2" reference by labeling the next section explicitly or removing the step numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it spends tokens explaining what Chaser is ("Chaser is a sales pipeline management and automation tool...") and includes padded best-practices prose ("This will burn less tokens and make communication more secure"), so it could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case — install, login, connection ensure, polling get, action list/run with JSON input, and proxy requests with a full flag table — fully executable with concrete examples.	5 / 5
Workflow Clarity	The sequence (Install → Authenticate → Connect → poll for READY → Search → Run → Proxy) is explicit, with validation checkpoints and a feedback loop on CLIENT_ACTION_REQUIRED ("poll again... to check if the state moved to READY").	5 / 5
Progressive Disclosure	The file is well-organized into clear headed sections with no nested references, but at over 50 lines it inlines bulk content (the 23-row Popular actions table and proxy flag table) that could live in separate reference files.	4 / 5
	Total	17 / 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 cleanly answers both what the skill does and when to use it, anchored to a specific named app. It is held back by a single generic action verb ("Manage") and limited trigger-term variety.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List, create, update, and delete Organizations, Users, and Projects."

Add natural trigger phrases and synonyms, e.g. "Use when the user mentions Chaser, sales pipeline data, invoices, or customers."

Expand the "when" clause with multiple concrete triggers to push completeness toward an explicit multi-trigger form.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Organizations, Users, Projects" name the domain and three resources, but the single generic verb "Manage" is one abstract action rather than several concrete CRUD actions, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states a clear "what" ("Chaser integration. Manage Organizations, Users, Projects.") and an explicit "when" ("Use when the user wants to interact with Chaser data."), though the trigger could be more specific with multiple concrete phrases.	4 / 5
Trigger Term Quality	"Chaser" plus "Organizations, Users, Projects" and "interact with Chaser data" provide relevant keywords, but common synonyms or natural variations users might say are missing, fitting the anchor for some relevant keywords without variations.	3 / 5
Distinctiveness Conflict Risk	The named app "Chaser" carves a clear niche with low conflict risk, but the generic "Manage Organizations, Users, Projects" could overlap with other CRM/integration skills, so it is mostly distinct with minor overlap risk.	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/chaser/SKILL.md
Commit: f484c82

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