Bigquery Scheduled Query - Auto-activating skill for GCP Skills. Triggers on: bigquery scheduled query, bigquery scheduled query Part of the GCP Skills skill category.
Overall
score
24%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill bigquery-scheduled-queryActivation
22%This description is severely underdeveloped, essentially just naming the skill topic without explaining what it does or when to use it. The repeated trigger term and lack of concrete actions make it nearly useless for skill selection. It reads more like a placeholder than a functional skill description.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, updates, monitors, and troubleshoots scheduled queries in BigQuery. Configures query schedules, destination tables, and notification settings.'
Add an explicit 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user wants to automate recurring BigQuery queries, set up scheduled data exports, or manage existing query schedules.'
Expand trigger terms to include variations users might naturally say: 'recurring query', 'automate query', 'query schedule', 'cron BigQuery', 'periodic data refresh'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'bigquery scheduled query' but provides no concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'create', 'manage', 'monitor', or 'configure'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic, and provides no explicit 'when to use' guidance. The 'Triggers on' line just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | Contains 'bigquery scheduled query' which is a relevant keyword, but it's repeated identically and misses common variations users might say like 'schedule a query', 'recurring query', 'cron query', 'automated query', or 'BQ scheduled job'. | 2 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'bigquery scheduled query' provides some distinctiveness within GCP skills, but without describing actual capabilities, it could conflict with other BigQuery-related skills or general GCP scheduling skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what a skill should do rather than providing any concrete guidance on BigQuery scheduled queries. The content fails on all dimensions by offering zero actionable information, code examples, or workflow guidance.
Suggestions
Add executable code examples showing how to create a BigQuery scheduled query using gcloud CLI or the BigQuery API/client libraries
Include a clear workflow with steps: define query -> configure schedule -> set destination table -> validate -> monitor execution
Provide specific configuration examples including cron syntax for scheduling, parameterized queries, and error handling patterns
Remove all generic boilerplate text ('Provides step-by-step guidance', 'Follows industry best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty filler that Claude doesn't need to be told. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no commands, and no actual instructions for working with BigQuery scheduled queries. The content only describes what the skill claims to do without showing how. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, and no validation checkpoints for creating or managing BigQuery scheduled queries. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed documentation, examples, or related files. There's no structure that would help Claude navigate to actual useful information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.