CtrlK
BlogDocsLog inGet started
Tessl Logo

gcp-cloud-run

When to use: ['Web applications and APIs', 'Need any runtime or library', 'Complex services with multiple endpoints', 'Stateless containerized workloads']

41

Quality

41%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/gcp-cloud-run/SKILL.md

The canonical home for this skill is gcp-cloud-run in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 skill offers concrete, broadly useful Cloud Run patterns but is undermined by malformed code fences that break rendering, placeholder content in the sharp-edges table, and an absence of validation steps for production deploys.

Suggestions

Fix the broken/nested code fences (e.g. the ```javascript/```dockerfile pair and the Cold Start section where '## 1.' headers appear inside a javascript fence) so all code blocks render correctly.

Replace the placeholder sharp-edges table rows ('Issue | high | ## ...') with real issue names and concrete solutions, or remove the table.

Add explicit validation/verification checkpoints after deploy steps (e.g. check service status, tail logs, confirm the /health endpoint) to support the batch/production nature of Cloud Run deployments.

DimensionReasoningScore

Conciseness

The body is mostly lean code with little conceptual padding, but malformed nested code fences, a placeholder sharp-edges table ('Issue | high | ## Calculate memory...'), and duplicated 'When to use' lists waste tokens and could be tightened.

3 / 5

Actionability

It contains concrete Dockerfile, Express, cloudbuild.yaml, and gcloud code, but broken fences in the Cold Start section (a markdown header inside a javascript fence) and undefined placeholder functions (getItem, processMessage) make parts incomplete rather than copy-paste ready.

3 / 5

Workflow Clarity

cloudbuild.yaml gives an implicit build-push-deploy sequence, but there are no explicit validation or verification checkpoints for production-affecting deploys, which caps this dimension at 3 per the batch/destructive guideline.

3 / 5

Progressive Disclosure

The ~280-line document has section headers (Patterns, Anti-Patterns, Sharp Edges) but is entirely monolithic with no bundle/reference files, and pattern code that could live in separate references is inlined.

3 / 5

Total

12

/

20

Passed

Description

32%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 is a bare 'When to use' trigger list that omits any statement of what the skill does and never names Cloud Run or GCP, leaving it vague and prone to overlapping with other deployment skills.

Suggestions

Add a 'what' clause stating the concrete capability, e.g. 'Deploy containerized services and event-driven functions to GCP Cloud Run.'

Include the platform name and natural triggers ('Cloud Run', 'GCP', 'deploy to Cloud Run', 'Cloud Functions') so the skill is distinguishable from other container platforms.

Convert the bracketed list into prose with an explicit 'Use when...' phrase and concrete actions (deploy, configure, optimize cold starts).

DimensionReasoningScore

Specificity

The description names the domain ('Web applications and APIs', 'Stateless containerized workloads') but lists only applicability scenarios, with no concrete actions like deploy, build, or configure.

2 / 5

Completeness

Only the 'when' is present (a 'When to use' list) with no 'what does this skill do' statement, matching the anchor where only 'when' is present without 'what'.

2 / 5

Trigger Term Quality

It includes relevant scenario phrases ('Web applications and APIs', 'Need any runtime or library') but omits the actual product name 'Cloud Run'/'GCP' and common synonyms users would say, leaving keyword coverage incomplete.

3 / 5

Distinctiveness Conflict Risk

The scenarios are broad and do not mention Cloud Run or GCP, so 'Stateless containerized workloads' would overlap with many other container-deployment skills (ECS, Lambda, etc.).

2 / 5

Total

9

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.