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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill google-cloud-agent-sdk-master60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 deficient - it's essentially a template placeholder rather than a functional skill description. It names the technology (Google Cloud ADK) but fails to describe any concrete capabilities, and the trigger guidance is completely circular and unhelpful. Claude would have no meaningful basis for selecting this skill appropriately.
Suggestions
Replace the vague 'Execute automatic activation' with specific actions like 'Create agents, configure tools, deploy to Vertex AI, test agent responses'
Add explicit trigger terms users would actually say, such as 'ADK project', 'create agent', 'Vertex AI agent', 'agent tools', 'agent deployment'
Rewrite the 'Use when' clause with concrete scenarios: 'Use when building conversational agents with Google Cloud ADK, configuring agent tools, or deploying agents to Vertex AI'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - 'Execute automatic activation' is vague and abstract. It doesn't describe what the skill actually does with the Google Cloud ADK. | 1 / 3 |
Completeness | The 'what' is essentially missing (no actual capabilities described), and the 'when' is completely circular ('Use when appropriate context detected' provides no guidance). Both are very weak. | 1 / 3 |
Trigger Term Quality | Contains 'google cloud agent development kit (adk)' which is a relevant keyword, but 'appropriate context detected' and 'relevant phrases based on skill purpose' are circular and provide no actual trigger terms users would say. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'google cloud agent development kit (adk)' provides some specificity to a particular technology, but the lack of concrete actions means it could still conflict with other Google Cloud or development-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized and concise, appropriately assuming Claude's competence with agent development concepts. However, it lacks concrete, executable examples - the instructions describe what to do at a high level without providing specific code scaffolds, commands, or copy-paste ready implementations that would make it immediately actionable.
Suggestions
Add a concrete code example showing a minimal ADK agent scaffold with tool definition
Include specific validation commands (e.g., `adk run --smoke-test` or equivalent) rather than abstract 'smoke prompts' guidance
Provide an example tool interface definition showing the expected input/output/error contract format
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of what ADK is or how agents work. Every section serves a purpose without padding or unnecessary context. | 3 / 3 |
Actionability | Instructions are clear but abstract - no concrete code examples, specific commands, or executable scaffolds are provided. The guidance describes what to do rather than showing how with copy-paste ready examples. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (clarify → define → implement → validate), but validation checkpoints lack specificity. No concrete commands for smoke tests or deployment verification are provided. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and appropriate references to external resources (full guide, docs, standards). Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 10 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.