Name: github-actions
Rating: 53.6 (1 reviews)
Author: membranedev

github-actions

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

Quality

60%

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/github-actions/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 body is largely command-driven and well-structured with a genuinely sequenced, checkpointed connection workflow — a strong showing for an integration skill. Its main weakness is token-efficiency: an opening conceptual explainer and repeated Membrane marketing prose pad what is otherwise tight, executable guidance.

Suggestions

Cut the opening 'GitHub Actions is a CI/CD platform...' paragraph and the 'used by individual developers and large organizations alike' filler — Claude already knows what GitHub Actions is.

Trim best-practice prose that restates Membrane's generic value ('burn less tokens', 'make communication more secure') down to the actionable directive.

Resolve the dangling 'skip to Step 2' reference by explicitly labeling the Searching/Running actions section as Step 2, or remove the forward references.

Dimension	Reasoning	Score
Conciseness	Most sections are tight and command-oriented, but the opening paragraph explains what GitHub Actions is ('CI/CD platform integrated directly into GitHub repositories... used by individual developers and large organizations alike') — a concept Claude already knows — and the proxy/best-practices prose repeats Membrane's value props ('handles auth', 'burn less tokens', 'make communication more secure'), which could be trimmed.	3 / 5
Actionability	Concrete, copy-pasteable commands dominate (membrane login, connection ensure, action list/run, request flags in a table) and cover the common cases with minor gaps such as leaving CONNECTION_ID as an undefined placeholder and not showing how to obtain it from the prior JSON output.	4 / 5
Workflow Clarity	The connection flow is explicitly sequenced with state checks (READY → skip to Step 2; BUILDING → poll; CLIENT_ACTION_REQUIRED → branch on type; CONFIGURATION_ERROR/SETUP_FAILED → check error), which is a clear checkpointed workflow with feedback loops; minor gaps (a dangling 'Step 2' reference with no labeled Step 2, and searching/running not explicitly tied back to it) keep it below 5.	4 / 5
Progressive Disclosure	The body is a single-file overview with clearly signaled section headers and command tables, and no bundle files exist to offload detail; most content is appropriately placed, though some API-reference-style material (the full clientAction object schema, the proxy flag table) could arguably live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

53%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 names the domain and includes an explicit 'Use when' trigger, but the capability phrasing is generic boilerplate shared across Membrane integrations rather than GitHub-Actions-specific actions. It is functional but reads as templated rather than tailored.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete GitHub Actions capabilities, e.g. 'Trigger and inspect workflow runs, read job logs, and manage artifacts.'

Add natural trigger variations and synonyms a user would actually say, such as 'CI/CD', 'workflow runs', 'jobs', 'pipelines', or '.github/workflows'.

Sharpen the 'Use when' clause with concrete triggers, e.g. 'Use when the user wants to trigger or inspect GitHub Actions workflow runs, debug failed jobs, or manage build artifacts.'

Dimension	Reasoning	Score
Specificity	The domain (GitHub Actions) is named, but the only actions offered are the generic trio 'Manage data, records, and automate workflows' — boilerplate phrasing that could describe almost any Membrane integration rather than concrete GitHub Actions capabilities (e.g. triggering/listing runs, inspecting logs, managing artifacts).	2 / 5
Completeness	Both halves are present: 'what' (GitHub Actions integration via Membrane) and an explicit 'Use when the user wants to interact with GitHub Actions data' trigger clause; the 'when' is somewhat generic rather than listing concrete trigger phrases, which keeps it just below a 5.	4 / 5
Trigger Term Quality	It includes the natural term 'GitHub Actions' plus 'workflows' and 'data, records', but lacks common variations or synonyms a user would actually say (e.g. 'CI/CD', 'workflow runs', 'jobs', 'pipeline', 'actions').	3 / 5
Distinctiveness Conflict Risk	'GitHub Actions integration' gives it a recognizable niche, but the generic 'Manage data, records, and automate workflows' wording overlaps heavily with other Membrane app skills, so it could plausibly trigger for adjacent CI/CD or automation skills.	3 / 5
	Total	12 / 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/github-actions/SKILL.md
Commit: f484c82

Reviewed: 5 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.