CtrlK
BlogDocsLog inGet started
Tessl Logo

makepad-deployment

CRITICAL: Use for Makepad packaging and deployment. Triggers on: deploy, package, APK, IPA, 打包, 部署, cargo-packager, cargo-makepad, WASM, Android, iOS, distribution, installer, .deb, .dmg, .nsis, GitHub Actions, CI, action, marketplace

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/makepad-deployment/SKILL.md

The canonical home for this skill is makepad-deployment in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive, highly actionable packaging guide covering all Makepad target platforms with concrete, executable commands and configuration examples. Its main weaknesses are redundancy (the complete example Cargo.toml duplicates earlier content, resource lists appear twice) and the absence of validation checkpoints in packaging workflows — there are no steps to verify packages were built correctly before distribution. The structure and navigation are solid but could benefit from trimming duplicated content.

Suggestions

Remove or significantly condense the 'Complete Example Cargo.toml' section since it largely duplicates the earlier configuration section — consider moving it to a reference file instead.

Add explicit validation steps after each packaging command (e.g., verify output file exists, check file size, test installation on target platform) to create proper feedback loops for these batch operations.

Integrate troubleshooting checks as inline validation steps within each platform's workflow rather than as a separate section at the end.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but has significant redundancy: the 'Complete Example Cargo.toml' section largely duplicates the earlier 'Configure Cargo.toml' section with the same resource entries and packaging commands. The Quick Reference table also repeats commands already shown inline. Some sections like the resource list are verbose with all the Chinese font entries repeated twice.

3 / 5

Actionability

Excellent actionability throughout — every platform has copy-paste ready commands, complete Cargo.toml configuration blocks, specific install commands with version pins, and concrete output paths. The iOS IPA creation steps and Wasm serving instructions are particularly well-specified with exact commands.

5 / 5

Workflow Clarity

Steps are listed in logical sequence for each platform, but validation/verification checkpoints are largely missing. For packaging operations (which are batch/destructive in nature — producing distributable artifacts), there are no explicit validation steps like verifying the package was created, testing the output, or checking signatures. The troubleshooting section is reactive rather than integrated into the workflow as checkpoints.

3 / 5

Progressive Disclosure

Good structure with a navigation table at the top, clear section headers, and references to external files (references/platform-troubleshooting.md, references/makepad-packaging-action.md, community/dora-studio-package-workflow.md). However, no bundle files were provided to verify these references exist, and the Complete Example Cargo.toml could arguably be in a separate reference file rather than inlined, as it adds significant length.

4 / 5

Total

15

/

20

Passed

Description

54%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 excels at trigger term coverage with an impressive list of natural keywords, synonyms, and even multilingual terms. However, it critically lacks specificity about what the skill actually does—it reads as a keyword list rather than a capability description. Adding concrete actions (e.g., 'Builds APKs for Android, generates WASM bundles, configures CI pipelines') would significantly improve it.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Builds Android APKs, generates iOS IPA files, creates desktop installers (.deb, .dmg, .nsis), deploys WASM builds, and configures GitHub Actions CI pipelines for Makepad projects.'

Restructure to separate the 'what it does' from the 'when to use it'—e.g., lead with capability statements, then follow with 'Use when...' and the trigger terms.

DimensionReasoningScore

Specificity

The description names the domain (Makepad packaging and deployment) but lists no concrete actions—only trigger terms. There are no verbs describing what the skill actually does (e.g., 'builds APKs', 'creates installers', 'configures CI pipelines').

2 / 5

Completeness

The 'when' is explicitly covered via the trigger list, but the 'what' is extremely vague—'Makepad packaging and deployment' gives no detail about what concrete actions or capabilities the skill provides. The description is essentially just a trigger list without explaining what the skill does.

2 / 5

Trigger Term Quality

Excellent coverage of natural trigger terms including platform names (Android, iOS, WASM), file extensions (.deb, .dmg), tool names (cargo-packager, cargo-makepad), CI terms (GitHub Actions, CI), and even Chinese synonyms (打包, 部署). Comprehensive and includes synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

The Makepad-specific focus and specialized trigger terms (cargo-makepad, cargo-packager) make it fairly distinct. Minor overlap risk exists with generic CI/CD or packaging skills due to broad terms like 'deploy', 'package', 'GitHub Actions', and 'installer'.

4 / 5

Total

13

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.