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 severely underdeveloped, essentially serving as a label rather than a functional skill description. It names the topic but provides no information about what actions the skill enables or specific scenarios for its use. The duplicate trigger term suggests incomplete editing.
Suggestions
Add specific actions the skill performs, e.g., 'Creates, modifies, monitors, and troubleshoots BigQuery scheduled queries in GCP.'
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to automate recurring BigQuery jobs, set up scheduled SQL execution, or manage existing scheduled queries.'
Expand trigger terms to include variations like 'schedule query', 'recurring query', 'BigQuery automation', 'cron job BigQuery', and 'scheduled SQL'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain 'bigquery scheduled query' but provides no concrete actions. There are no verbs describing what the skill actually does (e.g., create, modify, monitor, troubleshoot). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming the topic. While it lists trigger terms, there is no explanation of capabilities or a proper 'Use when...' clause explaining when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'bigquery scheduled query' as a trigger term (duplicated), which is a natural phrase users might say. However, it's missing common variations like 'schedule query', 'recurring query', 'BigQuery automation', 'cron query', or 'scheduled SQL'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'bigquery scheduled query' focus is somewhat specific and wouldn't conflict with general document or code skills. However, it could overlap with other GCP/BigQuery skills without clearer differentiation of its specific purpose. | 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 content is essentially a placeholder template with no actual instructional value. It describes what a skill should do rather than providing any concrete guidance on BigQuery scheduled queries. The entire content could be replaced with actual executable examples, gcloud commands, or SQL syntax for scheduled queries.
Suggestions
Add concrete code examples showing how to create a scheduled query using gcloud CLI (e.g., `bq mk --transfer_config ...`) or the BigQuery console steps
Include a working SQL example with scheduling parameters and destination table configuration
Provide a workflow with validation steps: create query -> test manually -> schedule -> verify execution history
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') 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 to do anything. | 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 meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related documentation. | 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
0c08951
- 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.