google-cloud-agent-sdk-master
Execute automatic activation for all google cloud agent development kit (adk) Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
35
21%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/productivity/004-jeremy-google-cloud-agent-sdk/skills/google-cloud-agent-sdk-master/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 extremely weak across all dimensions. It reads like a template placeholder rather than an actual skill description—the trigger guidance is circular ('use when appropriate context detected') and no concrete capabilities are listed. The only redeeming quality is the mention of 'Google Cloud Agent Development Kit (ADK)' which provides minimal domain anchoring.
Suggestions
Replace the vague 'automatic activation' with specific concrete actions the skill performs, e.g., 'Scaffolds ADK agent projects, configures agent YAML files, deploys agents to Google Cloud'.
Replace the placeholder trigger clause with explicit natural-language triggers, e.g., 'Use when the user mentions ADK, Google Cloud agents, agent development kit, building conversational agents on GCP, or deploying ADK agents'.
Add a clear 'when' clause that describes specific scenarios, such as 'Use when creating, testing, or deploying agents using Google Cloud's Agent Development Kit framework'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Execute automatic activation for all google cloud agent development kit (adk)' which is vague and does not list any concrete actions. There are no specific capabilities described—just a generic 'automatic activation' phrase. | 1 / 3 |
Completeness | The 'what' is extremely vague ('automatic activation' tells nothing about what the skill actually does), and the 'when' is a meaningless placeholder ('when appropriate context detected' and 'trigger with relevant phrases based on skill purpose'). Both are effectively missing. | 1 / 3 |
Trigger Term Quality | The phrases 'appropriate context detected' and 'relevant phrases based on skill purpose' are entirely generic meta-language, not actual trigger terms. While 'google cloud agent development kit' and 'adk' are mentioned, the trigger guidance is circular and unhelpful. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'google cloud agent development kit (adk)' does provide some domain specificity that distinguishes it from generic skills, but the lack of concrete actions or clear triggers means it could still overlap with other Google Cloud-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a project management template than an actionable technical guide. It lacks any concrete ADK code, CLI commands, or specific patterns that would help Claude actually build agents with Google's ADK. The references to a full guide and external docs suggest the real content lives elsewhere, but the SKILL.md itself provides almost no executable guidance.
Suggestions
Add concrete, executable code examples showing ADK agent creation (e.g., a minimal single-agent scaffold with `google.adk` imports, tool definitions, and a runnable entry point).
Include specific CLI commands for ADK operations (e.g., `adk create`, `adk deploy`, `adk test`) with actual flags and expected outputs.
Replace the abstract 'Example' section with a real input/output pair showing actual code or configuration that would be produced.
Add validation commands with expected success/failure outputs so Claude knows what 'passing' looks like (e.g., `adk validate agent.py` → expected output).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some unnecessary padding. The 'Overview' section restates what the skill does in a way that adds little value. The 'Examples' section describes what would happen rather than showing concrete output. The 'Prerequisites' section lists things Claude should infer from context rather than needing to be told. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. The instructions are high-level process steps ('Clarify requirements', 'Define tool interfaces', 'Provide an implementation plan') that describe rather than instruct. There are no ADK-specific code snippets, CLI commands, or concrete patterns that Claude could directly use. | 1 / 3 |
Workflow Clarity | There is a numbered sequence of steps and the output section mentions validation checklists, but the steps are abstract ('Clarify requirements', 'Add validation') without specific checkpoints or feedback loops. The validation step mentions 'smoke prompts, regression tests' but doesn't show how to run them or what to check. | 2 / 3 |
Progressive Disclosure | The skill references a detailed guide at `${CLAUDE_SKILL_DIR}/references/SKILL.full.md` and external docs, which is good progressive disclosure structure. However, no bundle files are provided to verify the reference exists, and the main content itself is thin enough that it's unclear what value the overview provides beyond pointing to the full guide. | 2 / 3 |
Total | 7 / 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.