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

bitrise

Bitrise integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bitrise 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/bitrise/SKILL.md

Quality

Content

75%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 highly actionable with concrete commands and a well-described connection state machine, but it carries some unnecessary introductory concept explanation and the overall workflow sequencing could be more explicitly numbered.

Suggestions

Trim the introductory paragraph explaining what Bitrise is and remove promotional framing (e.g. "so you can focus on the integration logic"), since Claude already knows the platform.

Number the end-to-end workflow explicitly (1. Install CLI, 2. Authenticate, 3. Ensure connection, 4. Search actions, 5. Run action / proxy) and resolve the dangling "Step 2" reference so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The bulk is efficient commands and output explanations, but the opening "Bitrise is a mobile CI/CD platform as a service (PaaS)..." paragraph and framing like "so you can focus on the integration logic rather than auth plumbing" explain concepts Claude already knows and could be trimmed.	3 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands for every common case (install, login, connection ensure, polling, action list/run, proxy) plus a concrete flags table, covering the workflow comprehensively.	5 / 5
Workflow Clarity	The connection phase is a clear state machine with explicit feedback loops (poll with --wait until READY, re-poll after CLIENT_ACTION_REQUIRED, handle CONFIGURATION_ERROR), but the macro connect→search→run flow is not numbered as steps and the reference to "Step 2" is dangling.	4 / 5
Progressive Disclosure	It is a single file with no external references and is organized into clear logical headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); structure is good with only minor gaps like the thin "Popular actions" and bare "Bitrise Overview" outline sections.	4 / 5
	Total	16 / 20 Passed

Description

66%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 answers what and when and is highly distinct thanks to the Bitrise brand name, but its capability list is generic and its trigger vocabulary is limited to the brand rather than the platform's actual domain terms.

Suggestions

Replace generic actions ("Manage data, records") with Bitrise-specific concrete actions such as triggering builds, listing apps, inspecting build artifacts, and managing workflows.

Broaden the trigger phrases to include natural domain terms users say, e.g. "Use when the user wants to trigger or monitor Bitrise builds, manage Bitrise apps or workflows, or automate mobile CI/CD."

Dimension	Reasoning	Score
Specificity	It names the domain (Bitrise) and lists a couple of actions ("Manage data, records, and automate workflows"), but those actions are generic rather than Bitrise-specific concrete operations like triggering builds or inspecting artifacts.	3 / 5
Completeness	It explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Bitrise data"), matching the both-present-but-when-could-be-more-specific anchor rather than the comprehensive multi-trigger anchor 5.	4 / 5
Trigger Term Quality	The natural keyword "Bitrise" (and "Bitrise data", "workflows") appears, but it misses the common variations a user would actually say such as CI/CD, builds, mobile apps, or deployments.	3 / 5
Distinctiveness Conflict Risk	"Bitrise" is a specific named SaaS platform with a distinct trigger ("interact with Bitrise data"), giving it a clear niche and minimal risk of conflicting with other skills.	5 / 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/bitrise/SKILL.md
Commit: f484c82

Reviewed: 8 minutes 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.