cloud-logging-sink-setup
Cloud Logging Sink Setup - Auto-activating skill for GCP Skills. Triggers on: cloud logging sink setup, cloud logging sink setup Part of the GCP Skills skill category.
36
Quality
3%
Does it follow best practices?
Impact
96%
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-logging-sink-setup/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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or providing meaningful trigger guidance. It lacks concrete actions, natural user keywords, and explicit usage conditions. The redundant trigger terms and boilerplate category mention add no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures Cloud Logging sinks to route logs to BigQuery, Cloud Storage, or Pub/Sub destinations.'
Add a proper 'Use when...' clause with natural trigger terms like 'Use when setting up log exports, routing logs to storage, configuring log sinks, or when the user mentions log destinations in GCP.'
Include common keyword variations users might say: 'log routing', 'export logs', 'log destination', 'Stackdriver sink', 'log aggregation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Cloud Logging Sink Setup') but provides no concrete actions. It doesn't explain what specific tasks this skill performs - no verbs describing capabilities like 'create', 'configure', 'route logs', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the title, and has no explicit 'Use when...' clause or equivalent guidance. The 'Triggers on' line is not a proper when clause - it just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('cloud logging sink setup' repeated twice) and overly specific/technical. Missing natural variations users might say like 'log routing', 'export logs', 'stackdriver sink', 'log destination', or 'GCP logging'. | 1 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Cloud Logging Sink' and 'GCP' provides some distinctiveness within cloud platforms, but the lack of detail about what actions it performs could cause confusion with other GCP logging-related 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 an empty placeholder that describes what a skill should do rather than providing any actual guidance for Cloud Logging sink setup. It contains no executable code, no gcloud commands, no configuration examples, and no concrete steps. The entire content is self-referential boilerplate that would provide zero value to Claude when actually performing the task.
Suggestions
Add concrete gcloud commands for creating logging sinks, e.g., `gcloud logging sinks create SINK_NAME DESTINATION --log-filter=FILTER`
Include specific examples for common sink destinations (BigQuery, Cloud Storage, Pub/Sub) with complete configuration snippets
Provide a clear workflow: 1) Define filter, 2) Create sink, 3) Grant service account permissions, 4) Verify sink is working
Add validation steps such as `gcloud logging sinks describe SINK_NAME` and how to test that logs are flowing to the destination
| 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 technical content. | 1 / 3 |
Actionability | There is zero concrete guidance - no commands, no code, no specific steps for setting up a Cloud Logging sink. The skill describes what it claims to do rather than actually instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps, no sequence, no validation checkpoints - just vague claims about 'step-by-step guidance' without any actual steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, no code examples to organize, and no actual content to disclose progressively. | 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.