Name: specify
Rating: 62.4 (1 reviews)
Author: membranedev

specify

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

Quality

74%

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

Quality

Content

82%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-ready commands and a well-validated connection workflow, organized into clear sections. The main weaknesses are minor verbosity, a broken step-numbering reference, and a single-file structure that could split reference material.

Suggestions

Fix the workflow numbering: the "skip to Step 2" reference points to no labeled Step 2 and the "1b" heading has no "1a", so relabel the connection sequence as explicit numbered steps (1. connect, 2. wait for READY, 3. search actions, 4. run).

Trim editorial padding such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" to improve token efficiency.

Consider moving the proxy flags table and detailed clientAction state handling into a references/ file linked from the body, which would shorten the main SKILL.md and strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with concise explanations, but contains minor over-explanation such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" that could be trimmed, fitting the efficient-with-minor-padding anchor.	4 / 5
Actionability	It provides copy-paste-ready, executable commands with clearly marked placeholders across install, auth, connect, search, run, and proxy flows, plus a flags table, fully covering the common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit validation checkpoints (poll for READY, handle CLIENT_ACTION_REQUIRED, re-poll, check CONFIGURATION_ERROR), but the "skip to Step 2" reference and an unanchored "1b" heading introduce a minor structural gap that keeps it below 5.	4 / 5
Progressive Disclosure	The body is well-organized into clearly labeled sections with no external references needed, but at ~139 lines (above the 50-line simple-skill threshold) and as a single monolithic file it lands at 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

66%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 covers both what and when and is tightly anchored to the distinct Specify niche, but its action list is generic and its trigger vocabulary is thin. Tightening the capabilities and adding natural trigger phrases would lift specificity and trigger_term_quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Specify capabilities users actually request, e.g. "search specimens, manage loans, generate collection reports".

Expand the trigger clause with natural phrasings users would say, e.g. "Use when the user wants to query Specify specimens, manage collection loans, or pull Specify records."

Dimension	Reasoning	Score
Specificity	The description names the Specify domain and a few action areas ("Manage data, records, and automate workflows"), but these are generic verbs rather than concrete capabilities, so it stops short of the several-specific-actions anchor at 4.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Specify data"), but the trigger clause could be more explicit and specific, landing at 4 rather than 5.	4 / 5
Trigger Term Quality	It repeats the relevant keyword "Specify" / "Specify data" in the trigger clause, but offers only that single domain term with no natural synonyms or variations users might say, matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The description is anchored to the named Specify application ("Specify integration", "interact with Specify data"), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	15 / 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/specify/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.