CtrlK
BlogDocsLog inGet started
Tessl Logo

authenticate-com

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

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/authenticate-com/SKILL.md
SKILL.md
Quality
Evals
Security

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 sensible workflow including a connection-state feedback loop. Its main weaknesses are mild intro/best-practices verbosity and broken cross-references in the step numbering, which slightly hurt conciseness and workflow clarity.

Suggestions

Fix the dangling step references: label the connect and search/run sections as 'Step 1' and 'Step 2' (or add a 1a) so 'skip to Step 2' and '1b' resolve.

Trim the opening product paragraph and the 'rather than auth plumbing' aside to reduce tokens that do not aid execution.

Consider moving the proxy flag table and clientAction state reference into a separate reference file to improve progressive disclosure for this >50-line skill.

DimensionReasoningScore

Conciseness

The body is mostly lean executable command blocks with clear tables, but the opening product paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' add mild over-explanation that could be trimmed; not a 5 because of these padded passages.

4 / 5

Actionability

Provides copy-paste-ready commands across the full flow (install, login, connection ensure/get, action list/run, request proxy) with a concrete flag table, covering the common cases as the anchor 5 example does.

5 / 5

Workflow Clarity

A clear install -> login -> connect -> search -> run sequence exists with a real feedback loop for connection state polling (CLIENT_ACTION_REQUIRED -> user acts -> re-poll), but step numbering is broken ('skip to Step 2' with no Step 2, '1b' with no 1a), a minor validation/navigation gap that keeps it below 5.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections in a single file with no external bundle references; at over 50 lines it does not qualify for the simple-skill 5, and no separate reference files are signaled, so it sits at the 'good structure, minor organization gaps' anchor.

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 well-formed with an explicit 'Use when' trigger and a named product niche, but its capability verbs are generic and it lacks concrete trigger scenarios or synonyms. It clears the bar for completeness and distinctiveness while leaving specificity and trigger-term richness as the main improvement areas.

Suggestions

Replace generic verbs with concrete Authenticate.com capabilities, e.g. 'verify identities, run background checks, manage person records, and automate verification workflows'.

Add concrete trigger phrases users would say, such as 'Use when the user wants to verify identities, run background checks, or query Authenticate.com person/records data'.

Include natural synonyms and objects (e.g. 'identity verification', 'background checks', 'person records') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Authenticate.com domain and lists actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete API operations, matching the 'names domain and 1-2 concrete actions but not comprehensive' anchor; not a 4 because the verbs lack specific capability detail.

3 / 5

Completeness

Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Authenticate.com data'); not a 5 because the 'when' clause is somewhat generic rather than naming concrete trigger scenarios.

4 / 5

Trigger Term Quality

Includes the natural product keyword 'Authenticate.com' plus 'data, records, workflows', but offers few synonyms or variation phrases a user would naturally say, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

The specific product name 'Authenticate.com' gives a clear niche with low conflict risk, but the generic action phrasing ('manage data, records') leaves minor overlap risk with other data/CRM skills, placing it just below the clearly-distinct anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.