Name: makepad-deployment
Rating: 65.60000000000001 (1 reviews)
Author: administrakt0r

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

Quality

80%

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 ./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

Quality

Content

65%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 executable commands and complete config for every supported platform, but it is held back by duplicated config blocks, a lack of explicit validation checkpoints in build/release workflows, and reference-file pointers to files that are not actually present in the bundle.

Suggestions

Add explicit validation checkpoints to the build/release workflows (e.g. 'Verify the .apk exists in ./target/makepad-android-app/ before uploading') to lift workflow_clarity above the batch-operation cap of 3.

De-duplicate the packaging config: keep one canonical Cargo.toml example and reference it instead of repeating the resources array and before-packaging-command in both the 'Configure Cargo.toml' and 'Complete Example Cargo.toml' sections.

Either create the referenced bundle files (references/makepad-packaging-action.md, references/platform-troubleshooting.md, community/dora-studio-package-workflow.md) or remove the broken 'Reference Files' pointers so navigation is not misleading.

Dimension	Reasoning	Score
Conciseness	Largely actionable code/config with little concept padding, but it duplicates material: the resources array and packaging config appear both in 'Configure Cargo.toml' and again in 'Complete Example Cargo.toml', and the 'Quick Navigation' and 'Quick Reference' tables repeat overlapping command summaries — content that could be tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready bash and TOML blocks cover the common cases across all platforms — e.g. 'cargo makepad android build -p your-app --release', the IPA 'mkdir Payload / cp -r / zip -r' steps, and complete Cargo.toml packaging metadata with clear placeholders.	5 / 5
Workflow Clarity	Sequences exist per platform (install toolchain → build → output path) and iOS device provisioning is numbered, but there are no explicit validation checkpoints or feedback loops (no 'verify build succeeded before packaging/releasing'); per the batch/release-operation cap, this keeps it at 3 rather than higher.	3 / 5
Progressive Disclosure	Good top-level structure (Quick Navigation, per-platform sections, Quick Reference) and a 'Reference Files' list, but the referenced files ('references/makepad-packaging-action.md', 'references/platform-troubleshooting.md', 'community/dora-studio-package-workflow.md') do not exist in the bundle, and large config blocks are inlined rather than split out — structure present but references unverified and bulk content inline.	3 / 5
	Total	14 / 20 Passed

Description

95%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.

A strong description: it states the niche, lists concrete actions and tools, and provides an explicit, comprehensive bilingual trigger list with synonyms and file extensions. The only minor weakness is that the named actions themselves are limited to 'packaging and deployment'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Makepad packaging and deployment') plus concrete actions and specific targets such as 'APK, IPA', '.deb, .dmg, .nsis', 'WASM, Android, iOS', and the tools 'cargo-packager, cargo-makepad' — several specific items with minor gaps in naming the actions themselves.	4 / 5
Completeness	Explicitly answers both what ('Use for Makepad packaging and deployment') and when ('Triggers on: deploy, package, APK, IPA...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive coverage with synonyms and file extensions: 'deploy, package, APK, IPA, 打包, 部署', '.deb, .dmg, .nsis', 'WASM, Android, iOS', 'GitHub Actions, CI, action, marketplace' — bilingual synonyms and concrete extensions match the top anchor.	5 / 5
Distinctiveness Conflict Risk	Clear niche (Makepad) with distinct tool triggers ('cargo-packager', 'cargo-makepad', 'makepad-packaging-action') and platform/format extensions, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/makepad-deployment/SKILL.md
Commit: 57c135b

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.