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

singular

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

Quality

69%

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/singular/SKILL.md

Quality

Content

76%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 skill body is highly actionable with executable CLI commands and clear connection-state feedback loops, and it is reasonably concise and well-structured. Its main gap is the absence of validation/confirmation steps before running potentially destructive actions on external data.

Suggestions

Add a validation checkpoint before running write/mutating actions, e.g. inspect the action's inputSchema, confirm intent with the user, and prefer a dry-run or read-first verification for destructive operations.

Fix the step-numbering inconsistency (references to 'Step 2' and a '1b' without a labeled 'Step 1'/'1a') so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused with copy-paste CLI examples, with only minor over-explanation (the opening marketing-analytics paragraph and phrases like 'burn less tokens') that could be trimmed, matching the 'efficient with minor instances of over-explanation' anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the common cases (install, interactive and headless login, connection ensure/get, action list, action run with JSON input, proxy) plus a complete flag table, matching the 'fully executable; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	The connection phase has clear state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but the action-execution phase mutates external CRM/marketing data with no validation or confirmation checkpoint before running write operations, triggering the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no nested references; with no bundle files present, structure is good but the inline entity list and proxy flag table leave minor organization gaps, matching the 'good structure with minor gaps' anchor rather than a fully split one-level-deep layout.	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 what the skill does and when to use it in third person, and its Singular-specific naming keeps conflict risk low. Its main weakness is generic action verbs and a single trigger phrase rather than concrete capabilities with natural synonym coverage.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Singular capabilities such as 'query campaign ROI, pull attribution reports, create and update records'.

Broaden the trigger clause with natural synonyms users would say, e.g. 'Use when the user wants to pull Singular marketing analytics, attribution data, or campaign reports'.

Add a brief note on scope (read vs. write operations) so the 'when' guidance is more specific.

Dimension	Reasoning	Score
Specificity	Names the Singular domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete capabilities, matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Provides both a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Singular data'), though the 'when' could be more specific, matching the anchor that has both with room for greater specificity.	4 / 5
Trigger Term Quality	Contains a single natural trigger phrase ('Use when the user wants to interact with Singular data') but misses common variations or synonyms, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Explicitly names Singular and ties the trigger to 'Singular data', giving it a distinct niche with minimal conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap risk with other data/CRM skills.	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/singular/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.