bigquery-view-generator

Bigquery View Generator - Auto-activating skill for GCP Skills. Triggers on: bigquery view generator, bigquery view generator Part of the GCP Skills skill category.

0.92x

Quality

11%

Does it follow best practices?

Impact

83%

0.92x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./planned-skills/generated/14-gcp-skills/bigquery-view-generator/SKILL.md

Quality

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 just restating the skill name without explaining what it actually does or when to use it. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The description would fail to help Claude distinguish this skill from others in a large skill library.

Suggestions

Add specific actions the skill performs, e.g., 'Generates BigQuery view definitions, creates SQL SELECT statements for views, handles view schema design and column aliasing'

Include a 'Use when...' clause with natural trigger terms like 'Use when creating BigQuery views, defining SQL views in GCP, or when the user mentions BQ views, view definitions, or BigQuery SELECT statements'

Remove the duplicate trigger term and expand to include variations users might naturally say: 'bigquery view', 'BQ view', 'create view in bigquery', 'SQL view GCP'

Dimension	Reasoning	Score
Specificity	The description only names the tool ('Bigquery View Generator') but provides no concrete actions. It doesn't explain what generating a BigQuery view entails or what specific capabilities it offers.	1 / 3
Completeness	The description fails to answer 'what does this do' beyond the name itself, and the 'when' is only a literal trigger phrase repetition rather than meaningful usage guidance. No 'Use when...' clause or equivalent.	1 / 3
Trigger Term Quality	Includes 'bigquery view generator' as a trigger term (duplicated), which is somewhat relevant but misses natural variations users might say like 'create view', 'SQL view', 'BigQuery SQL', 'BQ view', or 'define view'.	2 / 3
Distinctiveness Conflict Risk	The BigQuery-specific focus provides some distinctiveness from general SQL or database skills, but the vague description could overlap with other BigQuery-related skills or general SQL view creation tools.	2 / 3
	Total	6 / 12 Passed

Implementation

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. It describes what a BigQuery view generator skill would do without providing any actual guidance, code examples, or workflows for generating BigQuery views. The entire content could be replaced with a single executable SQL example and would be more useful.

Suggestions

Add concrete SQL examples showing how to create BigQuery views (e.g., CREATE VIEW syntax with common patterns like aggregations, joins, or partitioned views)

Include a workflow for view creation: define schema -> write SQL -> validate with dry-run -> deploy -> verify

Provide specific bq CLI commands or Python client code for programmatic view creation

Remove the meta-description sections (Purpose, When to Use, Example Triggers) and replace with actionable technical content

Dimension	Reasoning	Score
Conciseness	The content is padded with boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need.	1 / 3
Actionability	No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly but never shows how to actually generate a BigQuery view - no SQL examples, no API calls, no configuration snippets.	1 / 3
Workflow Clarity	No workflow or steps are defined. The 'Capabilities' section mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for creating BigQuery views.	1 / 3
Progressive Disclosure	The content is a monolithic block of meta-description with no actual technical content to organize. No references to detailed documentation, examples, or related files are provided.	1 / 3
	Total	4 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 0c08951

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.