Name: griffin
Rating: 59.2 (1 reviews)
Author: membranedev

griffin

Griffin integration. Manage data, records, and automate workflows. Use when the user wants to interact with Griffin 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/griffin/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 a practical, command-heavy integration guide with a well-sequenced connection workflow and real error-recovery loops. Its main weaknesses are a 'Popular actions' section that underdelivers, minor padding, and slightly inconsistent step numbering.

Suggestions

Populate 'Popular actions' with concrete Griffin action names and example invocations rather than restating the discovery command.

Fix the step numbering (label 'Step 1: Connect' explicitly so '1b' and 'Step 2' have a clear parent) to remove navigation ambiguity.

Trim editorial asides ('so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens') to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands and state-handling guidance, with only minor over-explanation ('so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens'), fitting 'efficient; minor instances of over-explanation' rather than the lean anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action list/run, and proxy requests plus a flags table, but the 'Popular actions' header only re-states the discovery command instead of listing concrete Griffin actions, a minor gap below the fully executable anchor.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is clear and the connection-state handling is an explicit feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll, surface CONFIGURATION_ERROR), but the inconsistent step numbering ('1b' with no 'Step 1') and absent validation on action results keep it just below the explicit-validation anchor.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is inline with clear section headers (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices); the structure is good and navigable, but the full auth flow and proxy flag table inlined into SKILL.md and the stray step numbering are minor organization gaps versus the well-split anchor.	4 / 5
	Total	16 / 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 clearly identifies the Griffin niche and includes an explicit 'Use when...' trigger, but its action language is generic and lacks concrete capabilities or richer trigger synonyms. It is solid but not comprehensive.

Suggestions

Replace generic verbs with concrete Griffin actions (e.g., 'create and track support tickets, manage customer records, automate ticket routing').

Expand the 'Use when...' trigger to cover natural user phrasings like 'manage support tickets', 'track customer issues', or 'automate Griffin workflows'.

Mention key Griffin objects (Project, Document, Task, Asset) from the body to sharpen specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	It names the domain ('Griffin integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the '1-2 concrete actions, not comprehensive' anchor and falling below the 'several specific actions' anchor.	3 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Griffin data'), but the 'when' trigger is narrow and the 'what' is vague, so it sits at 'has both, when could be more explicit' rather than the fully explicit anchor.	4 / 5
Trigger Term Quality	Relevant keywords ('Griffin', 'data', 'records', 'workflows') are present, but they are generic and miss natural synonyms or variations a user might say, fitting 'some relevant keywords but missing common variations' rather than 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific SaaS ('Griffin') gives a clear niche with minimal conflict risk, but the broad action verbs ('manage data, records, automate workflows') create minor overlap with general data skills, matching 'mostly distinct; 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/griffin/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.