Name: outseta
Rating: 64 (1 reviews)
Author: membranedev

outseta

Outseta integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Outseta data.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/outseta/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, command-heavy integration guide with fully executable examples, a clear connection workflow featuring state-polling feedback loops, and good section structure. Minor trimming of conceptual preamble and explicit validation guidance for destructive actions would push it to the top level.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused with brief explanations, but the introductory paragraph describing what Outseta is and the somewhat redundant 'Outseta Overview' tree add over-explanation that could be trimmed, matching anchor 4 rather than the fully lean anchor 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands throughout (install, login, connection ensure, action list/run, request) plus a flag-options table, covering the common cases as required by anchor 5.	5 / 5
Workflow Clarity	Clear sequence from install → authenticate → connect (with explicit state polling and CLIENT_ACTION_REQUIRED feedback loops) → search → run, but no validation guidance for potentially destructive action runs leaves a minor gap, matching anchor 4 rather than 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with content appropriately kept inline for a single-file CLI-wrapper skill and no nested or buried references, though no external file split is used, matching anchor 4.	4 / 5
	Total	17 / 20 Passed

Description

70%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 Outseta niche and includes both a capability statement and a 'Use when' trigger, but the action vocabulary is generic ('Manage') and the trigger phrasing could be more concrete. It is solid and low-conflict but not maximally specific.

Suggestions

Replace the generic verb 'Manage' with a few concrete actions (e.g., 'Create, update, query, and delete Persons, Organizations, Deals, Leads, Projects, and Activities') to lift specificity toward anchor 5.

Expand the 'Use when' clause with concrete trigger phrases users would say (e.g., 'Use when the user wants to create or update Outseta deals, manage leads, or query CRM records').

Add common synonyms or aliases (e.g., 'contacts', 'accounts', 'subscriptions', 'tickets') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete Outseta entities ('Persons, Organizations, Deals, Leads, Projects, Activities') but relies on a single generic verb 'Manage' rather than enumerating distinct actions, so it sits at anchor 3 and falls short of the 'several specific actions' of anchor 4.	3 / 5
Completeness	Clearly states both what ('Manage Persons, Organizations, Deals, Leads, Projects, Activities and more') and when ('Use when the user wants to interact with Outseta data'), but the 'when' is somewhat generic rather than packed with concrete trigger phrases, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Includes natural entity keywords a user would actually say (Outseta, Persons, Organizations, Deals, Leads, Projects, Activities) plus an explicit 'Use when' clause, though some synonyms and common variations are missing, keeping it just below anchor 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific named platform (Outseta) giving a clear niche and distinct trigger, but the entity terms (Deals, Leads, Organizations) are generic CRM concepts with minor overlap risk against other CRM skills, so it does not fully reach anchor 5.	4 / 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/outseta/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.