Name: coveralls
Rating: 60 (1 reviews)
Author: membranedev

coveralls

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

Quality

70%

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/coveralls/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 content is a strong, executable CLI guide with a well-validated connection workflow and clean sectioning. Its main weaknesses are minor verbosity in the opening overview, a broken "Step 2" cross-reference, and slight redundancy between the actions sections.

Suggestions

Fix or remove the dangling "Skip to Step 2" references and renumber sections (e.g. replace "1b" with a coherent 1/2/3 sequence) so the workflow path is unambiguous.

Trim the opening "Coveralls is a code coverage tool..." paragraph and the rationale clauses in Best practices, since Claude already knows these concepts.

Consolidate "Searching for actions" and "Popular actions" into a single section to remove the duplicated `action list --intent=QUERY` guidance.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and command-driven, but includes minor over-explanation Claude already knows ("Coveralls is a code coverage tool that helps developers track the percentage of their code that is tested") and slightly padded best-practice rationales, matching the score-4 anchor of efficient with minor trimmable instances.	4 / 5
Actionability	It provides fully executable `membrane` CLI commands for install, login, connection, action search/run, and proxying, plus a concrete flags table, covering the common cases in copy-paste-ready form, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but the "Skip to Step 2" pointer references a step that does not exist and section labels ("1b" with no 1a/2) are slightly incoherent, matching the score-4 anchor of clear sequence with minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the ~155-line body is well-sectioned with clear headers and a one-level external docs link, giving good structure with easy navigation; it is not a 5 because some inline material (e.g. the proxy flags table) could live in a reference file and the "Popular actions" section partly restates "Searching for actions", matching the score-4 anchor.	4 / 5
	Total	17 / 20 Passed

Description

57%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 correctly anchors on the Coveralls niche and includes an explicit use-when clause, but its capability wording ("manage data, records, and automate workflows") is generic and lacks the coverage-specific vocabulary users would naturally invoke. Strengthening it with concrete coverage actions and natural trigger terms would raise specificity and trigger quality.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete Coveralls actions such as "view build coverage, track per-file coverage, and inspect line-by-line coverage changes".

Add natural user trigger terms like "code coverage", "test coverage", "coverage reports", or "builds" so the skill matches how users actually phrase the request.

Tighten the "Use when..." clause to coverage-specific situations, e.g. "Use when the user wants to check code coverage, review a build's coverage, or investigate untested lines in a repository."

Dimension	Reasoning	Score
Specificity	The description names the Coveralls domain but the actions ("Manage data, records, and automate workflows") are generic and not tied to coverage-specific capabilities like builds or file coverage, matching the score-2 anchor of naming the domain with minimal/generic actions.	2 / 5
Completeness	It states both a "what" ("Coveralls integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Coveralls data"), but the "when" clause is generic rather than tied to concrete coverage triggers, matching the score-4 anchor of having both with a less-specific "when".	4 / 5
Trigger Term Quality	It includes the keyword "Coveralls" plus "data", "records", and "workflows", but omits the natural phrases users actually say ("code coverage", "test coverage", "builds"), so it has some relevant keywords but misses common variations, matching the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	The "Coveralls integration" framing gives a clear niche with distinct triggers and low conflict risk, though the generic "manage data, records" tail introduces minor overlap with other data skills, matching the score-4 anchor of mostly distinct with minor overlap risk.	4 / 5
	Total	13 / 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/coveralls/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.