Configure and verify Flutter flavors, environments, signing, versioning, release artifacts, obfuscation symbols, and store-ready builds. Use for local artifact configuration; route CI provider workflows to flutter-ci-cd, and do not publish or change live credentials without explicit authorization.
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
The canonical home for this skill is thiennc-tesoglobal/flutter-skills
Produce reproducible artifacts for the requested platforms while preserving secrets and external-release authority.
Read SDK constraints, flavors/schemes, bundle/application IDs, version source, signing configuration, environment injection, CI, native deployment targets, and store requirements. Never print or commit secrets, keystores, provisioning material, or service credentials.
Run formatting, analysis, tests, and a clean release build for each intended target/flavor. Verify the produced artifact's signature without uploading it: apksigner verify --print-certs for an APK, jarsigner -verify -certs for an AAB, and codesign --verify --deep --strict for an iOS app bundle, then compare the certificate or signing identity with the intended release key. Install or serve the built artifact and smoke-test startup plus a critical flow. Record artifact path, version, flavor, target, and remaining store-side work.
thienqo/flutter-skills
a177189
Canonical home
since Aug 24, 2026
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.