bigquery-scheduled-query
Bigquery Scheduled Query - Auto-activating skill for GCP Skills. Triggers on: bigquery scheduled query, bigquery scheduled query Part of the GCP Skills skill category.
41
11%
Does it follow best practices?
Impact
97%
1.03xAverage 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/bigquery-scheduled-query/SKILL.mdQuality
Discovery
22%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 extremely minimal and essentially just repeats the skill name without explaining what it does or when to use it. It lacks concrete actions, an explicit 'Use when...' clause, and sufficient trigger term variety. The only redeeming quality is that 'bigquery scheduled query' is a reasonably specific domain term.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates, modifies, monitors, and troubleshoots BigQuery scheduled queries in GCP.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to set up recurring SQL queries, automate BigQuery jobs, or manage scheduled query configurations.'
Expand trigger terms to include natural variations like 'schedule a query', 'recurring BigQuery job', 'automated query', 'BQ cron', and 'scheduled SQL'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not list any concrete actions. It only names 'bigquery scheduled query' without describing what the skill actually does (e.g., create, modify, monitor, troubleshoot scheduled queries). | 1 / 3 |
Completeness | The 'what' is essentially absent—there is no explanation of what the skill does beyond naming itself. The 'when' is only partially addressed via trigger terms but lacks an explicit 'Use when...' clause describing scenarios. | 1 / 3 |
Trigger Term Quality | It includes 'bigquery scheduled query' which is a relevant keyword, but the trigger terms are duplicated and missing common variations like 'schedule a query', 'recurring query', 'BigQuery cron', 'scheduled SQL', or 'BQ scheduled query'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'bigquery scheduled query' is fairly specific and unlikely to conflict with non-BigQuery skills, but the lack of detail about what it does versus other potential BigQuery-related skills (e.g., general BigQuery querying, BigQuery administration) creates some overlap risk within the GCP Skills category. | 2 / 3 |
Total | 6 / 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 template with no substantive content about BigQuery scheduled queries. It contains only meta-descriptions of what the skill would do without any actual technical guidance, code examples, configuration snippets, or workflow steps. It provides no value beyond what the skill's title already communicates.
Suggestions
Add concrete, executable examples showing how to create a BigQuery scheduled query using SQL DDL, the bq CLI tool, Terraform, or the Python client library.
Include a clear multi-step workflow: write query → test query → configure schedule (cron syntax) → set service account permissions → validate scheduled query creation → monitor execution.
Provide specific configuration details such as schedule syntax, required IAM roles (e.g., bigquery.admin), service account setup, and common parameters like destination table write disposition.
Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') that describe the skill itself rather than teaching how to accomplish the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content about BigQuery scheduled queries. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no configuration examples, no API references, no SQL syntax. The skill describes rather than instructs, offering nothing executable or copy-paste ready. | 1 / 3 |
Workflow Clarity | No workflow steps are provided whatsoever. Creating a BigQuery scheduled query involves multiple steps (writing the query, configuring schedule, setting service account, etc.) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to supporting files, no structured navigation, and no separation of overview from detailed content. There are no bundle files to support it either. | 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
3a2d27d
- 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.