google-app-engine
Deploy Python applications to Google App Engine Standard/Flexible. Covers app.yaml configuration, Cloud SQL socket connections, Cloud Storage for static files, scaling settings, and environment variables. Use when: deploying to App Engine, configuring app.yaml, connecting Cloud SQL, setting up static file serving, or troubleshooting 502 errors, cold starts, or memory limits.
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill google-app-engine90
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities, includes a comprehensive 'Use when:' clause with both positive triggers and troubleshooting scenarios, and uses highly distinctive GCP/App Engine terminology that minimizes conflict risk with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'app.yaml configuration, Cloud SQL socket connections, Cloud Storage for static files, scaling settings, and environment variables' - these are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (deploy Python apps, configure app.yaml, Cloud SQL connections, etc.) AND when with explicit 'Use when:' clause listing specific trigger scenarios including troubleshooting common errors. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'App Engine', 'app.yaml', 'Cloud SQL', 'static files', '502 errors', 'cold starts', 'memory limits' - these are exactly the terms developers use when facing these issues. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Google App Engine deployment for Python, with GCP-specific terms (Cloud SQL, Cloud Storage, app.yaml) that wouldn't conflict with other deployment or cloud skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, production-ready skill with excellent actionability and workflow clarity. The comprehensive coverage of App Engine deployment scenarios, complete with executable code examples and a thorough Known Issues section, makes it highly useful. Minor verbosity in explanatory sections and comparison tables could be trimmed to improve token efficiency.
Suggestions
Condense the Standard vs Flexible comparison - Claude understands these concepts; focus on the decision criteria and yaml differences only
Move the Instance Classes table to the referenced instance-classes.md file and keep only a brief recommendation inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as explaining what Standard vs Flexible environments are when Claude likely knows this. The comparison tables and extensive Known Issues section add value but could be more condensed. | 2 / 3 |
Actionability | Excellent executable code throughout - complete app.yaml configurations, Python settings.py snippets, bash commands for deployment, and copy-paste ready examples. Every section provides concrete, runnable guidance. | 3 / 3 |
Workflow Clarity | Clear sequential workflows with explicit validation steps. The Quick Start has numbered steps, deployment commands are well-sequenced, and the Known Issues section provides clear cause-prevention patterns. The Production Checklist serves as a validation checkpoint. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from Quick Start to advanced topics. References to bundled templates and external documentation are clearly signaled. Content is appropriately split between inline guidance and referenced resources. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (638 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.