CtrlK
BlogDocsLog inGet started
Tessl Logo

gloria-ai

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

59

Quality

68%

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/gloria-ai/SKILL.md
SKILL.md
Quality
Evals
Security

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 well-structured, executable CLI integration guide with concrete commands, a clear sequenced workflow, and an explicit connection-readiness feedback loop, with only minor verbosity and a small navigation inconsistency.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-focused, but contains minor over-explanation that could be trimmed, such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection".

4 / 5

Actionability

It provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flag table, with only minor gaps from unsubstituted placeholders like CONNECTION_ID and actionId.

4 / 5

Workflow Clarity

The install→authenticate→connect→search→run sequence is clear with a genuine state-machine feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED and re-polling), but the "skip to Step 2" reference points to a step that is not explicitly numbered, a minor navigation gap.

4 / 5

Progressive Disclosure

It is a single self-contained file with well-organized section headers and no nested references, appropriate for this size; the thin "Gloria AI Overview" section and absence of any split-out detail keep it just short of fully exemplary.

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 cleanly states both a purpose and an explicit use trigger, and the named product gives it reasonable distinctiveness, but the listed capabilities are generic and the trigger vocabulary is narrow.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Gloria AI actions such as "qualify leads, schedule meetings, send follow-ups, and sync contacts to your CRM".

Broaden the trigger terms beyond "interact with Gloria AI data" to natural phrases a user would say, e.g. "Gloria AI", "sales assistant", "lead qualification", "meeting scheduling", and "follow-ups".

Make the 'when' clause enumerate specific use cases (lead qualification, scheduling, follow-ups) rather than the abstract "interact with Gloria AI data".

DimensionReasoningScore

Specificity

It names the domain (Gloria AI) and lists two to three actions ("Manage data, records, and automate workflows"), but the actions are generic verbs on generic objects rather than concrete capabilities, matching the anchor that names a domain plus a few actions without being comprehensive.

3 / 5

Completeness

It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Gloria AI data"), with an explicit "Use when" clause; both halves could be more specific, fitting the anchor where 'when' is present but not maximally explicit.

4 / 5

Trigger Term Quality

It includes "Gloria AI", "data", and "records", but the only trigger phrasing is "Use when the user wants to interact with Gloria AI data", missing the natural sales-domain terms (leads, CRM, scheduling, follow-ups) a user would actually say.

3 / 5

Distinctiveness Conflict Risk

Tying triggers to the named product "Gloria AI" makes it mostly distinct with minimal conflict risk, though the generic "manage data/records/workflows" verbs create minor overlap with other data-integration skills.

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.