CtrlK
BlogDocsLog inGet started
Tessl Logo

codemagic

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/codemagic/SKILL.md
SKILL.md
Quality
Evals
Security

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 CLI commands and validation checkpoints for connection setup, weakened only by an unnecessary introductory explanation of what Codemagic is and minor workflow-numbering inconsistencies. Structure is clean for a single-file skill.

Suggestions

Remove or condense the introductory paragraph explaining what Codemagic is and its target audience, since Claude already knows this.

Fix the broken 'Step 2' reference and the '1b' subsection numbering so the connection workflow reads as a coherent numbered sequence.

Add a brief validation note before destructive actions (cancel-build, delete caches), e.g. confirm the target application ID before running.

DimensionReasoningScore

Conciseness

Most of the body is lean executable commands, but the opening paragraph explains what Codemagic is and who uses it — concepts Claude already knows — and could be trimmed.

3 / 5

Actionability

It provides copy-paste ready commands for every phase (install, login, connection ensure, action list/run, request proxy) plus a table of concrete popular actions with keys and descriptions.

5 / 5

Workflow Clarity

The connect-to-run sequence has explicit polling and state validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but references to an unlabeled 'Step 2' and the '1b' numbering introduce minor gaps.

4 / 5

Progressive Disclosure

The single-file skill is well organized into clear sections (Overview, Working with Codemagic, Popular actions, Best practices) with no nested references, though the popular-actions table could live in a separate reference file.

4 / 5

Total

16

/

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 includes an explicit 'Use when' trigger and names a distinct niche (Codemagic), but its capability verbs are generic rather than concrete CI/CD actions and it lacks natural keyword variations. Trigger guidance is present but thin.

Suggestions

Replace generic verbs with concrete Codemagic actions, e.g. 'Start and cancel builds, manage applications, and retrieve build artifacts'.

Expand the 'Use when' clause with natural trigger phrases users would say, such as 'CI/CD builds', 'mobile app deployments', or 'Codemagic workflows'.

Tie the 'what' to actual Codemagic objects (builds, applications, artifacts, workflows) instead of 'data and records'.

DimensionReasoningScore

Specificity

It names the Codemagic domain but the actions ('Manage data, records, and automate workflows') are generic and not concrete CI/CD actions like starting builds or managing applications.

2 / 5

Completeness

It states both what ('Codemagic integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Codemagic data'), though the trigger could be more specific.

4 / 5

Trigger Term Quality

'Codemagic' and 'Codemagic data' are relevant keywords, but common natural variations like 'CI/CD', 'builds', 'mobile app', or 'iOS/Android' are missing.

3 / 5

Distinctiveness Conflict Risk

'Codemagic' is a distinct niche trigger with minimal overlap risk, though the generic 'manage data, records' phrasing slightly weakens distinctiveness.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.