Name: signicat
Rating: 61.6 (1 reviews)
Author: membranedev

signicat

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

Quality

72%

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/signicat/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 body is a strong, action-oriented guide with executable Membrane CLI commands and a clear connection-readiness workflow including error-state feedback loops. Its main gaps are minor structural inconsistencies in the workflow numbering and a single-file layout that could split out some reference detail.

Suggestions

Fix the step numbering: add an explicit "Step 2" label for the action-search/run phase or rename "1b" to match a clearly numbered sequence.

Consider moving the proxy flags table and detailed clientAction state handling into a references/ file, keeping SKILL.md as a tighter overview.

Tighten the opening Signicat description paragraph to one line to reduce over-explanation of domain context.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with little padding, though the opening platform-description paragraph and a few explanatory sentences could be trimmed slightly.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure, action list/run with JSON input, request proxy) plus a concrete flags table, covering the common cases.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run/proxy sequence with explicit state checkpoints and a feedback loop (poll again until READY), but the "Step 2" reference is implicit and the "1b" heading appears without a corresponding "1a", leaving minor gaps.	4 / 5
Progressive Disclosure	Content is well-organized into logical sections in a single file with no external bundle files to navigate; at over 50 lines it is borderline, and the proxy flags table and detailed connection-state handling could optionally be split into a reference file.	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 is a concise, third-person statement that covers both what the skill does and when to use it, anchored by the distinctive Signicat brand. Its main weakness is generic action language and a narrow "when" clause that under-sells the platform's identity-verification and signing capabilities.

Suggestions

Replace generic verbs with concrete Signicat capabilities, e.g. "Manage identity verification, digital signing, and onboarding workflows."

Broaden the "when" clause to surface natural trigger phrases users say, e.g. "Use when the user wants to verify identities, send documents for signature, or interact with Signicat data."

Mention the relevant resource types (sessions, documents, document groups, users, webhooks, reports) to improve specificity and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Signicat domain and lists several action areas ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete (e.g., it omits identity verification, digital signing, onboarding) so it does not reach comprehensive coverage.	3 / 5
Completeness	It states both a "what" ("Signicat integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Signicat data"), but the "when" clause is narrow and could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural trigger term "Signicat" appears, plus "data", "records", and "workflows", but beyond the brand name the keywords are generic and lack common variations a user might say (e.g., signing, identity verification, eID).	3 / 5
Distinctiveness Conflict Risk	The Signicat brand name gives it a clear, distinct niche with low conflict risk against other skills, though the generic action verbs slightly weaken how distinctive the triggers are.	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/signicat/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.