SkillsAdd

smithery.ai

check-secure-files

Enforces a checklist to verify that all required secure configuration files (google-services.json, GoogleService-Info.plist, environment-configs.json) are present for all environments (dev, stg, prd).

First seen Apr 16, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,625 B
  • docs SUMMARY.md 226 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Check Secure Files Skill

This skill ensures that the necessary secure configuration files are populated before proceeding with build variant setup or deployment.

Steps

1. Initialize secureFiles

  • Check/Create secureFiles:

- Copy the template secureFiles folder from resources (.agent/skills/setup_variants/resources/secureFiles) to the project root if it does not exist. - Ensure signing/debug.keystore and signing/keystore.properties.template are present.

2. Verify Checklist (CRITICAL)

[!IMPORTANT]
Safety Check: You must NOT proceed until the secureFiles directory is populated with actual data.

ASK the user to confirm the following checklist. If the user asks to proceed without confirming ALL items, you MUST ask again.

Checklist:

  • Dev Environment

- [ ] secureFiles/dev/google-services.json (Android) - [ ] secureFiles/dev/GoogleService-Info.plist (iOS) - [ ] secureFiles/dev/environment-configs.json (Dart Defines)

  • Staging Environment

- [ ] secureFiles/stg/google-services.json (Android) - [ ] secureFiles/stg/GoogleService-Info.plist (iOS) - [ ] secureFiles/stg/environment-configs.json (Dart Defines)

  • Production Environment

- [ ] secureFiles/prd/google-services.json (Android) - [ ] secureFiles/prd/GoogleService-Info.plist (iOS) - [ ] secureFiles/prd/environment-configs.json (Dart Defines)

3. Verify Content Integrity

  • Compare with Templates:

- For each file in the checklist, compare its content with the corresponding template in .agent/skills/setupvariants/resources/secureFiles. - Example: Compare secureFiles/dev/google-services.json with .agent/skills/setupvariants/resources/secureFiles/dev/google-services.json.

  • Validation Logic:

- If a file has the exact same content as the template, it is considered INVALID (user failed to update it). - If a file is missing, it is INVALID.

  • On Failure:

- If any file is invalid: 1. Notify the user specifically which files are still defaults or missing. 2. Re-present the Checklist from Step 2. 3. Uncheck the boxes for the invalid files. 4. Ask the user to update the files and check the box again when done. - Loop until all files are present and different from the templates.