django-cloud-sql-postgres
Deploy Django on Google App Engine Standard with Cloud SQL PostgreSQL. Covers Unix socket connections, Cloud SQL Auth Proxy for local dev, Gunicorn configuration, and production-ready settings. Use when: deploying Django to App Engine, configuring Cloud SQL PostgreSQL, setting up Unix socket connections, or troubleshooting "No such file or directory", "connection refused", or "FATAL: password authentication failed".
Install with Tessl CLI
npx tessl i github:jezweb/claude-skills --skill django-cloud-sql-postgresOverall
score
87%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation 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 clearly defines a specific technical niche (Django on GAE with Cloud SQL). It excels by including both configuration topics and specific error messages as triggers, making it highly discoverable. The explicit 'Use when:' clause with varied trigger scenarios ensures Claude can accurately select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Deploy Django on Google App Engine Standard', 'Cloud SQL PostgreSQL', 'Unix socket connections', 'Cloud SQL Auth Proxy for local dev', 'Gunicorn configuration', and 'production-ready settings'. | 3 / 3 |
Completeness | Clearly answers both what (deploy Django on GAE with Cloud SQL, covers specific configurations) AND when (explicit 'Use when:' clause with deployment scenarios and troubleshooting triggers). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Django', 'App Engine', 'Cloud SQL', 'PostgreSQL', 'Unix socket', plus specific error messages like 'No such file or directory', 'connection refused', 'password authentication failed' that users would search for. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Django + Google App Engine + Cloud SQL PostgreSQL. The specific error messages as triggers further distinguish it from generic Django or cloud deployment skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable, production-ready skill with excellent workflow clarity and comprehensive error prevention. The 12 documented issues section is particularly valuable for preventing common pitfalls. However, the skill is verbose in places with explanatory content Claude doesn't need, and the monolithic structure could benefit from splitting detailed reference material into separate files.
Suggestions
Move the 12 Known Issues section to a separate 'references/known-issues.md' file and summarize the top 3-4 in the main skill
Remove 'Why this matters' and 'Why these settings' explanatory blocks - Claude understands these concepts
Move the complete settings.py example to 'templates/settings.py' and keep only the critical database configuration snippet inline
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., 'Why this matters' sections explaining what psycopg2 is, verbose 'Why these settings' blocks). The 12 documented issues section is valuable but could be more condensed. Overall useful content but could be tightened by ~30%. | 2 / 3 |
Actionability | Excellent executable code throughout - complete settings.py examples, bash commands for gcloud, app.yaml configurations, and Python patterns are all copy-paste ready. Every step has concrete, runnable commands with specific flags and parameters. | 3 / 3 |
Workflow Clarity | Clear 6-step setup process with explicit validation checkpoints. The troubleshooting section provides error recovery paths. The complete setup checklist at the end serves as a verification step. Migration workflow explicitly warns against running in entrypoint and provides safe alternatives. | 3 / 3 |
Progressive Disclosure | References external files (templates/, references/) but these are mentioned without being the primary organization strategy. The skill itself is quite long (~600 lines) with content that could be split - the 12 known issues section and complete settings.py example could be in separate reference files. Structure is good but the main file is monolithic. | 2 / 3 |
Total | 10 / 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 (922 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | 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.