cloud-scheduler-job-creator
Cloud Scheduler Job Creator - Auto-activating skill for GCP Skills. Triggers on: cloud scheduler job creator, cloud scheduler job creator Part of the GCP Skills skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/14-gcp-skills/cloud-scheduler-job-creator/SKILL.mdQuality
Discovery
7%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 description is essentially a title with metadata rather than a functional description. It provides no information about what actions the skill performs, what parameters or configurations it handles, or when Claude should use it. The trigger terms are redundant and miss common user language patterns.
Suggestions
Add specific actions the skill performs, e.g., 'Creates and configures Cloud Scheduler jobs including cron expressions, HTTP/Pub-Sub targets, retry policies, and time zones'
Add a 'Use when...' clause with natural trigger terms like 'schedule a task', 'create cron job', 'recurring job in GCP', 'automate scheduled execution'
Include common variations of terminology users might use: 'scheduled task', 'cron schedule', 'timer trigger', 'periodic job'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Cloud Scheduler Job Creator' without describing any concrete actions. It doesn't explain what creating a job entails, what parameters can be configured, or what outcomes are produced. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'cloud scheduler job creator' repeated twice. Missing natural variations users would say like 'schedule task', 'cron job', 'scheduled job', 'GCP scheduler', 'create schedule', or 'automate recurring task'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Cloud Scheduler' and 'GCP' provides some specificity to Google Cloud Platform's scheduling service, but without describing specific capabilities, it could overlap with other scheduling or automation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actual content. It contains only generic boilerplate text that could apply to any skill, with no specific guidance on Cloud Scheduler job creation. The skill fails to provide any actionable information - no gcloud commands, no API examples, no configuration formats, and no workflow for creating scheduler jobs.
Suggestions
Add executable gcloud commands for creating Cloud Scheduler jobs (e.g., `gcloud scheduler jobs create http JOB_NAME --schedule='0 9 * * *' --uri=TARGET_URL`)
Include concrete examples showing different job types (HTTP, Pub/Sub, App Engine) with complete configuration
Provide a clear workflow: 1) Define schedule (cron format), 2) Configure target, 3) Set authentication, 4) Create job, 5) Verify with `gcloud scheduler jobs describe`
Add common patterns like retry configuration, time zone handling, and authentication setup for different target types
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about Cloud Scheduler. | 1 / 3 |
Actionability | There is zero concrete guidance - no gcloud commands, no API calls, no code examples, no actual instructions for creating a Cloud Scheduler job. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Creating a Cloud Scheduler job involves specific steps (defining schedule, target, authentication) that are completely absent. No validation or verification steps mentioned. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. No references to examples, API documentation, or related configuration files. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
b8a3b3e
- 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.