Name: travis-ci
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

travis-ci

Travis CI integration. Manage Repositories, Users. Use when the user wants to interact with Travis CI data.

Quality

65%

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

Quality

Content

67%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 actionable and the connection workflow is well-sequenced with polling and state-based checkpoints. It loses points mainly to removable explanatory prose, placeholder-only examples, and a sizable inline action catalog that a leaner overview could offload.

Suggestions

Remove or condense the introductory definition paragraph ("Travis CI is a continuous integration service...") since Claude already knows what Travis CI is.

Add one fully populated worked example for `membrane action run` (with a concrete connection id and --input JSON) so the run path is copy-paste ready.

Flesh out the CONFIGURATION_ERROR / SETUP_FAILED recovery branch beyond "Check the error field for details," e.g. steps to inspect the error and re-run `connection ensure`.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary prose such as the opening "Travis CI is a continuous integration service..." definition and asides like "This is the fastest way to get a connection" that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands, a popular-actions table, and proxy flag reference, but run examples rely on placeholders (<actionId>, CONNECTION_ID) without a fully populated worked example, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with --wait polling and explicit handling of READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR states plus a re-poll feedback loop, but recovery guidance for error states is thin ("Check the error field for details").	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections with no nested references and no bundle files, but sizable inline content such as the full action catalog could be more clearly signaled or split off, leaving minor organization gaps.	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 correctly states both what the skill does and when to use it, and the Travis CI niche is distinct. It is held back by limited action coverage and generic, single-trigger language rather than a richer set of natural keywords.

Suggestions

Replace "Manage Repositories, Users" with the broader concrete action set the skill supports, e.g. "Manage repositories, builds, jobs, logs, environment variables, and cron jobs."

Expand the trigger clause with concrete natural phrases, e.g. "Use when the user wants to inspect Travis CI builds, view job logs, trigger or restart builds, or manage repository settings."

Add common synonyms/extensions users say ("CI", "builds", "jobs", ".travis.yml") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	"Manage Repositories, Users" names the domain plus one or two actions, but omits the other concrete capabilities the skill actually supports (builds, jobs, logs, env vars, cron), so it is not comprehensive.	3 / 5
Completeness	It answers both what ("Travis CI integration. Manage Repositories, Users.") and when ("Use when the user wants to interact with Travis CI data."), but the trigger clause is generic rather than listing concrete trigger phrases, keeping it below a 5.	4 / 5
Trigger Term Quality	It surfaces relevant terms ("Travis CI", "Repositories", "Users", "Travis CI data") but misses common variations and synonyms a user would naturally say ("CI", "builds", "jobs", "pipelines").	3 / 5
Distinctiveness Conflict Risk	"Travis CI integration" carves a clear, distinct niche with minimal conflict risk, though the generic "interact with Travis CI data" trigger leaves minor overlap risk with adjacent CI 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/travis-ci/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.