Name: simple-analytics
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

simple-analytics

Simple Analytics integration. Manage Websites, Events. Use when the user wants to interact with Simple Analytics data.

Quality

64%

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

Quality

Content

66%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 actionable and reasonably concise, with concrete CLI commands and good section structure. Its main weakness is the absence of explicit validation/verification checkpoints in the action-running and proxy workflows, which caps workflow clarity.

Suggestions

Add explicit validation steps after running actions or proxy requests (e.g., check the `output`/`error` field and confirm expected results before proceeding).

Trim minor over-explanation such as the token-burn rationale in 'Best practices' to lean out the closing section.

Consider moving the proxy options table and the popular-actions reference into separate reference files to tighten the core SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete commands and minimal padding, though a few lines explain concepts Claude could infer (e.g., 'This will burn less tokens'), placing it slightly below fully lean at 'Efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides concrete, mostly copy-paste-ready CLI commands and a clear options table, with only minor gaps (e.g., placeholder CONNECTION_ID handling), fitting 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connection flow is sequenced with state polling, but operations that touch external analytics data (running actions, proxy requests) lack explicit validation or verification checkpoints, capping it at 'Steps listed but validation gaps'.	3 / 5
Progressive Disclosure	Content is well-organized into clearly signaled sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, though some inline material (the proxy options table, popular actions) could live in separate reference files.	4 / 5
	Total	15 / 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 adequately specific and includes an explicit 'Use when' trigger with the product name, making it mostly distinct. Its main weakness is generic action verbs ('Manage Websites, Events') and a thin set of natural trigger synonyms.

Suggestions

Replace the generic 'Manage Websites, Events' with concrete actions like 'List websites, retrieve events, and query traffic stats' to improve specificity.

Broaden the trigger phrase with natural variations, e.g. 'Use when the user asks about Simple Analytics traffic, page views, events, or visitor stats.'

Keep the explicit 'Use when...' clause but pair it with more specific trigger keywords to raise completeness and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of concrete actions ('Manage Websites, Events') but the actions are generic and not comprehensive, matching the 'Names domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	It has a clear 'what' ('Manage Websites, Events') and an explicit 'when' ('Use when the user wants to interact with Simple Analytics data'), but the 'when' could be more specific, matching 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	It includes the natural product name 'Simple Analytics' and the phrase 'interact with Simple Analytics data', but lacks common synonyms, file extensions, or broader trigger variations, fitting the 'Some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Simple Analytics' gives it a clear niche with minimal conflict risk, though the generic 'Manage Websites, Events' leaves minor overlap risk with other analytics 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/simple-analytics/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.