CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/makepad-deployment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 copy-paste configuration for every platform, and per-platform workflows are clearly sequenced with troubleshooting recovery steps. Its weaknesses are verbatim duplication between the guide sections, the complete example, and the quick-reference table, and reference links pointing to files that are absent from the bundle.

Suggestions

Create the referenced files (references/platform-troubleshooting.md, references/makepad-packaging-action.md, community/dora-studio-package-workflow.md) or remove the citations — every listed reference is currently a dead path.

Move the "Complete Example Cargo.toml" and platform-specific config blocks into a single reference file, keeping only a minimal quick-start config inline, to eliminate the verbatim duplication of resources arrays and packaging commands.

Add explicit verification checkpoints after each build step (e.g., "confirm ./dist/*.deb exists before uploading") to strengthen the workflow's validation loop for CI/release contexts.

DimensionReasoningScore

Conciseness

The body is mostly high-value commands and config, but the ~70-line "Complete Example Cargo.toml" and the Quick Reference table duplicate earlier sections nearly verbatim (resources arrays, before-packaging commands, platform metadata, install commands), which is padding that could be trimmed or merged; it does not over-explain known concepts, so it sits at anchor 3 rather than the noticeably-padded anchor 2.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: install commands with versions, complete Cargo.toml config, per-platform build commands with output paths, a GitHub Actions YAML snippet, and IPA creation steps — specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Each platform follows a clear install → configure → build → output sequence with output locations and a troubleshooting section covering error recovery (missing resources, iOS provisioning, Android SDK); minor validation gaps (no explicit "verify the artifact exists" checkpoints) keep it at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Section structure and the navigation table are good and references are clearly signaled, but the cited files (`references/platform-troubleshooting.md`, `references/makepad-packaging-action.md`, `community/dora-studio-package-workflow.md`) do not exist in the bundle, and content that belongs in references (the full example Cargo.toml, platform-specific config) is inlined — matching anchor 3's "could be better organized" rather than anchor 4's appropriately-placed content.

3 / 5

Total

15

/

20

Passed

Description

68%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 has an explicit, rich trigger list with synonyms and file extensions, but its capability statement is generic — it names the domain without saying what the skill concretely does. Broad trigger terms like "CI", "action", and "marketplace" raise conflict risk with non-Makepad deployment skills.

Suggestions

State concrete capabilities in the description, e.g., "Builds and packages Makead apps for Android (.apk), iOS (.ipa), desktop (.deb/.dmg/.nsis), and Wasm, plus GitHub Actions packaging".

Remove or qualify overly generic trigger terms ("CI", "action", "marketplace") so the skill does not fire for non-Makepad deployment or CI requests.

Keep the bilingual triggers (打包, 部署) and file extensions — they are the strongest part of the trigger list.

DimensionReasoningScore

Specificity

"Use for Makepad packaging and deployment" names the domain but the stated actions are minimal and generic, closely paralleling the anchor-2 example "Processes PDF files"; no concrete capability (e.g., building APKs/IPAs/.deb installers) is stated, so it does not reach anchor 3.

2 / 5

Completeness

Both "what" ("Makepad packaging and deployment") and "when" (explicit "Triggers on:" keyword list) are present, but the "what" is thin and generic — it never says what the skill actually produces or covers — so it falls at anchor 4 rather than the fully explicit anchor 5.

4 / 5

Trigger Term Quality

The trigger list ("deploy, package, APK, IPA, 打包, 部署, cargo-packager, cargo-makepad, WASM, Android, iOS, distribution, installer, .deb, .dmg, .nsis, GitHub Actions, CI") comprehensively covers natural terms with synonyms, tool names, and file extensions; only marginal overbroad entries like "action"/"marketplace" keep it from being flawless but it still matches the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

"Makepad" carves out a clear niche, but generic trigger terms ("CI", "action", "marketplace", "deploy", "package", "distribution") create real overlap risk with any general deployment or CI skill, matching anchor 3 rather than the minor-overlap anchor 4.

3 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

skills/makepad-deployment/SKILL.md

Revision

64adc55

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill